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
- Transmission 2.31 still very slow and now only crashes a couple of times a week, downgrading again to 2.22.
- Let me know if you find the right version that is stable. I have a similar problem, but I arrived there with a different path. I havent tried to debug it like you are.
I had been away for a while and my NAS had remained unused (~4 months). So over the weekend I upgraded to the latest RAIDiator. This caused the Transmission to be unstable. I upgraded to the latest version (2.34b04) and have been downgrading ever since but to no avail.
The symptoms are that the ipaddress:8181 times out, or sometimes I get the UI, but it says it cannot connect. ps -A using ssh shows the transmission threads running. Turning it off and on via front view again solves the problem for about 5 minutes. Then it starts again.
I have reverted to the standard ReadyNAS BT client for the time period, but it doesn't support time shaping. - I have the same problem with crashes as several have reported here. It seems like someone said before, that only some torrents cause this but I havent found the pattern yet. From browwing around the forum this seems pretty well spread, is there any work beeing done on this by the developer? Or is there a different torrent client which is known to be stable?
NASSOO mentioned reverting to the standard BT client. Can someone tell me how to do that on an Ultra? I havent been able to find any info about it (I had a Duo before so I know where it was on that) ObiWan84 wrote: I suspect that the issue is related to https://trac.transmissionbt.com/ticket/4556. Hopefully it will be fixed soon.
I agree with ObiWan84 that it's related to this issue.- Giving the new 2.42 version a try viewtopic.php?f=47&t=24271
- Transmission 2.42 is stable on the ReadyNAS Duo, it now stays up instead of crashing on errors connecting to UDP trackers, which is an improvement. I'll be jumping on the "Cannot connect to UDP" threads now.
- I also having the same problem with Transmission v2.42 on my new ReadyNAS-DUO v1 (Sparc version).
Transmission v2.42 just Kept stopping arbitrarily & freezing the transmission browser & stopped all downloads -- only a reset of Transmission from Front-View would restart it, but it would then just freeze up again! No idea what was causing it.
Ended up downgrading to v2.22 after long & helpful calls in to Netgear...Am monitoring v2.22 now, but so far so good & no freezes!...
Personally cant see much difference between the versions or in normal usability otherwise...Is Transmission v2.42 meant to be better at downloading than v2.22? I haven't noticed much difference & am enjoying less hassle & problems with the older version.
Regards
Baron. - I also having the same problem with Transmission v2.42 on my new ReadyNAS-DUO v1 (Sparc version).
Transmission v2.42 just Kept stopping arbitrarily & freezing the transmission browser & stopped all downloads -- only a reset of Transmission from Front-View would restart it, but it would then just freeze up again! No idea what was causing it.
Ended up downgrading to v2.22 after long & helpful calls in to Netgear...Am monitoring v2.22 now, but so far so good & no freezes!...
Personally cant see much difference between the versions or in normal usability otherwise...Is Transmission v2.42 meant to be better at downloading than v2.22? I haven't noticed much difference & am enjoying less hassle & problems with the older version.
Regards
Baron.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
