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

INFO gave up: nginx entered FATAL state, too many start retries too quickly #1

Open
qiulang opened this issue Nov 7, 2017 · 1 comment

Comments

@qiulang
Copy link

qiulang commented Nov 7, 2017

When running it on my local machine there is no problem at all. But when I run it on my cloud server I hit the error "INFO gave up: nginx entered FATAL state, too many start retries too quickly"

The full log like these. So do I fix it ?

volume_nginx_1 | 2017-11-07T07:32:42.499776285Z /usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
volume_nginx_1 | 2017-11-07T07:32:42.499833936Z   'Supervisord is running as root and it is searching '
volume_nginx_1 | 2017-11-07T07:32:42.504282056Z 2017-11-07 07:32:42,504 CRIT Supervisor running as root (no user in config file)
volume_nginx_1 | 2017-11-07T07:32:42.504313289Z 2017-11-07 07:32:42,504 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
volume_nginx_1 | 2017-11-07T07:32:42.511939256Z 2017-11-07 07:32:42,511 INFO RPC interface 'supervisor' initialized
volume_nginx_1 | 2017-11-07T07:32:42.511954735Z 2017-11-07 07:32:42,511 CRIT Server 'unix_http_server' running without any HTTP authentication checking
volume_nginx_1 | 2017-11-07T07:32:42.512163271Z 2017-11-07 07:32:42,512 INFO supervisord started with pid 1
volume_nginx_1 | 2017-11-07T07:32:43.518633731Z 2017-11-07 07:32:43,514 INFO spawned: 'nginx' with pid 7
volume_nginx_1 | 2017-11-07T07:32:43.518659543Z 2017-11-07 07:32:43,515 INFO spawned: 'reloader' with pid 8
volume_nginx_1 | 2017-11-07T07:32:43.522218948Z 2017-11-07 07:32:43,521 INFO exited: nginx (exit status 1; not expected)
volume_nginx_1 | 2017-11-07T07:32:44.529624730Z 2017-11-07 07:32:44,528 INFO spawned: 'nginx' with pid 14
volume_nginx_1 | 2017-11-07T07:32:44.529649574Z 2017-11-07 07:32:44,529 INFO success: reloader entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
volume_nginx_1 | 2017-11-07T07:32:44.536281318Z 2017-11-07 07:32:44,536 INFO exited: nginx (exit status 1; not expected)
volume_nginx_1 | 2017-11-07T07:32:46.539262019Z 2017-11-07 07:32:46,538 INFO spawned: 'nginx' with pid 15
volume_nginx_1 | 2017-11-07T07:32:46.546335640Z 2017-11-07 07:32:46,546 INFO exited: nginx (exit status 1; not expected)
volume_nginx_1 | 2017-11-07T07:32:48.529633357Z da39a3ee5e6b4b0d3255bfef95601890afd80709
volume_nginx_1 | 2017-11-07T07:32:48.529672822Z 
volume_nginx_1 | 2017-11-07T07:32:48.533546924Z Test Nginx Configuration failed...
volume_nginx_1 | 2017-11-07T07:32:50.538086967Z 2017-11-07 07:32:50,537 INFO spawned: 'nginx' with pid 23
volume_nginx_1 | 2017-11-07T07:32:50.545469277Z 2017-11-07 07:32:50,545 INFO exited: nginx (exit status 1; not expected)
volume_nginx_1 | 2017-11-07T07:32:51.546902456Z 2017-11-07 07:32:51,546 INFO gave up: nginx entered FATAL state, too many start retries too quickly
@auzty
Copy link
Owner

auzty commented May 12, 2020

i didn't see that error, i just docker build an run without error

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

No branches or pull requests

2 participants