Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
eromoe opened this issue Feb 13, 2015 · 3 comments
Closed

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

eromoe opened this issue Feb 13, 2015 · 3 comments

Comments

@eromoe
Copy link

eromoe commented Feb 13, 2015

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??

@mnaberez
Copy link
Member

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.

@ScalerYan
Copy link

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

@ghxter
Copy link

ghxter commented Oct 13, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants