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
this causes an error to endlessly repeat in the nzbget logs:
ERROR Binding socket failed for 0.0.0.0: ErrNo 98, Address already in use
it appears to be happening because start.sh is calling nzbget in daemon mode, resulting in supervisor thinking the process is dead and eventually giving up with two processing still running:
2016-10-05 22:42:55,838 INFO exited: nzbget (exit status 0; not expected)
2016-10-05 22:42:55,838 DEBG received SIGCLD indicating a child quit
2016-10-05 22:42:55,839 INFO gave up: nzbget entered FATAL state, too many start retries too quickly
running nzbget in console mode results in only one process starting, however the interactive nature of the console pollutes supervisord.log.
The text was updated successfully, but these errors were encountered:
after the container starts there are two nzbget processes running:
this causes an error to endlessly repeat in the nzbget logs:
it appears to be happening because start.sh is calling nzbget in daemon mode, resulting in supervisor thinking the process is dead and eventually giving up with two processing still running:
running nzbget in console mode results in only one process starting, however the interactive nature of the console pollutes supervisord.log.
The text was updated successfully, but these errors were encountered: