Closed Sab44 closed 3 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Our container uses s6 as the supervisor, which is what you're seeing restart the service when it stops.
We don't recommend using app commands to stop or restart processes inside the container because the app does not know how it is started and often leads to issues you're observing. And we have no control over how the app tries to restart itself.
To restart, you should restart the container.
I see, thanks for the explanation. It is unfortunate that it can lead to this behaviour, but I understand. Going to close the issue then.
Is there an existing issue for this?
Current Behavior
When restarting pyLoad via the web interface on the "Settings" tab (clicking the "Restart pyLoad" button), the docker logs get spammed with
Note: not talking about the pyLoad log visible on the web UI in the
Logs
tab, but the logs inside the docker container as observed by Dockge. There is also a slight but noticeable increase in CPU load observable.It seems, there's some kind of watchdog that implicitly restarts pyLoad if it exits. If I click on the "Quit pyLoad" button, it is also restarted straight away (although without the log spam). So if I click "Restart pyLoad" it is presumably either
Expected Behavior
Restarting pyLoad via the web interface should not cause this loop and spam in the logs.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs