Open tryoutuser opened 1 year ago
If you have any software that issues the execute
call to rtorrent, that runs directly in the rtorrent process so it may actually be something completely unrelated. You can try enabling the RPC log to see if there's anything happening around the times you see CPU spikes: https://rtorrent-docs.readthedocs.io/en/latest/cmd-ref.html#term-log-xmlrpc
If you have any software that issues the
execute
call to rtorrent, that runs directly in the rtorrent process so it may actually be something completely unrelated.
uh okay. i did execute rtorrent directly by just typing rtorrent
inside a screen session. weird then.
You can try enabling the RPC log to see if there's anything happening around the times you see CPU spikes: https://rtorrent-docs.readthedocs.io/en/latest/cmd-ref.html#term-log-xmlrpc
i afraid it will generate such a huge log file like i've seen in other issues so i didn't enable xmlrpc logging.
By execute
I was referring specifically to the rtorrent calls: https://rtorrent-docs.readthedocs.io/en/latest/cmd-ref.html#execute-commands
i afraid it will generate such a huge log file like I've seen in other issues so i didn't enable xmlrpc logging.
It will definitely generate a big log file, but you don't have to keep it enabled forever, just long enough to catch whatever's causing the issue (hopefully).
rtxmlrpc log.xmlrpc '' /tmp/xmlrpc.log # Open the log
# Figure out the issue
rtxmlrpc log.xmlrpc '' '' # Close the log
The execute log may be smaller and similarly helpful depending on what the root cause is: https://rtorrent-docs.readthedocs.io/en/latest/cmd-ref.html#term-log-execute
are there some ways to ease down cpu usage? i often get some high cpu usage sometimes even on idle just seeding. is there known cause of this?
can anyone answer my question in discussions tab? #1181