2017-03-02 13:33:46 -06:00
|
|
|
[supervisord]
|
2017-05-08 17:43:31 -05:00
|
|
|
logfile_maxbytes=1MB
|
|
|
|
|
logfile_backups=2
|
2017-03-02 13:33:46 -06:00
|
|
|
nodaemon=true
|
|
|
|
|
|
2020-03-03 18:50:32 -06:00
|
|
|
[eventlistener:supervisor-proc-exit-listener]
|
|
|
|
|
command=/usr/bin/supervisor-proc-exit-listener --container-name bgp
|
[supervisord] Monitoring the critical processes with supervisord. (#6242)
- Why I did it
Initially, we used Monit to monitor critical processes in each container. If one of critical processes was not running
or crashed due to some reasons, then Monit will write an alerting message into syslog periodically. If we add a new process
in a container, the corresponding Monti configuration file will also need to update. It is a little hard for maintenance.
Currently we employed event listener of Supervisod to do this monitoring. Since processes in each container are managed by
Supervisord, we can only focus on the logic of monitoring.
- How I did it
We borrowed the event listener of Supervisord to monitor critical processes in containers. The event listener will take
following steps if it was notified one of critical processes exited unexpectedly:
The event listener will first check whether the auto-restart mechanism was enabled for this container or not. If auto-restart mechanism was enabled, event listener will kill the Supervisord process, which should cause the container to exit and subsequently get restarted.
If auto-restart mechanism was not enabled for this contianer, the event listener will enter a loop which will first sleep 1 minute and then check whether the process is running. If yes, the event listener exits. If no, an alerting message will be written into syslog.
- How to verify it
First, we need checked whether the auto-restart mechanism of a container was enabled or not by running the command show feature status. If enabled, one critical process should be selected and killed manually, then we need check whether the container will be restarted or not.
Second, we can disable the auto-restart mechanism if it was enabled at step 1 by running the commnad sudo config feature autorestart <container_name> disabled. Then one critical process should be selected and killed. After that, we will see the alerting message which will appear in the syslog every 1 minute.
- Which release branch to backport (provide reason below if selected)
201811
201911
[x ] 202006
2021-01-21 14:57:49 -06:00
|
|
|
events=PROCESS_STATE_EXITED,PROCESS_STATE_RUNNING
|
2020-03-03 18:50:32 -06:00
|
|
|
autostart=true
|
|
|
|
|
autorestart=unexpected
|
|
|
|
|
|
2017-05-08 17:43:31 -05:00
|
|
|
[program:start.sh]
|
|
|
|
|
command=/usr/bin/start.sh
|
|
|
|
|
priority=1
|
|
|
|
|
autostart=true
|
2017-05-09 19:37:08 -05:00
|
|
|
autorestart=false
|
2017-05-08 17:43:31 -05:00
|
|
|
stdout_logfile=syslog
|
|
|
|
|
stderr_logfile=syslog
|
|
|
|
|
|
|
|
|
|
[program:rsyslogd]
|
|
|
|
|
command=/usr/sbin/rsyslogd -n
|
|
|
|
|
priority=2
|
|
|
|
|
autostart=false
|
2020-03-03 18:50:32 -06:00
|
|
|
autorestart=unexpected
|
2017-05-08 17:43:31 -05:00
|
|
|
stdout_logfile=syslog
|
|
|
|
|
stderr_logfile=syslog
|
|
|
|
|
|
2017-03-02 13:33:46 -06:00
|
|
|
[program:gobgpd]
|
|
|
|
|
command=/usr/sbin/gobgpd -p -f /etc/gobgp/gobgpd.conf -r
|
2017-05-08 17:43:31 -05:00
|
|
|
priority=3
|
|
|
|
|
autostart=false
|
2017-05-09 19:37:08 -05:00
|
|
|
autorestart=false
|
2017-05-08 17:43:31 -05:00
|
|
|
stdout_logfile=syslog
|
|
|
|
|
stderr_logfile=syslog
|
|
|
|
|
|
|
|
|
|
[program:fpmsyncd]
|
|
|
|
|
command=fpmsyncd
|
|
|
|
|
priority=5
|
|
|
|
|
autostart=false
|
2017-05-09 19:37:08 -05:00
|
|
|
autorestart=false
|
2017-05-08 17:43:31 -05:00
|
|
|
stdout_logfile=syslog
|
|
|
|
|
stderr_logfile=syslog
|
