SystemD должен умереть

Feb 09, 2022 09:44

Как легко возненавидеть systemd:

# supervisorctl status
mmonit RUNNING pid 27782, uptime 12 days, 17:11:27
mmonit_bot RUNNING pid 30322, uptime 4 days, 17:29:36
socat_2812 RUNNING pid 27783, uptime 12 days, 17:11:27
# /etc/init.d/supervisor stop
[ ok ] Stopping supervisor (via systemctl): supervisor.service.

# supervisorctl status
mmonit RUNNING pid 27782, uptime 12 days, 17:11:33
mmonit_bot RUNNING pid 30322, uptime 4 days, 17:29:42
socat_2812 RUNNING pid 27783, uptime 12 days, 17:11:33
# supervisorctl shutdown
Shut down

# supervisorctl status
error: , : file: /usr/lib/python2.7/xmlrpclib.py line: 794

# /etc/init.d/supervisor stop
[ ok ] Stopping supervisor (via systemctl): supervisor.service.
# /etc/init.d/supervisor start
[....] Starting supervisor (via systemctl): supervisor.serviceJob for supervisor.service failed. See 'systemctl status supervisor.service' and 'journalctl -xn' for details.
failed!
# supervisorctl status
mmonit RUNNING pid 24348, uptime 0:00:05
mmonit_bot RUNNING pid 24350, uptime 0:00:05
socat_2812 RUNNING pid 24349, uptime 0:00:05

Ну а дальше регулярные алерты от monit, что ваш, мол, супервизор не запущен.
Previous post
Up