Environment: centos7+
When using supervisor to provide daemons services, it suddenly appears after a period of time
unix:///tmp/supervisor.sock no such file
The reason for this error is that the linux
system will clean up the TMP
Folder irregularly
Solution:
Before modifying the configuration, the supervisor related processes are stopped
[root@xss-linux-server ~]# ps -aux|grep supervisor
root 12818 0.0 0.0 222308 15440 ? Ss 15:26 0:00 /usr/bin/python /usr/bin/supervisord
root 14251 0.0 0.0 112704 980 pts/0 S+ 15:47 0:00 grep --color=auto supervisor
Kill and supervisor related processes
Open the/etc/Supervisor/supervisor.conf file and modify the [supervisor CTL] configuration section
[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL for a unix socket
This works well
Similar Posts:
- [Solved] Reasons for error in rabbitmq when supervisor starts
- PHP FPM and Nginx start normally, page 502 Error [How to Solve]
- PHP nginx 504 gateway timeout gateway timeout error
- How to Solve MYSQL error “no directory, logging in with home = -“
- MySQL Error: the solution of command not found
- Got permission denied while trying to connect to the Docker daemon socket
- Remember to check the error of no such file or directory in PHP mysqli once
- How to Backup MySQL database regularly
- scrapyd sqlite3.OperationalError: database is locked
- su: cannot set user id: Resource temporarily unavailable