Transmission suddenly stops working

[tekngolong]

Hello,

Transmission (v2.04) has been working fine for me for a couple of months now. I am running RAIDiator 4.1.6 on my ReadyNAS Duo. However, all of a sudden, recently when clicking on the Transmission Interface radio button via ReadyNAS Frontview, I receive the following error in Firefox:


Unable to connect

Firefox can't establish a connection to the server at 192.168.10.103:8181.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.


I've seen other threads where Super-poussin has suggested to 1) restart Transmission or 2) modify the following entries in the settings.json file (which did not work for me):

"rpc-whitelist": "*",
"rpc-whitelist-enabled": true,


Here is my current settings.json file:

{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "/var/local//Downloads",
"encryption": 1,
"incomplete-dir": "/c/addons-config/Transmission/transmission-daemon/Incomplete",
"incomplete-dir-enabled": false,
"lazy-bitfield-enabled": true,
"lpd-enabled": false,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.0000,
"ratio-limit-enabled": false,
"rename-partial-files": true,
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{dd9391aab4a5fdc513ef4cee5bcf49ec870a882aJckOKSV3",
"rpc-port": 9091,
"rpc-username": "",
"rpc-whitelist": "127.0.0.1",
"rpc-whitelist-enabled": true,
"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"speed-limit-down": 100,
"speed-limit-down-enabled": false,
"speed-limit-up": 100,
"speed-limit-up-enabled": false,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 18,
"upload-slots-per-torrent": 14
}


I noticed that "rpc-port": 9091... I tried setting this to 8080 and I still receive the same error message. PLEASE HELP !!!

[borrisl]

I've had similar issues with Transmission. My issues are related to a memory leak with Transmission. If I allow it to run more than a week without restarting it I experience the same crash. I've had to reboot the NAS, restarting the service didn't work for me.

[tekngolong]

I've tried rebooting the NAS multiple times with no luck.

[yjb]

I think that you ended up with a default settings.json file that was recreated after the daemon was not able to find the file. It happened to me after an unexpected shutdown.

This is the default settings.json file (2.04):
{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": true,
"dht-enabled": true,
"download-dir": "/media/BitTorrent/",
"encryption": 1,
"incomplete-dir": "/c/media/BitTorrent/Incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": false,
"max-peers-global": 200,
"message-level": 2,
"open-file-limit": 32,
"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": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.0000,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{d15b146a3063b3ade7d0fecaa9602218a327a8c8gOoal64v",
"rpc-port": 8181,
"rpc-username": "admin",
"rpc-whitelist": "*",
"rpc-whitelist-enabled": true,
"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"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,
"watch-dir": "/c/media/BitTorrent/sources/",
"watch-dir-enabled": 0
}


HTH

[tekngolong]

YJB, were you able to fix the problem. If so, how? What exactly should I modify in my file?

[Deaf_Raiders]

mines is stopped working too

[emilc]

mine also stopped working after i updated the firmware on my dou to 4.1.7. tried starting it says that the service is started but the indicator is still grey. i do not know what too do, tried diffented things. still the same.

[super-poussin]

Réinstal it


Super-Poussin
If you like my add-ons please donate

[M_Pierzon]

I have the exact problem described above. I have tried to reinstall and all the above suggestions, but whitout any luck. If you have any other suggestions I'm all ears.

I have solved the problem. Installed the light version 1.93 - works fine now and I don't think I'll need the new stuff anyway. I'm running it on a Readynas Duo 4.1.8 by the way whithout having upgraded the memory, wich maybee could have been another way to solve the problem as insinuated in another thread.

/Mikael

[grr]

I am having the same problems as you guys, however I have seen a lot of people claiming to solve the problem by doing a "export EVENT_NOEPOLL=1" before starting the client on other NAS devices. Apparantly working well afterwards, but not on mine. I tried adding:

EVENT_NOEPOLL=1
export EVENT_NOEPOLL

at the top in transtart.sh, but that does not seem to have solved it. Are these the actual scripts used by Frontview to start and stop Transmission?

[drm]

Not sure if this is helpful to anyone, but I figured out why my Transmission kept crashing on me.

I stumbled upon Out of Memory errors in /var/syslog. Apparently, Transmission keeps its own disk cache in memory, which is 200 MB by default. This is way too much for the ReadyNAS to handle since it only has 256MB available, which ultimately leads to an out of memory error. Reducing this cache to 20MB fixed the problem for me. I'm not sure yet if this is an optimal setting for the cache size, but that is another story. Hope this helps for any future lost soul searching for answers

The setting is in the settings.json file and is called "cache-size-mb". And here's how I monitored the memory usage after start:

Code: Select all

while [ true ]; do cat /proc/meminfo; sleep .25; clear; done;

Important values are "MemFree" (free available memory) and "Cached" (system level disk cache). As long as "Cached" is a high value, this is ok, because in fact this is available memory too, as disk cache can be expunged immediately. As soon as "SwapFree" is decreasing, you're in trouble.

[drm]

See http://www.readynas.com/forum/viewtopic.php?f=36&t=60375 for even more info regarding this setting, because merely setting it to 20 wouldn't fix it for good