[LNMP] Nginx access_log Daily Rotation

Wed, 10 Apr 2019 02:30:15 +0000

Previously, I had a service using Nginx as a reverse proxy. Due to the high volume of traffic, I wanted to do some simple access statistics at the Nginx layer. I found that Nginx’s default access_log writes everything to a single file, which is very inconvenient. After some research, many people suggested using shell scripts to solve this problem. Finally, I found a better solution – Nginx supports the following configuration:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23


server {
 listen 8082;
 server_name your ip;

 if ($time_iso8601 ~ "^(\d{4})-(\d{2})-(\d{2})T(\d{2}):(\d{2}):(\d{2})"){
 set $year \$1;
 set $month \$2;
 set $day \$3;
 set $hour \$4;
 set $minutes \$5;
 set $seconds \$6;
 }

 access_log logs/8082_$year-$month-$day.log;
 error_log logs/8082.error;

 # Forward all requests
 location / {
 proxy_set_header Host $host;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_pass http://localhost:8082;
 }
}

[nginx] Starting, Stopping, and Restarting Nginx on Linux

Sat, 23 May 2015 05:36:29 +0000

Starting Nginx

1

/usr/nginx/sbin/nginx

1

/usr/nginx/sbin/nginx -t

Check whether the configuration is correct.

Stopping Nginx

Stopping is done by sending signals to the nginx process (for more about signals, refer to Linux documentation).

Step 1: Find the nginx master process ID

1

ps -ef | grep nginx

Find the master process in the process list – its number is the master process ID.

Step 2: Send a signal

Graceful shutdown:
1

kill -QUIT master_process_id
Fast shutdown:
1

kill -TERM master_process_id
Forced shutdown:
1

pkill -9 nginx

Additionally, if the pid file path is configured in nginx.conf, that file contains the Nginx master process ID. If not specified, it is stored in nginx’s logs directory. With the pid file, you don’t need to look up the master process ID first and can send signals to Nginx directly:

1

kill -signal_type '/usr/nginx/logs/nginx.pid'

Graceful Restart

If you changed the configuration, do you need to stop Nginx and start it again? No – you can send a signal to Nginx for a graceful restart.

Graceful restart command:

1

kill -HUP master_process_id_or_pid_file_path

Or use:

1

/usr/nginx/sbin/nginx -s reload

Note: After modifying the configuration file, it’s best to check whether the modified configuration is correct first, to avoid errors after restart that could affect server stability. The command to check Nginx configuration:

1

nginx -t -c /usr/nginx/conf/nginx.conf

Or:

1

/usr/nginx/sbin/nginx -t