You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/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 ...)
The text was updated successfully, but these errors were encountered:
The dockerfiles
aren't usable at the moment :-(
log:
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 ...)The text was updated successfully, but these errors were encountered: