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
These errors are appearing in the rtorrent log. Possibly something wrong with the rtorrent-ps installation?
(13:52:45) rtorrent disk: Starting thread.
(13:52:45) Opened log file.
(13:52:45) Logging to /config/log/rtorrent/rtorrent.log
(13:52:45) rTorrent-PS features NOT active!
(13:52:45) WARNING: Fall-back for 'do' command active (update rTorrent-PS)!
(13:52:45) WARNING: No LAST ACTIVE column (update rTorrent-PS)!
(13:52:45) WARNING: LAST ACTIVE column is static (update rTorrent-PS)!
(13:52:45) WARNING: No LAST XFER column (update rTorrent-PS)!
(13:52:45) WARNING: LAST XFER column is static (update rTorrent-PS)!
(13:52:45) WARNING: No RATIO column (update rTorrent-PS)!
(13:52:45) WARNING: RATIO column is static (update rTorrent-PS)!
(13:52:45) WARNING: No LAST SCRAPE column (update rTorrent-PS)!
(13:52:45) WARNING: LAST SCRAPE column is static (update rTorrent-PS)!
(13:52:45) Ignoring rtorrent.rc.
(13:52:45) rtorrent main: Starting thread.
(13:52:45) rtorrent scgi: Starting thread.
(13:56:44) Scheduled command failed: session_save: Command "session_save" does not exist.
Tested with a completely fresh container to ensure it wasn't a config error on my end.
Possibly unrelated, but I have noticed the auto-tools soemtimes fail to action, with nothing at all appearing in the debug log when failed.
The text was updated successfully, but these errors were encountered:
Thanks for the tip. I have the required snippet in my rtorrent.rc as I used the template provided. I get an ‘ignoring rtorrent.rc’ error in the docker container logs, but as the container accepts all my other parameters and snippets in the .rc file, I assume that’s an error.
Hi all.
These errors are appearing in the rtorrent log. Possibly something wrong with the rtorrent-ps installation?
Tested with a completely fresh container to ensure it wasn't a config error on my end.
Possibly unrelated, but I have noticed the auto-tools soemtimes fail to action, with nothing at all appearing in the debug log when failed.
The text was updated successfully, but these errors were encountered: