Help rTorrent - Debugging Recent Crashes, Debug Log Location?

Status
Not open for further replies.

moreChalk

Passing Basics
Beginner
May 4, 2019
10
1
2
3
QNAP
TVS-x73
Ethernet
1 GbE
Running 0.9.9-0037.

About 2 weeks ago my rTorrent instance has started to crash regularly.
Sessions stay alive about 1 week before crashing.
Prior to this, the app was rock stable and I would only need to stop/restart for firmware upgrades.

In settings, I enabled debugging so as to begin tracing the issue.
2024-09-14 07 31 47.png


If possible, can you point me to where this debug information is captured and stored?
I have a vanilla setup with a Rdownload share.

I looked in
Bash:
/share/Rdownload/logs
but the log files therein didn't hold much.
I suspect the debug is being stored elsewhere.
 
Solution
Interesting -- made the changes to
Code:
include_logs_debug.tpl
and noted my absolute path (in my case /share/ZFS530_DATA/.qpkg/rtorrent/) in case I need to get back to it manually.

Saved, and scheduled a reboot.
Upon reboot, rTorrent just hangs attempting to launch for the last 30 minutes.
2024-09-21 06 59 59.png


In App center, Cancelling the operation, Stop, Start restores Rtorrent.
Was expecting to see more debug logs based on the config update made earlier -- but this is the log folder's file listing:

Code:
[XXXXXXX@YYYYYYYYYYYYY logs]$ ls -al
total 86
drwxrwxrwx  2 admin administrators    19 2024-09-21 07:08 ./
drwxrwxrwx 15 admin administrators    16 2024-09-21 07:25 ../
-rwxrwxrwx  1 admin administrators 30816 2024-09-21 07:17 execute.log*...
I'm curious what will happen if you will disable rtorrent and rename session directory to something else. Will it crash again? I guess some of your session files are corrupted.
 
Think I found the root cause.
I'm running firmware: QuTS hero h5.2.0.2860.
Applied this firmware on 2024-08-31 (which fits the suspected time frame).

The rTorrent service no longer restores itself on reboot under this firmware for whatever reason.

I have this reboot schedule:
2024-09-18 08 44 59.png

I forget why I set up this schedule.
Likely to clean up hanging connections collected throughout the week.

With a empty session folder and just the service running.
This is what I see when inspect the services file within: /share/Rdownload/logs
Code:
[2024-09-14] Start service: php-fpm

[2024-09-14] Start service: rtorrent

init.d/rtorrent: Starting engine program: rtorrent

[2024-09-14] Start service: lighttpd

init.d/lighttpd: Starting web server rtorrent-webserver

[2024-09-18] Stop service: lighttpd

init.d/lighttpd: Stop lighttpd from PID: 19780

[2024-09-18] Stop service: rtorrent

init.d/rtorrent: Stopping engine program: rtorrent

init.d/rtorrent: Socket/Lock file: /share/Rdownload/session/rtorrent.lock

init.d/rtorrent: Stop rtorrent from PID: 30442

init.d/rtorrent: -SIGINT: Sending Term Interrupt signal.

init.d/rtorrent: -SIGINT  ... 180 seconds left

init.d/rtorrent: -SIGINT  ... 179 seconds left

init.d/rtorrent: -SIGINT  ... 178 seconds left

init.d/rtorrent: -SIGINT  ... 177 seconds left

init.d/rtorrent: -SIGINT  ... 176 seconds left

init.d/rtorrent: -SIGINT  ... 175 seconds left

init.d/rtorrent: -SIGINT  ... 174 seconds left

init.d/rtorrent: -SIGINT  ... 173 seconds left

[2024-09-18] Stop service: php-fpm

init.d/php5-fpm: -WAIT 0


init.d/php5-fpm: Gracefully shutting down done.

~

Upon reboot, App Center states rTorrent is restored
2024-09-18 08 55 21.png


But navigating actually navigating to the app's URL results in browser errors.
This is obvious, since none of the underlying services [php-fm, lighttpd, etc.] are not actually running.
2024-09-18 08 55 47.png


For now, I have deleted my reboot schedule.
I have been spoiled by Silas's init scripts always magically working.
 
I'm not sure if firmware has something to do with that issue.

It's better if you could replicate this issue and look for me here same time everyday. I could login to your NAS by SSH through teamviewer session and together with you check whats going on or whats the reason that it crash.

Anyway....
Edit /usr/bin/rtorrent/etc/rtorrent.conf.tpl/include_logs_debug.tpl and uncomment almost all lines, to be like that:
INI:
log.open_file = "rtorrent.debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.debug.log)
log.add_output = "debug", "rtorrent.debug.log"

# extra debug
log.open_file = "rtorrent.connection_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.connection_debug.log)
log.add_output = "connection_debug", "rtorrent.connection_debug.log"

log.open_file = "rtorrent.dht_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.dht_debug.log)
log.add_output = "dht_debug", "rtorrent.dht_debug.log"

log.open_file = "rtorrent.peer_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.peer_debug.log)
log.add_output = "peer_debug", "rtorrent.peer_debug.log"

log.open_file = "rtorrent.rpc_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.rpc_debug.log)
log.add_output = "rpc_debug", "rtorrent.rpc_debug.log"

log.open_file = "rtorrent.storage_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.storage_debug.log)
log.add_output = "storage_debug", "rtorrent.storage_debug.log"

#log.open_file = "rtorrent.thread_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.thread_debug.log)
#log.add_output = "thread_debug", "rtorrent.thread_debug.log"

log.open_file = "rtorrent.tracker_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.tracker_debug.log)
log.add_output = "tracker_debug", "rtorrent.tracker_debug.log"

log.open_file = "rtorrent.torrent_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.torrent_debug.log)
log.add_output = "torrent_debug", "rtorrent.torrent_debug.log"

## DONT UNCOMMENT ME!!!!!!!
# engine debug
# producing huge log file which is slowing down rtorrent - do not turn it on until youre sure
#log.open_file = "rtorrent.socket_debug.log", (cat,[[RT_DOWNLOAD_PATH]]/logs/rtorrent.socket_debug.log)
#log.add_output = "socket_debug", "rtorrent.socket_debug.log"

Once you do that, please apply new rtorrent settings from UI once again by hitting Save settings button.
1726665871642.png


Now once rtorrent crashes please look for log files in Rdownload/logs or in Rdownload/reports and look for latest crash-report*.zip
 
Thank you for the further debug steps.
Will re-setup these conditions unit test for Saturday ~0700 ET/ 1200 UTC and post results.
 
Interesting -- made the changes to
Code:
include_logs_debug.tpl
and noted my absolute path (in my case /share/ZFS530_DATA/.qpkg/rtorrent/) in case I need to get back to it manually.

Saved, and scheduled a reboot.
Upon reboot, rTorrent just hangs attempting to launch for the last 30 minutes.
2024-09-21 06 59 59.png


In App center, Cancelling the operation, Stop, Start restores Rtorrent.
Was expecting to see more debug logs based on the config update made earlier -- but this is the log folder's file listing:

Code:
[XXXXXXX@YYYYYYYYYYYYY logs]$ ls -al
total 86
drwxrwxrwx  2 admin administrators    19 2024-09-21 07:08 ./
drwxrwxrwx 15 admin administrators    16 2024-09-21 07:25 ../
-rwxrwxrwx  1 admin administrators 30816 2024-09-21 07:17 execute.log*
-rwxrwxrwx  1 admin administrators  1125 2024-09-21 07:08 httpd.env*
-rwxrwxrwx  1 admin administrators   431 2024-09-21 07:17 httpd-error.log*
-rwxrwxrwx  1 admin administrators  1345 2024-09-21 07:08 httpd.export*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:08 httpd.out*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:07 php-fpm.log*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent_dht-log.critical*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent_dht-log.debug*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent_dht-log.error*
-rwxrwxrwx  1 admin administrators    37 2024-09-21 07:12 rtorrent_dht-log.warn*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:17 rtorrent init.log*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent-log.error*
-rwxrwxrwx  1 admin administrators   275 2024-09-21 07:17 rtorrent-log.info*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent_storage-log.critical*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent_storage-log.error*
-rwxrwxrwx  1 admin administrators     0 2024-09-21 07:12 rtorrent_tracker-log.error*
-rwxrwxrwx  1 admin administrators   722 2024-09-21 07:17 services*

As a sanity check, I have re-done the test will let Rtorrent attempt to launch itself for an hour to see if it generates any logs
2024-09-21 07 35 30.png


Edit: Looks like QNAP gives up and states the service is "started" on the frontend after ~40 minutes.
In reality the program is not running (original condition)
2024-09-21 08 01 05.png
 
Solution
Status
Not open for further replies.

Users search this thread by keywords

  1. session
  2. Rtorrent