Shulou(Shulou.com)05/31 Report--

This article mainly explains how to install the Linux process management tool Supervisor. Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to install the Linux process management tool Supervisor.

Experimental environment

System platform

Cat / etc/redhat-release CentOSLinux release 7.6.1810 (Core)

Python version

Python-V Python2.7.5

If the python version is less than 2.6, please upgrade. Here is an installation example for installing python3.6.8.

Yum install zlib-devel bzip2-devel openssl-devel ncurses-devel sqlite-devel readline-devel tk-devel gdbm-devel db4-devel libpcap-devel xz-devel-y libffi-devel wget https://www.python.org/ftp/python/3.6.8/Python-3.6.8.tar.xz tar xf Python-3.6.8.tar.xz cd Python-3.6.8. / configure-- prefix=/usr/local/python368 make & & make install echo 'export PATH=/usr/local/ Python368/bin:$PATH' > > / etc/profile source / etc/profile python3-V

Install Supervisor

There are many ways to install Supervisor, three of which are described below, and the third one I use here

1. Easy_install install supervisor

Installing Python package Management tool (easy_install) easy_install is a command in the setuptools package. Using easy_install is actually calling setuptools to complete the installation of the module, so you can install setuptools:

Wget https://pypi.io/packages/source/s/setuptools/setuptools-33.1.1.zip unzip setuptools-33.1.1.zip cd setuptools-33.1.1 python setup.py install easy_install supervisor

2. Pip install supervisor

Use pip to install, as long as the pip version is greater than 2.6

Pip install supervisor

3. Yum epel-release install supervisor

Yum install-y epel-release & & yum install-y supervisor

Superviso command

After the supervisor installation is completed, three execution programs are generated: supervisortd, supervisorctl, and echo_supervisord_conf:

Supervisortd: used to manage the supervisor itself service supervisorctl: used to manage the service we need to delegate to the superviso tool echo_supervisord_conf: daemon service for generating superviso configuration file supervisor (for receiving process management commands) client (for communicating with daemons and sending instructions for managing processes)

[root@Jumpserver /] # which supervisord / bin/supervisord [root@Jumpserver /] # which supervisorctl / bin/supervisorctl [root@Jumpserver /] # which echo_supervisord_conf / bin/echo_supervisord_conf

Configure Supervisor

Generate the initialization configuration file for supervisor by running the echo_supervisord_conf program

If you use yum installation, this step is omitted and the configuration file modification step is carried out directly.

Mkdir / etc/supervisord.d echo_supervisord_conf > / etc/supervisord.conf

Modify the configuration file

There are many configuration files for supervisor, but many of them can be used without modification. I have only modified the following two items here.

# modify the mode of socket file. Default is 0700.

Sed-I-I-

# add the following two lines at the end of the configuration file to include the / etc/supervisord directory

Sed-I'$a [include]\

Files = / etc/supervisord.d/*.conf' / etc/supervisord.conf

Write processes that need to be managed by Supervisor

Supervisor can only manage non-dameon processes. For example, the default redis runs in the foreground, and Tomcat actually calls catalina.sh to run in the background. The default catalina.sh is a program running in the foreground, and non-dameon processes like Nginx cannot be managed.

Tomcat is managed by Supervisor

The Tomcat installation is as follows:

Wget http://us.mirrors.quenda.co/apache/tomcat/tomcat-8/v8.5.47/bin/apache-tomcat-8.5.47.tar.gz yum install java-1.8.0-openjdk.x86_64 java-1.8.0-openjdk-devel.x86_64-y tar xf apache-tomcat-8.5.47.tar.gz-C / usr/local/ mv / usr/local/apache-tomcat-8.5.47/usr/local/tomcat

If you want our application to be managed by Supervisor, you need to write a configuration file in the / etc/supervisord directory. The Tomcat example is as follows:

Vim / etc/supervisord.d/tomcat.conf [program:tomcat] # unique name of the program directory=/usr/local/tomcat # Program path command=/usr/local/tomcat/bin/catalina.sh run # whether the command autostart=true# of the running program does not exit abnormally 10 seconds after the tomcat also starts the startsecs=10# after supervisord starts, it means that the process has started normally. Default is 1 second. Autorestart=true# program restarts automatically after exiting. Available value: [unexpected,true,false]. Default is unexpected, which means that the process will restart after it is killed unexpectedly. It means that if the process is not shut down by supervisord, it is considered improper. Supervisord will start the process again. Only the supervisorctl can be used for shutdown, startup, and restart operations. Startretries=3# failed to automatically retry the number of attempts. Default is 3 user=root # which user starts the process. Default is root priority=999# process startup priority. Default is 999. If Supervisord needs to manage multiple processes, then the small value first starts stopsignal=INT redirect_stderr=true# to redirect stderr to stdout standard output. The default false stdout_logfile_maxbytes=200MB#stdout standard output log file size is 200m, and the log file size is cut. The cut log file will be marked as catalina.out1,catalina.out2,catalina.out3..., default 50MB stdout_logfile_backups = number of backup 100#stdout standard output log files. Save 100 200MB log files, more than 100 old will be deleted, the default is 10 save 10 stdout_logfile=/usr/local/tomcat/logs/catalina.out# standard log output location, if the output location does not exist, it will start failure stopasgroup=false# default to false, when the process is killed, whether to send stop signal to this process group, including child process killasgroup=false# default to false, send kill signal to process group, including child process

After the startup process is started using supervisord management, when you use / usr/local/tomcat/shutdown.sh or kill $PID, supervisord will think that it is an unexpected shutdown and will automatically pull up the process again, unless you use the supervisord command to shut down

# supervisord starts supervisord-c / etc/supervisord.conf # starts the supervisord process. We set the autostart=true parameter in the configuration file. When supervisord starts, tomcat also starts ps-ef. | grep java # check whether tomcat is started.

Program management

Supervisorctl status tomcat # tomcat status supervisorctl stop tomcat # stop tomcat supervisorctl start tomcat # start tomcat supervisorctl restart tomcat # restart tomcat supervisorctl reoload tomcat # restart tomcat

Redis is managed by Supervisor

If redis does not add daemonize yes parameters to the configuration file by default, the foreground starts, so the redis configuration file can also be managed by our Supervisor as follows:

Cat redis6001.conf port 6001 bind 192.168.31.230 protected-mode yes pidfile "/ usr/local/redis/run/redis6001.pid" loglevel notice logfile "/ usr/local/redis/logs/redis6001.log" save 9001 stop-writes-on-bgsave-error yes rdbcompression yes rdbchecksum yes dbfilename dump.rdb dir "/ usr/local/redis/data/rdb/" timeout 0 tcp-keepalive

Write a case where redis is managed by Supervisor

Vim / etc/supervisord.d/redis.conf [program:redis] directory=/usr/local/redis command=/usr/local/redis/bin/redis-server / usr/local/redis/etc/redis6001.conf autostart=true startsecs=10 autorestart=true startretries=3 user=root priority=999 stopsignal=INT redirect_stderr=true stdout_logfile_maxbytes=200MB stdout_logfile_backups = 100stdout_logfile=/usr/local/redis/logs/redis6001.log stopasgroup=false killasgroup=false

Start redis using super

# close tomcat supervisorctl stop tomcat tomcat: stopped # Kill supervisord ps-ef | grep supervisord root 269271010:47?00:00:00/usr/bin/python / bin/supervisord-c / etc/supervisord.conf root 2754927402011 pts/200:00:00 grep 07 pts/200:00:00 grep-- color=autosuper kill-926927 # restart supervisord to reload the configuration file. Supervisord will pull both redis and tomcat up by default supervisord-c / etc/supervisord.conf

Program management

Supervisorctl status redis # redis status supervisorctl stop redis # stop redis supervisorctl start redis # start redis supervisorctl restart reids # restart redis supervisorctl reoload redis # reload redis

Program management

Program management

Supervisorctl status all # View all process status supervisorctl stop all # stop all processes supervisorctl start all # start all processes supervisorctl restart all # restart all processes supervisorctl reoload all # reload all processes

Supervisord enables startup configuration

Vim / usr/lib/systemd/system/supervisord.service [Unit] Description=ProcessMonitoringandControlDaemon After=rc-local.service nss-user-lookup.target [Service] Type=forking ExecStart=/usr/bin/supervisord-c / etc/supervisord.conf [Install] WantedBy=multi-user.targetsystemctl enable supervisord systemctl is-enabled supervisord here, I believe you have a deeper understanding of "how to install the Linux process management tool Supervisor". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.