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

rtorrent not responding in docker #62

Closed
anstosa opened this issue Apr 17, 2023 · 2 comments
Closed

rtorrent not responding in docker #62

anstosa opened this issue Apr 17, 2023 · 2 comments

Comments

@anstosa
Copy link

anstosa commented Apr 17, 2023

Flood is running and rtorrent is not responding. Are there more details logs anywhere? UI stuck on loading screen with call to /api/client/settings pending forever
Running in docker.

$ docker logs rtorrent
rTorrent: loading 182 entries from session directory
rTorrent: started, 182 torrents loaded
Caught internal_error: TrackerController cannot set timeout when inactive.
Stack dump not enabled.
rTorrent: loading 248 entries from session directory
rTorrent: started, 248 torrents loaded
Caught internal_error: TrackerController cannot set timeout when inactive.
Stack dump not enabled.
rTorrent: loading 196 entries from session directory
rTorrent: started, 196 torrents loaded
rTorrent: loading 109 entries from session directory
rTorrent: started, 109 torrents loaded
@kannibalox
Copy link
Contributor

You can try enabling the RPC log, which will show the commands that flood is sending to rtorrent:

rpc.log = /<path mounted via docker>/rpc.log

This will have a lot of output, though, and may not tell you exactly why the web UI is stuck.

@anstosa
Copy link
Author

anstosa commented Apr 19, 2023

We had a power failure and upon recovery this is working again 🤷🏽

Thanks for the rpc log tip, I'll use that if it happens again!

@anstosa anstosa closed this as completed Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants