nginx平滑升级

nginx信号

TERM, INT fast shutdown
QUIT graceful shutdown
HUP changing configuration, keeping up with a changed time zone (only for FreeBSD and Linux), starting new worker processes with a new configuration, graceful shutdown of old worker processes
USR1 re-opening log files
USR2 upgrading an executable file
WINCH graceful shutdown of worker processes

编译新版本

查看旧nginx编译参数

# /usr/local/webserver/nginx/sbin/nginx -V
nginx version: nginx/1.12.2
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) 
built with OpenSSL 1.0.2k-fips  26 Jan 2017
TLS SNI support enabled
configure arguments: --prefix=/usr/local/webserver/nginx --user=nobody --group=nobody --with-http_stub_status_module --with-http_ssl_module

编译新版本,注意不用make install 备注1

# tar -xzf nginx-1.14.2.tar.gz
# cd nginx-1.14.2
# yum install -y gcc
# ./configure --prefix=/usr/local/webserver/nginx --user=nobody --group=nobody --with-http_stub_status_module --with-http_ssl_module
# make -j `cat /proc/cpuinfo | grep "^processor" | wc -l`

平滑升级 备注2

在这里插入图片描述

拷贝二进制文件

# cp -a /usr/local/webserver/nginx/sbin/nginx /usr/local/webserver/nginx/sbin/nginx.oldbin
# cp -af objs/nginx /usr/local/webserver/nginx/sbin/nginx
cp: overwrite ‘/usr/local/webserver/nginx/sbin/nginx’? y
# ps -ef | grep ngin[x]
root     31862     1  0 11:16 ?        00:00:00 nginx: master process /usr/local/webserver/nginx/sbin/nginx
nobody   31863 31862  0 11:16 ?        00:00:00 nginx: worker process
nobody   31864 31862  0 11:16 ?        00:00:00 nginx: worker process

发送USR2信号给master进程 备注3

# kill -s USR2 12029
# ps -ef | grep ngin[x]
root     31862     1  0 11:16 ?        00:00:00 nginx: master process /usr/local/webserver/nginx/sbin/nginx
nobody   31863 31862  0 11:16 ?        00:00:00 nginx: worker process
nobody   31864 31862  0 11:16 ?        00:00:00 nginx: worker process
root     31961 31862  0 11:17 ?        00:00:00 nginx: master process /usr/local/webserver/nginx/sbin/nginx
nobody   31962 31961  0 11:17 ?        00:00:00 nginx: worker process
nobody   31963 31961  0 11:17 ?        00:00:00 nginx: worker process

发送WINCH信号给旧master进程

# kill -s WINCH 31862
# ps -ef | grep ngin[x]
root     31862     1  0 11:16 ?        00:00:00 nginx: master process /usr/local/webserver/nginx/sbin/nginx
root     31961 31862  0 11:17 ?        00:00:00 nginx: master process /usr/local/webserver/nginx/sbin/nginx
nobody   31962 31961  0 11:17 ?        00:00:00 nginx: worker process
nobody   31963 31961  0 11:17 ?        00:00:00 nginx: worker process

master进程退出

# kill -s QUIT 31862
# ps -ef | grep ngin[x]
root     31961     1  0 11:17 ?        00:00:00 nginx: master process /usr/local/webserver/nginx/sbin/nginx
nobody   31962 31961  0 11:17 ?        00:00:00 nginx: worker process
nobody   31963 31961  0 11:17 ?        00:00:00 nginx: worker process

备注

备注1

make install实际上只是将编译好的文件拷贝到指定目录,如下

# make install
make -f objs/Makefile install
make[1]: Entering directory `/usr/local/src/nginx-1.12.2'
test -d '/usr/local/webserver/nginx' || mkdir -p '/usr/local/webserver/nginx'
test -d '/usr/local/webserver/nginx' \
	|| mkdir -p '/usr/local/webserver/nginx'
test ! -f '/usr/local/webserver/nginx/sbin' \
	|| mv '/usr/local/webserver/nginx/sbin' \
		'/usr/local/webserver/nginx/sbin.old'
cp objs/nginx '/usr/local/webserver/nginx/sbin'
...

备注2

除了手动一步一步的进行升级之外,也可以执行make upgrade一步到位。

# cat Makefile 

default:	build

clean:
	rm -rf Makefile objs

build:
	$(MAKE) -f objs/Makefile

install:
	$(MAKE) -f objs/Makefile install

modules:
	$(MAKE) -f objs/Makefile modules

upgrade:
	/usr/local/webserver/nginx/sbin/nginx -t

	kill -USR2 `cat /usr/local/webserver/nginx/logs/nginx.pid`
	sleep 1
	test -f /usr/local/webserver/nginx/logs/nginx.pid.oldbin

	kill -QUIT `cat /usr/local/webserver/nginx/logs/nginx.pid.oldbin`

备注3

从较老版本升级到新版本时候遇到一个问题,新进程会在3s左右退出,错误日志如下

2019/07/25 17:58:44 [emerg] 15540#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/07/25 17:58:44 [emerg] 15540#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/07/25 17:58:44 [emerg] 15540#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/07/25 17:58:44 [emerg] 15540#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/07/25 17:58:44 [emerg] 15540#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/07/25 17:58:44 [emerg] 15540#0: still could not bind()
nginx: [emerg] still could not bind()

查了一下进程监听到端口的流程:
socket

strace查了下,发新新master进程在打开了日志文件描述符之后,会尝试创建新的socket,猜测新老版本差异太大了,无法共享同socket。

[pid 16930] socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = 8
[pid 16930] setsockopt(8, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid 16930] ioctl(8, FIONBIO, [1])      = 0
[pid 16930] bind(8, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EADDRINUSE (Address already in use)
[pid 16930] write(4, "2019/07/25 18:14:43 [emerg] 1693"..., 94) = 94
[pid 16930] write(2, "nginx: [emerg] bind() to 0.0.0.0"..., 72) = 72
[pid 16930] close(8)                    = 0
[pid 16930] nanosleep({0, 500000000}, NULL) = 0
[pid 16930] socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = 8
[pid 16930] setsockopt(8, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid 16930] ioctl(8, FIONBIO, [1])      = 0
[pid 16930] bind(8, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EADDRINUSE (Address already in use)
[pid 16930] write(4, "2019/07/25 18:14:43 [emerg] 1693"..., 94) = 94
[pid 16930] write(2, "nginx: [emerg] bind() to 0.0.0.0"..., 72) = 72
[pid 16930] close(8)

参考:http://nginx.org/en/docs/control.html

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
信息数据从传统到当代,是一直在变革当中,突如其来的互联网让传统的信息管理看到了革命性的曙光,因为传统信息管理从时效性,还是安全性,还是可操作性等各个方面来讲,遇到了互联网时代才发现能补上自古以来的短板,有效的提升管理的效率和业务水平。传统的管理模式,时间越久管理的内容越多,也需要更多的人来对数据进行整理,并且数据的汇总查询方面效率也是极其的低下,并且数据安全方面永远不会保证安全性能。结合数据内容管理的种种缺点,在互联网时代都可以得到有效的补充。结合先进的互联网技术,开发符合需求的软件,让数据内容管理不管是从录入的及时性,查看的及时性还是汇总分析的及时性,都能让正确率达到最高,管理更加的科学和便捷。本次开发的医院后台管理系统实现了病房管理、病例管理、处方管理、字典管理、公告信息管理、患者管理、药品管理、医生管理、预约医生管理、住院管理、管理员管理等功能。系统用到了关系型数据库中王者MySql作为系统的数据库,有效的对数据进行安全的存储,有效的备份,对数据可靠性方面得到了保证。并且程序也具备程序需求的所有功能,使得操作性还是安全性都大大提高,让医院后台管理系统更能从理念走到现实,确确实实的让人们提升信息处理效率。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值