


Operation tutorial for smooth upgrade of nginx
Smooth upgrade overview
Nginx conveniently helps us achieve smooth upgrades. The principle is simply summarized as follows:
(1) Start a new process without stopping the old process.
(2) The old process is responsible for processing requests that have not yet been processed, but will no longer accept processing requests.
(3) The new process accepts new requests.
(4) The old process stops after processing all requests and closing all connections.
This makes it easy to achieve smooth upgrades. Generally, there are two situations when you need to upgrade Nginx. One is to really upgrade the version of Nginx, and the other is to add a new module to Nginx.
Upgrade process
The specific operation is also very simple, as follows:
(0) View the current version
Enter in the directory where the Nginx executable file is stored:
Copy the code as follows:
./nginx -V
(1) Download the new Nginx version and compile it .
Copy the code code as follows:
wget nginx-1.0.11.tar.gz
tar zxvf nginx-1.0.11.tar.gz
cd nginx- 1.0.11
./configure --add-module=/customized_module_0 --add-module=/customized_module_1
make
[root@liuawblizfpws~]#wget *.*.tar.gz (version number has been modified)Unzip:
[root@liuawblizfpws ~]#tar zxvf nginx-0.*.*.tar.gz (version number has been modified)By the way, the version number of nginx is modified here, which plays a certain security role. Modify the source code file:
[root@liuawblizfpws ~]#vim nginx-0.*.*/src/core/nginx.h#define NGINX_VERSION "*.$.&" (version number)#define NGINX_VER "net/" NGINX_VERSION (server name)You need to check the previous nginx installation information before recompiling :[root@liuawblizfpws ~]#/usr/local/nginx/sbin/nginx -VGet information (the path varies from person to person):nginx: configure arguments: --user=www --group=www --prefix=/usr/local/nginx --with-http_stub_status_module --with-http_ssl_moduleCompile, but not install; in the compilation directory The nginx file in the objs directory is the new executable file:
[root@liuawblizfpws nginx-0.*.*]#./configure --user=www --group=www -- prefix=/usr/local/nginx --with-http_stub_status_module --with-http_ssl_module[root@liuawblizfpws nginx-0.*.*]#makeBack up the original nginx file: [root@liuawblizfpws ~]#mv /usr/local/nginx/sbin/nginx /usr/local/nginx/sbin/nginx.old will have been compiled Copy the nginx file to the corresponding execution path: cp ~/nginx-0.*.*/objs/nginx /usr/local/nginx/sbin/nginx Test to avoid failure Smooth upgrade:
[root@liuawblizfpws ~]#/usr/local/nginx/sbin/nginx -tnginx: the configuration file /usr/local/nginx/conf /nginx.conf syntax is oknginx: configuration file /usr/local/nginx/conf/nginx.conf test is successfulIf the test passes, modify nginx.pid to your nginx.pid.oldbin, while starting the new nginx: [root@liuawblizfpws ~]#kill -USR2 `cat /usr/local/nginx/logs/nginx.pid` Exit original nginx: [root@liuawblizfpws ~]#kill -QUIT `cat /usr/loca/nginx/logs/nginx.pid.oldbin`Check:
[root@liuawblizfpws ~]#curl -I netonline.meHTTP/1.1 200 OKServer: net/*.$.&Date: Thu, 09 Dec 2010 05:13:36 GMT
The above is the detailed content of Operation tutorial for smooth upgrade of nginx. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

To set the access address to server IP in Nginx, configure the server block, set the listening address (such as listen 192.168.1.10:80) Set the server name (such as server_name example.com www.example.com), or leave it blank to access the server IP and reload Nginx to apply the changes

The methods to view the running status of Nginx are: use the ps command to view the process status; view the Nginx configuration file /etc/nginx/nginx.conf; use the Nginx status module to enable the status endpoint; use monitoring tools such as Prometheus, Zabbix, or Nagios.

There are two ways to solve the Nginx cross-domain problem: modify the cross-domain response header: add directives to allow cross-domain requests, specify allowed methods and headers, and set cache time. Use CORS modules: Enable modules and configure CORS rules that allow cross-domain requests, methods, headers, and cache times.
