[root@hdss7-22 bin]# supervisorctl update
error: <class ‘xmlrpclib.Fault’>, <Fault 92: “CANT_REREAD: The directory named as part of the path /data/logs/kubernetes/kube-controller-manager/controller.stdout.log does not exist in section ‘program:kube-controller-manager-7-22’ (file: ‘/etc/supervisord.d/kube-conntroller-manager.ini’)”>: file: /usr/lib64/python2.7/xmlrpclib.py line: 794
[root@hdss7-22 bin]# systemctl status supervisord.service
● supervisord.service - Process Monitoring and Control Daemon
Loaded: loaded (/usr/lib/systemd/system/supervisord.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-08-26 19:12:26 CST; 19min ago
Process: 8779 ExecStart=/usr/bin/supervisord -c /etc/supervisord.conf (code=exited, status=0/SUCCESS)
Main PID: 8912 (supervisord)
Tasks: 27
Memory: 368.1M
CGroup: /system.slice/supervisord.service
├─8912 /usr/bin/python /usr/bin/supervisord -c /etc/supervisord.conf
├─9495 /bin/bash /opt/kubernetes/server/bin/kube-apiserver.sh
├─9504 /bin/sh /opt/etcd/etcd-server-startup.sh
├─9505 ./kube-apiserver --apiserver-count 2 --audit-log-path /data/logs/kubernetes/kube-apiserver/audit-log --audit-policy-file ./conf/audi…
└─9522 ./etcd --name etcd-server-7-22 --data-dir /data/etcd/etcd-server --listen-peer-urls https://10.4.7.22:2380 --listen-client-urls http…
Aug 26 19:12:25 hdss7-22.host.com systemd[1]: Starting Process Monitoring and Control Daemon…
Aug 26 19:12:26 hdss7-22.host.com systemd[1]: Started Process Monitoring and Control Daemon.
[root@hdss7-22 bin]# supervisor status
bash: supervisor: command not found…
[root@hdss7-22 bin]# supervisorctl status
etcd-server-7-22 RUNNING pid 9504, uptime 0:20:03
kube-apiserver-7-22 RUNNING pid 9495, uptime 0:20:03
[root@hdss7-22 bin]# ^C
[root@hdss7-22 bin]# supervisorctl reread && supervisorctl update all
ERROR: CANT_REREAD: The directory named as part of the path /data/logs/kubernetes/kube-controller-manager/controller.stdout.log does not exist in section ‘program:kube-controller-manager-7-22’ (file: ‘/etc/supervisord.d/kube-conntroller-manager.ini’)
error: <class ‘xmlrpclib.Fault’>, <Fault 92: “CANT_REREAD: The directory named as part of the path /data/logs/kubernetes/kube-controller-manager/controller.stdout.log does not exist in section ‘program:kube-controller-manager-7-22’ (file: ‘/etc/supervisord.d/kube-conntroller-manager.ini’)”>: file: /usr/lib64/python2.7/xmlrpclib.py line: 794
[root@hdss7-22 bin]# ps aux|grep super
root 8912 0.0 0.1 221884 13024 ? Ss 19:12 0:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisord.conf
root 19526 0.0 0.0 112712 976 pts/0 S+ 19:33 0:00 grep --color=auto super
[root@hdss7-22 bin]# supervisorctl reload
Restarted supervisord
[root@hdss7-22 bin]# supervisorctl status
error: <class ‘xmlrpclib.Fault’>, <Fault 6: ‘SHUTDOWN_STATE’>: file: /usr/lib64/python2.7/xmlrpclib.py line: 794
[root@hdss7-22 bin]# supervisord -c /etc/supervisor/supervisord.conf
Error: could not find config file /etc/supervisor/supervisord.conf
For help, use /usr/bin/supervisord -h
[root@hdss7-22 bin]# supervisorctl status
unix:///var/run/supervisor/supervisor.sock no such file
[root@hdss7-22 bin]# supervisorctl status
unix:///var/run/supervisor/supervisor.sock no such file
[root@hdss7-22 bin]# /usr/bin/supervisord -c /etc/supervisord.conf
Error: The directory named as part of the path /data/logs/kubernetes/kube-controller-manager/controller.stdout.log does not exist in section ‘program:kube-controller-manager-7-22’ (file: ‘/etc/supervisord.d/kube-conntroller-manager.ini’)
For help, use /usr/bin/supervisord -h
[root@hdss7-22 bin]# cd /data/logs/kubernetes/kube-controller-manager/
-bash: cd: /data/logs/kubernetes/kube-controller-manager/: No such file or directory
[root@hdss7-22 bin]# mkdir /data/logs/kubernetes/kube-controller-manager/
[root@hdss7-22 bin]# /usr/bin/supervisord -c /etc/supervisord.conf
[root@hdss7-22 bin]# systemctl status supervisord.service
● supervisord.service - Process Monitoring and Control Daemon
Loaded: loaded (/usr/lib/systemd/system/supervisord.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-08-26 19:33:57 CST; 30min ago
Process: 8779 ExecStart=/usr/bin/supervisord -c /etc/supervisord.conf (code=exited, status=0/SUCCESS)
Main PID: 8912 (code=exited, status=2)
Aug 26 19:12:25 hdss7-22.host.com systemd[1]: Starting Process Monitoring and Control Daemon…
Aug 26 19:12:26 hdss7-22.host.com systemd[1]: Started Process Monitoring and Control Daemon.
Aug 26 19:33:57 hdss7-22.host.com systemd[1]: supervisord.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 26 19:33:57 hdss7-22.host.com systemd[1]: Unit supervisord.service entered failed state.
Aug 26 19:33:57 hdss7-22.host.com systemd[1]: supervisord.service failed.
[root@hdss7-22 bin]# systemctl start supervisord.service
Job for supervisord.service failed because the control process exited with error code. See “systemctl status supervisord.service” and “journalctl -xe” for details.
[root@hdss7-22 bin]# systemctl status supervisord.service
● supervisord.service - Process Monitoring and Control Daemon
Loaded: loaded (/usr/lib/systemd/system/supervisord.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-08-26 20:05:09 CST; 6s ago
Process: 20100 ExecStart=/usr/bin/supervisord -c /etc/supervisord.conf (code=exited, status=2)
Main PID: 8912 (code=exited, status=2)
Aug 26 20:05:09 hdss7-22.host.com systemd[1]: Starting Process Monitoring and Control Daemon…
Aug 26 20:05:09 hdss7-22.host.com supervisord[20100]: Error: Another program is already listening on a port that one of our HTTP servers is con…visord.
Aug 26 20:05:09 hdss7-22.host.com supervisord[20100]: For help, use /usr/bin/supervisord -h
Aug 26 20:05:09 hdss7-22.host.com systemd[1]: supervisord.service: control process exited, code=exited status=2
Aug 26 20:05:09 hdss7-22.host.com systemd[1]: Failed to start Process Monitoring and Control Daemon.
Aug 26 20:05:09 hdss7-22.host.com systemd[1]: Unit supervisord.service entered failed state.
Aug 26 20:05:09 hdss7-22.host.com systemd[1]: supervisord.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@hdss7-22 bin]# find / -name supervisor.sock
/run/supervisor/supervisor.sock
[root@hdss7-22 bin]# unlink /run/supervisor/supervisor.sock
[root@hdss7-22 bin]# systemctl start supervisord.service
[root@hdss7-22 bin]# systemctl status supervisord.service
● supervisord.service - Process Monitoring and Control Daemon
Loaded: loaded (/usr/lib/systemd/system/supervisord.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-08-26 20:05:56 CST; 2s ago
Process: 20146 ExecStart=/usr/bin/supervisord -c /etc/supervisord.conf (code=exited, status=0/SUCCESS)
Main PID: 20151 (supervisord)
Tasks: 28
Memory: 55.8M
CGroup: /system.slice/supervisord.service
├─20151 /usr/bin/python /usr/bin/supervisord -c /etc/supervisord.conf
├─20192 /bin/bash /opt/kubernetes/server/bin/kube-controller-manager.sh
├─20193 /bin/bash /opt/kubernetes/server/bin/kube-scheduler.sh
├─20194 /bin/bash /opt/kubernetes/server/bin/kube-apiserver.sh
├─20195 ./kube-controller-manager --cluster-cidr 172.7.0.0/16 --leader-elect true --log-dir /data/logs/kubernetes/kube-controller-manager -…
├─20197 ./kube-scheduler --leader-elect --log-dir /data/logs/kubernetes/kube-scheduler --master http://127.0.0.1:8080 --v 2
└─20198 ./kube-apiserver --apiserver-count 2 --audit-log-path /data/logs/kubernetes/kube-apiserver/audit-log --audit-policy-file ./conf/aud…
Aug 26 20:05:56 hdss7-22.host.com systemd[1]: Starting Process Monitoring and Control Daemon…
Aug 26 20:05:56 hdss7-22.host.com systemd[1]: Started Process Monitoring and Control Daemon.
[root@hdss7-22 bin]# supervisorctl status
etcd-server-7-22 FATAL Exited too quickly (process log may have details)
kube-apiserver-7-22 FATAL Exited too quickly (process log may have details)
kube-controller-manager-7-22 FATAL Exited too quickly (process log may have details)
kube-scheduler-7-22 FATAL Exited too quickly (process log may have details)
[root@hdss7-22 bin]# supervisorctl update
[root@hdss7-22 bin]# supervisorctl status
etcd-server-7-22 FATAL Exited too quickly (process log may have details)
kube-apiserver-7-22 FATAL Exited too quickly (process log may have details)
kube-controller-manager-7-22 FATAL Exited too quickly (process log may have details)
kube-scheduler-7-22 FATAL Exited too quickly (process log may have details)
[root@hdss7-22 bin]# supervisorctl status
etcd-server-7-22 FATAL Exited too quickly (process log may have details)
kube-apiserver-7-22 FATAL Exited too quickly (process log may have details)
kube-controller-manager-7-22 FATAL Exited too quickly (process log may have details)
kube-scheduler-7-22 FATAL Exited too quickly (process log may have details)
[root@hdss7-22 bin]# reboot
Connection closing…Socket close.
Connection closed by foreign host.
Disconnected from remote host(10.4.7.22) at 20:07:59.
Type `help’ to learn how to use Xshell prompt.
[C:~]$
Connecting to 10.4.7.22:22…
Connection established.
To escape to local shell, press ‘Ctrl+Alt+]’.
Last login: Thu Aug 26 19:20:11 2021 from 10.4.7.1
[root@hdss7-22 ~]# supervisorctl status
etcd-server-7-22 STARTING
kube-apiserver-7-22 STARTING
kube-controller-manager-7-22 STARTING
kube-scheduler-7-22 STARTING
[root@hdss7-22 ~]# supervisorctl status
etcd-server-7-22 RUNNING pid 9404, uptime 0:00:37
kube-apiserver-7-22 RUNNING pid 9403, uptime 0:00:37
kube-controller-manager-7-22 RUNNING pid 9396, uptime 0:00:37
kube-scheduler-7-22 RUNNING pid 9401, uptime 0:00:37
[root@hdss7-22 ~]# ^C