Question

我已成功supervisor为beanstalk队列设置{{3}}并且之前正在运行，但在更改密码后突然间，它已不再有效了。我做了（设置）为CentOS release 6.6用户，但现在每当我在root中添加作业时，它都会失败并且跟踪跟踪在日志文件中可用：

queue

现在2014-12-03 00:45:36,017 INFO RPC interface 'supervisor' initialized 2014-12-03 00:45:36,017 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2014-12-03 00:45:36,017 INFO daemonizing the supervisord process 2014-12-03 00:45:36,017 INFO supervisord started with pid 31309 2014-12-03 00:45:37,022 INFO spawned: 'queue' with pid 31317 2014-12-03 00:45:38,023 INFO success: queue entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)包含以下配置：

supervisord.conf

我尽可能地尝试了所有内容，重新启动[unix_http_server] file=/tmp/supervisor.sock ; (the path to the socket file) [supervisord] logfile=/tmp/supervisord.log logfile_maxbytes=50MB logfile_backups=10 loglevel=info pidfile=/tmp/supervisord.pid nodaemon=false minfds=1024 minprocs=200 [rpcinterface:supervisor] supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface [supervisorctl] serverurl=unix:///tmp/supervisor.sock [program:queue] command=/usr/local/bin/php artisan queue:listen --tries=3 --timeout=86400 --sleep=60 directory=/home/***/www/*** // Real path removed for this question autostart=true autorestart=true redirect_stderr=true并重新加载program几次但没有运气。我现在可以做些什么让它再次运作？

更新：如果我手动从终端运行supervisor，那么它可以在前台运行。

Answer 1

尝试

$ ps aux | grep artisan  # get artisan PID
$ sudo kill -2 <PID>
$ ps aux | grep artisan  # verify artisan has shutdown properly - if not use kill -9 in previous step

有时supervisorctl在关闭进程时遇到问题。这可能是因为进程没有侦听SIGINT / SIGTERM，或者因为进程已挂起。在任何一种情况下kill -9都应该强行杀死它，然后你可以使用supervisorctl start program

主管在后台运行，但工作立即失败

1 个答案: