3

我正在使用 supervisord 在 Docker 中构建一个 tomcat 容器。如果 Dockerfile 中的默认命令是

CMD supervisord -c /etc/supervisord.conf

当我发送 docker stop 命令时,容器成功退出,退出代码为 0。

但是如果我有

CMD ["/run"] 

在 run.sh 中,

supervisord -c /etc/supervisord.conf

docker stop 命令给了我一个退出代码-1。查看日志时,supervisord 似乎没有收到指示退出请求的 SIGTERM。

2014-10-06 19:48:54,420 CRIT Supervisor running as root (no user in config file)
2014-10-06 19:48:54,450 INFO RPC interface 'supervisor' initialized
2014-10-06 19:48:54,451 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-10-06 19:48:54,451 INFO supervisord started with pid 6
2014-10-06 19:48:55,457 INFO spawned: 'tomcat' with pid 9
2014-10-06 19:48:56,503 INFO success: tomcat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

与以前的日志相反,它接收 sigterm 并优雅地退出。

2014-10-06 20:02:59,527 CRIT Supervisor running as root (no user in config file)
2014-10-06 20:02:59,556 INFO RPC interface 'supervisor' initialized
2014-10-06 20:02:59,556 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-10-06 20:02:59,557 INFO supervisord started with pid 1
2014-10-06 20:03:00,561 INFO spawned: 'tomcat' with pid 9
2014-10-06 20:03:01,602 INFO success: tomcat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2014-10-06 20:05:11,690 WARN received SIGTERM indicating exit request
2014-10-06 20:05:11,690 INFO waiting for tomcat to die
2014-10-06 20:05:12,450 INFO stopped: tomcat (exit status 143)

任何帮助表示赞赏。

谢谢, 卡提克

更新

supervisord.conf 文件

[supervisord]
nodaemon=true
logfile=/var/log/supervisor/supervisord.log

[program:mysql]
command=/usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --pid-file=/var/run/mysqld/mysqld.pid
stdout_logfile=/tmp/mysql.log
stderr_logfile=/tmp/mysql_err.log

[supervisorctl]
serverurl=unix:///tmp/supervisor.sock

[unix_http_server]
file=/tmp/supervisor.sock ; path to your socket file

[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
4

1 回答 1

3

当您通过 run.sh 运行进程时,信号仅发送到该进程。除非你是

  1. 竭尽全力向子进程发送信号,例如使用陷阱
  2. 向进程组发送信号。
  3. exec supervisord ...在 run.sh 中做

子进程不会收到信号。

于 2014-10-06T20:09:41.860 回答