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
When restarting pyLoad via the web interface on the "Settings" tab (clicking the "Restart pyLoad" button), the docker logs get spammed with
pyload-ng | pyLoad already running with pid xxx
pyload-ng | Connection to localhost (127.0.0.1) 8000 port [tcp/*] succeeded!
pyload-ng | pyLoad already running with pid xxx
pyload-ng | Connection to localhost (127.0.0.1) 8000 port [tcp/*] succeeded!
pyload-ng | pyLoad already running with pid xxx
pyload-ng | Connection to localhost (127.0.0.1) 8000 port [tcp/*] succeeded!
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
restarted by the watchdog, and the "internal" restart mechanism spams the log
restarted by the internal mechanism and the watchdog spams the log
Expected Behavior
Restarting pyLoad via the web interface should not cause this loop and spam in the logs.
Steps To Reproduce
docker compose up with pyload-ng:latest
restart pyLoad on Settings tab in web interface
observe docker logs (e.g. in Dockge)
Environment
- OS: Debian 12
- How docker service was installed: according to official docker documentation
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.
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
The text was updated successfully, but these errors were encountered: