NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Transmission 2.34b04 and RAIDiator 4.1.8 Crashes using UDP
Hi all,
I've updated to RAIDiator 4.1.8 and Transmission 2.34b04, and it works... until I turn on the alternative bandwidth settings, which run from 8am to 2am (i.e. most of the day, but matches the unfiltered & unshaped traffic 2am to 8am window on my Internet service).
From looking at the log, Transmission runs fine while alternative-bandwidth is on, and starts up as scheduled, but at some time during it's run it chrashes, without logging any errors in /var/log/daemon.log, and does not recover. I have to restart it manually from Frontview.
I'd like to change where transmission is logging to, so I'm going to change :/etc/frontview/addons/bin/TRANSMISSION/start.sh to add the parameter
To be sure it would be writable I created it by:
Now, when transmission goes down in my logs (before I changed the logging directory) I see (in this case Transmission seems to have crashed at 02:10):
And no more transmission chatter until I restart it. (My ReadyNAS is called Tardis by the way).
Any advice?
I've updated to RAIDiator 4.1.8 and Transmission 2.34b04, and it works... until I turn on the alternative bandwidth settings, which run from 8am to 2am (i.e. most of the day, but matches the unfiltered & unshaped traffic 2am to 8am window on my Internet service).
From looking at the log, Transmission runs fine while alternative-bandwidth is on, and starts up as scheduled, but at some time during it's run it chrashes, without logging any errors in /var/log/daemon.log, and does not recover. I have to restart it manually from Frontview.
I'd like to change where transmission is logging to, so I'm going to change :/etc/frontview/addons/bin/TRANSMISSION/start.sh to add the parameter
-e /var/log/transmission.log
To be sure it would be writable I created it by:
touch /var/log/transmission.log
chown nobody:nogroup /var/log/transmission.log
Now, when transmission goes down in my logs (before I changed the logging directory) I see (in this case Transmission seems to have crashed at 02:10):
Sep 22 02:08:25 Tardis transmission-daemon[14880]: Ubuntu-11.04.iso IPv4 DHT not ready (broken, 10 nodes) (tr-dht.c:589)
Sep 22 02:08:42 Tardis last message repeated 2 times
Sep 22 02:08:55 Tardis transmission-daemon[14880]: Ubuntu-11.04.iso IPv4 DHT not ready (broken, 8 nodes) (tr-dht.c:589)
Sep 22 02:09:04 Tardis transmission-daemon[14880]: Ubuntu-11.04.iso IPv4 DHT not ready (broken, 8 nodes) (tr-dht.c:589)
Sep 22 02:09:09 Tardis transmission-daemon[14880]:The.Yes.Men.Fix.The.World Announcing to tracker (announcer.c:1516)
Sep 22 02:09:12 Tardis transmission-daemon[14880]: The.Yes.Men.Fix.The.World Got 2 peers from tracker (torrent.c:515)
Sep 22 02:09:12 Tardis transmission-daemon[14880]: The.Yes.Men.Fix.The.World Announce response contained scrape info; rescheduling next scrape to 1800 seconds from now
. (announcer.c:1137)
Sep 22 02:09:12 Tardis transmission-daemon[14880]: Ubuntu-11.04.iso IPv4 DHT not ready (broken, 8 nodes) (tr-dht.c:589)
Sep 22 02:09:47 Tardis last message repeated 3 times
Sep 22 02:10:10 Tardis last message repeated 2 times
Sep 22 04:00:29 Tardis ntpdate[27570]: step time server 120.136.6.133 offset -0.118978 sec
And no more transmission chatter until I restart it. (My ReadyNAS is called Tardis by the way).
Any advice?
18 Replies
Replies have been turned off for this discussion
- Another day, and again Transmission has crashed within 10 minutes of the scheduled coming out of alt-bandwidth mode with no error reported in the logs.
Here's my current config from /addons-config/Transmission/transmission-daemon/settings.json
{
"alt-speed-down": 0,
"alt-speed-enabled": true,
"alt-speed-time-begin": 480,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": true,
"alt-speed-time-end": 120,
"alt-speed-up": 0,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": true,
"blocklist-url": "http://list.iblocklist.com/?list=bt_level1",
"cache-size-mb": 1000,
"dht-enabled": true,
"download-dir": "/media/BitTorrent/",
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 1,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/c/media/BitTorrent/Incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": true,
"max-peers-global": 200,
"message-level": 3,
"open-file-limit": 32,
"peer-congestion-algorithm": "",
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-enabled": 0,
"peer-port-random-high": 65535,
"peer-port-random-low": 1024,
"peer-port-random-on-start": false,
"peer-socket-tos": "default",
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"prefetch-enabled": 0,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"queue-stalled-enabled": true,
"queue-stalled-minutes": 30,
"ratio-limit": 2,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "hashme",
"rpc-port": 8181,
"rpc-url": "/transmission/",
"rpc-username": "admin",
"rpc-whitelist": "*",
"rpc-whitelist-enabled": true,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"seed-queue-enabled": false,
"seed-queue-size": 10,
"speed-limit-down": 400,
"speed-limit-down-enabled": false,
"speed-limit-up": 20,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 0,
"upload-slots-per-torrent": 14,
"utp-enabled": true,
"watch-dir": "/c/media/BitTorrent/sources/",
"watch-dir-enabled": 0
} - Ok, more crashing, but more information:
[12:08:44.396] Found 1 blocklists in "/c/addons-config/Transmission/transmissio
n-daemon/blocklists" (session.c:2238)
[12:08:44.397] Transmission 2.33+ (12861) started (session.c:718)
[12:08:44.397] Cache Maximum cache size set to 1000.0 MiB (64000 blocks) (cache
.c:249)
[12:08:44.397] RPC Server Adding address to whitelist: * (rpc-server.c:805)
[12:08:44.397] RPC Server Serving RPC and Web requests on port 127.0.0.1:8181/transmission/ (rpc-server.c:999)
[12:08:44.397] RPC Server Whitelist enabled (rpc-server.c:1003)
[12:08:44.397] RPC Server Password required (rpc-server.c:1006)
[12:08:44.397] Bound socket 20 to port 51413 on 0.0.0.0 (net.c:373)
[12:08:44.397] UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:75)
[12:08:44.397] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:80)
[12:08:44.397] UDP Failed to set send buffer: requested 1048576, got 524288 (tr-udp.c:86)
[12:08:44.397] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:91)
[12:08:44.398] DHT Initializing DHT (tr-dht.c:276)
Will make those suggeted changes and see what happens. - Disable udp and let me know
super-poussin wrote: Disable udp and let me know
Hmm, there's no item in settings.json or the command line options for disabling UDP, do you mean µTP (utp-enable in settings.json)?
I've checked the transmission wiki https://trac.transmissionbt.com/wiki/EditConfigFiles to be sure...
EDIT: I've checked the Transmission source https://trac.transmissionbt.com/browser ... smission.h and there does not seem to be an option for disabling UDP.- I'm also seeing this error:
[21:02:17.680] Couldn't read "/c/addons-config/Transmission/transmission-daemon/dht.dat": No such file or directory (utils.c:443)
So I've created the file and set the owner to nobody:nogroup - Having made the changes to /etc/sysctl.conf Transmission has stayed up overnight for once.
These are the new entries in sysctl.conf:
net.core.rmem_max = 4094304
net.core.wmem_max = 1048576
I have not disabled UDP as super-poussin suggested. - Right, though this has helped, some torrent files are much more likely to cause crashes.
- Transmission no longer crashes, but the Web and Remote interfaces can not connect to the daemon. Transmission now uses a lot of CPU constantly, top shows it jumps between 60-98% available CPU, but memory is constant at about 5% (so it's not a memory leak).
Restarting transmission restores normal behavior while alt-bandwith is on (and set to 0kb/s) but any active downloding causes the interface to become unresponsive.
I've also discovered that shutting down transmission via the Frontview interface may not shut down all transmission-daemon threads, and often have to kill them from the command line to get a complete shutdown.
It also seems that although Transmission may be running, downloads are not progressing. - After locking myself out of my ReadyNAS and doing a Firmware reset (yay for apt-get upgrade) I've reverted to Transmission 2.31, we'll see what happens from here.
- RAIDator 4.8.1 and Transmission 2.31 is more stable. I think UDP trackers just don't work (so UDP heavy torrents are very slow, and UDP only torrents do nothing), full TCP torrents are as fast as ever. It still crashes sometimes, but not constantly. There may be some residual cruft left from my apt-get mistakes, but I don't have enough alternative storage to do a full factory reset.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
