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 isn't working #12

Closed
nupplaphil opened this issue May 26, 2018 · 1 comment
Closed

Supervisor isn't working #12

nupplaphil opened this issue May 26, 2018 · 1 comment
Labels
Bug Something isn't working

Comments

@nupplaphil
Copy link
Collaborator

nupplaphil commented May 26, 2018

The dockerfiles

aren't usable at the moment :-(

log:

/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.
  'Supervisord is running as root and it is searching '
2018-05-26 15:55:35,868 CRIT Supervisor running as root (no user in config file)
2018-05-26 15:55:37,821 CRIT reaped unknown pid 209)
2018-05-26 15:55:37,834 CRIT reaped unknown pid 164)
[...]

supervisor constantly restarts the php instances and kill them because it doesn't "remember" the pid.

I have the fear that the bin/worker.php usage in the whole docker environment has some flaws and is therefore the reason for the supervisor errors ("zombie-process"es ...)

@nupplaphil nupplaphil added the Bug Something isn't working label May 26, 2018
@nupplaphil
Copy link
Collaborator Author

nupplaphil commented Oct 11, 2018

solved with #30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant