supervisor FATAL Exited too quickly (process log may have details)

Created on 13 Feb 2015  Â·  3Comments  Â·  Source: Supervisor/supervisor

log:

2015-02-13 01:32:25,470 CRIT Supervisor running as root (no user in config file)
2015-02-13 01:32:25,471 INFO RPC interface 'supervisor' initialized
2015-02-13 01:32:25,471 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-02-13 01:32:25,471 INFO supervisord started with pid 5550
2015-02-13 01:32:26,473 INFO spawned: 'shadowsocks' with pid 9378
2015-02-13 01:32:26,564 INFO exited: shadowsocks (exit status 1; not expected)
2015-02-13 01:32:27,566 INFO spawned: 'shadowsocks' with pid 9380
2015-02-13 01:32:27,665 INFO exited: shadowsocks (exit status 1; not expected)
2015-02-13 01:32:29,668 INFO spawned: 'shadowsocks' with pid 9382
2015-02-13 01:32:29,754 INFO exited: shadowsocks (exit status 1; not expected)
2015-02-13 01:32:32,758 INFO spawned: 'shadowsocks' with pid 9384
2015-02-13 01:32:32,845 INFO exited: shadowsocks (exit status 1; not expected)
2015-02-13 01:32:33,846 INFO gave up: shadowsocks entered FATAL state, too many start retries too quickly

config:

[program:shadowsocks]
command=/usr/bin/python /usr/local/bin/ssserver -c /mithril/etc/shadowsocks.json -d start
stdout_logfile=/mithril/log/shadowsocks_stdout.log
stdout_logfile_maxbytes=1MB 
stderr_logfile=/mithril/log/shadowsocks_stderr.log
stderr_logfile_maxbytes=1MB
autostart=true
autorestart=true

Actually, shadowsocks start successfully. But supervisor say FATAL. What should I do??

Most helpful comment

https://github.com/shadowsocks/shadowsocks/blob/master/README.md#usage:

To run in the foreground:

ssserver -c /etc/shadowsocks.json

To run in the background:

ssserver -c /etc/shadowsocks.json -d start
ssserver -c /etc/shadowsocks.json -d stop

You are starting it with -d. Programs run under Supervisor must not daemonize. This is explained in Nondaemonizing of Subprocesses. Run it in the foreground instead.

Please ask general questions about using Supervisor on the mailing list.

All 3 comments

https://github.com/shadowsocks/shadowsocks/blob/master/README.md#usage:

To run in the foreground:

ssserver -c /etc/shadowsocks.json

To run in the background:

ssserver -c /etc/shadowsocks.json -d start
ssserver -c /etc/shadowsocks.json -d stop

You are starting it with -d. Programs run under Supervisor must not daemonize. This is explained in Nondaemonizing of Subprocesses. Run it in the foreground instead.

Please ask general questions about using Supervisor on the mailing list.

I already Run it in the foreground instead,but still show 'FATAL Exited too quickly...'

thanks,
I used "ssserver -c /etc/shadowsocks.json start" is resolved..

Was this page helpful?
0 / 5 - 0 ratings

Related issues

srwilson picture srwilson  Â·  25Comments

mminer picture mminer  Â·  41Comments

felipemachado-sambatech picture felipemachado-sambatech  Â·  74Comments

mkotsalainen picture mkotsalainen  Â·  28Comments

jbrehm picture jbrehm  Â·  64Comments