杀死守护进程
因为之前的接口1.0是以守护进程的形式部署到服务器上的,我们如果想把接口2.0的数据也部署到服务器的80端口,就需要把之前的守护进程杀死,再创建新的守护进程。
- 重启服务器
reboot
命令重启服务器,如果服务器只有这一个在跑的 程序没有其他的重要的进程这样也可以,不过如果有其他的进程在运行就不可以这样了。 - 查看守护进程pid并杀死
先查看守护进程的id
(base) [root@iZ2zeircp62xkpbg5hioetZ admin]# ps -ef |grep gunicorn
root 1341 1 0 21:44 ? 00:00:00 /usr/bin/python /usr/bin/gunicorn -c runconfig.py runserver:app
root 2429 1341 0 22:30 ? 00:00:00 /usr/bin/python /usr/bin/gunicorn -c runconfig.py runserver:app
root 2543 1 0 22:43 ? 00:00:00 /home/admin/work/yes/envs/innovationtraining/bin/python /home/admin/work/yes/envs/innovationtraining/bin/gunicorn -b 127.0.0.1:8080 -D app:app_1
root 2597 2543 0 23:12 ? 00:00:00 /home/admin/work/yes/envs/innovationtraining/bin/python /home/admin/work/yes/envs/innovationtraining/bin/gunicorn -b 127.0.0.1:8080 -D app:app_1
root 2601 2392 0 23:12 pts/3 00:00:00 grep --color=auto gunicorn
因为我是用gunicorn启动的守护进程,所以是查看的gunicorn相关的进程
然后根据进程pid杀死进程即可
kill -9 pid
错误尝试
- 看其他的博客有查看守护进程树在使用
kill -HUP pid
的方法杀死守护进程,我尝试之后并未成功,过程附下:
(base) [root@iZ2zeircp62xkpbg5hioetZ admin]# pstree -ap|grep gunicorn
|-gunicorn,1341 /usr/bin/gunicorn -c runconfig.py runserver:app
| `-gunicorn,2429 /usr/bin/gunicorn -c runconfig.py runserver:app
| `-{gunicorn},2430
|-gunicorn,2543 /home/admin/work/yes/envs/innovationtraining/bin/gunicorn -b 127.0.0.1:8080
| `-gunicorn,2545 /home/admin/work/yes/envs/innovationtraining/bin/gunicorn -b 127.0.0.1:8080
| |-grep,2596 --color=auto gunicorn
(base) [root@iZ2zeircp62xkpbg5hioetZ admin]# kill -HUP 2543
(base) [root@iZ2zeircp62xkpbg5hioetZ admin]# pstree -ap|grep gunicorn
|-gunicorn,1341 /usr/bin/gunicorn -c runconfig.py runserver:app
| `-gunicorn,2429 /usr/bin/gunicorn -c runconfig.py runserver:app
| `-{gunicorn},2430
|-gunicorn,2543 /home/admin/work/yes/envs/innovationtraining/bin/gunicorn -b 127.0.0.1:8080
| `-gunicorn,2597 /home/admin/work/yes/envs/innovationtraining/bin/gunicorn -b 127.0.0.1:8080
| |-grep,2599 --color=auto gunicorn