As strange as it sounds, I think I had a bad .torrent file that was bringing it down.

I went in and cleaned out the actual torrent folder and restarted the daemon. It actually started and held. So knowing that everytime it crashed on me before was after I loaded torrents A, B and C, I thought for fun I’d load different torrents instead, and sure enough it took them and held.

So one by one I’ve been loading in more torrents. It’s as slow as orange but still running (one tense moment when the GUI disconnected, but a couple of minutes later it fired back up).

I have deleted torrents A, B and C just to be safe. Could this be a sign of malware in our world?

/mnt/HD_a2 # /ffp/start/transmission.sh stop
Stopping transmission-daemon
killall: transmission-daemon: no process killed

Transmission has been running great for me for two years now, but in the last week some strange issue has come up that I haven’t been able to find a fix for.
I’m running Transmission 2.50 now.
About a week ago I suddenly was unable to connect to Transmission. This was with both the GUI and a web browser. The response in the GUI is “Connection refused”.
I tried a number of solutions found on the web but nothing worked. I’ve uninstalled then reinstalled Transmission several times. I even tried going back to 2.42 but it also gives “Connection refused”.
When I do the reinstall, it actually works for a few minutes. I start adding in torrents and it takes 2 or 3, then I get the connection issue and I can’t do anything with it.
Finally I gave up and decided it was time to upgrade my DNS-323 to a pair of larger drives, which I did, then installed Transmission on a clean pair of drives (RAID 1). Same issue as above; it works for a while then locks me out.
Here’s the relevant portion of the log:
[22:47:01.288] Transmission 2.50 (13236) started (session.c:718)
[22:47:01.289] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:803)
[22:47:01.289] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:997)
[22:47:01.289] RPC Server Whitelist enabled (rpc-server.c:1001)
[22:47:01.290] Couldn’t bind port 51413 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?) (net.c:363)
[22:47:01.290] UDP Couldn’t bind IPv4 socket (tr-udp.c:260)
[22:47:01.290] DHT Generating new id (tr-dht.c:309)
[22:47:01.290] Using settings from “/mnt/HD_a2/.transmission-daemon” (daemon.c:488)
[22:47:01.291] Saved “/mnt/HD_a2/.transmission-daemon/settings.json” (bencode.c:1731)
[22:47:01.291] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:72)
[22:47:01.291] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:72)
[22:47:02.294] Port Forwarding (UPnP) Found Internet Gateway Device “http://192.168.1.1:5555/ctl/IPConn” (upnp.c:202)
[22:47:02.294] Port Forwarding (UPnP) Local Address is “192.168.1.110” (upnp.c:204)
[22:47:02.295] Port Forwarding (UPnP) Port forwarding through “http://192.168.1.1:5555/ctl/IPConn”, service “urn:schemas-upnp-org:service:WANIPConnection:1”. (local address: 192.168.1.110:51413) (upnp.c:279)
[22:47:02.295] Port Forwarding Starting (port-forwarding.c:93)
[22:47:08.330] Port Forwarding Starting (port-forwarding.c:93)
[22:47:11.527] Saved “/mnt/HD_a2/.transmission-daemon/settings.json” (bencode.c:1731)
[22:47:11.528] DHT Not saving nodes, DHT not ready (tr-dht.c:356)
[22:47:11.528] Port Forwarding Stopped (port-forwarding.c:181)
[22:47:11.537] Saved “/mnt/HD_a2/.transmission-daemon/settings.json” (bencode.c:1731)
[22:47:11.538] DHT Not saving nodes, DHT not ready (tr-dht.c:356)
[22:47:11.538] Port Forwarding Stopped (port-forwarding.c:181)
[22:48:40.719] Transmission 2.50 (13236) started (session.c:718)
[22:48:40.719] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:803)
[22:48:40.720] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:803)
[22:48:40.720] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:997)
[22:48:40.720] RPC Server Whitelist enabled (rpc-server.c:1001)
[22:48:40.720] UDP Failed to set receive buffer: requested 4194304, got 208896 (tr-udp.c:75)
[22:48:40.721] UDP Please add the line “net.core.rmem_max = 4194304” to /etc/sysctl.conf (tr-udp.c:80)
[22:48:40.721] UDP Failed to set send buffer: requested 1048576, got 208896 (tr-udp.c:86)
[22:48:40.721] UDP Please add the line “net.core.wmem_max = 1048576” to /etc/sysctl.conf (tr-udp.c:91)
[22:48:40.722] DHT Generating new id (tr-dht.c:309)
[22:48:40.722] Using settings from “/mnt/HD_a2/.transmission-daemon” (daemon.c:488)
[22:48:40.722] Saved “/mnt/HD_a2/.transmission-daemon/settings.json” (bencode.c:1731)
[22:48:40.722] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:72)
[22:48:40.723] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:72)
[22:48:40.723] Port Forwarding (UPnP) Found Internet Gateway Device “http://192.168.1.1:5555/ctl/IPConn” (upnp.c:202)
[22:48:40.723] Port Forwarding (UPnP) Local Address is “192.168.1.110” (upnp.c:204)
[22:48:40.723] Port Forwarding (UPnP) Port forwarding through “http://192.168.1.1:5555/ctl/IPConn”, service “urn:schemas-upnp-org:service:WANIPConnection:1”. (local address: 192.168.1.110:51413) (upnp.c:279)
[22:48:40.724] Port Forwarding Starting (port-forwarding.c:93)
[22:48:47.761] Port Forwarding Starting (port-forwarding.c:93)
[22:48:59.832] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:247)
[22:50:24.333] Searching for web interface file “/home/nobody/.local/share/transmission/web/index.html” (platform.c:542)
[22:50:24.333] Searching for web interface file “/ffp/share/transmission/web/index.html” (platform.c:542)

Any ideas?

Thanks again, by the way, for all of your help in the past. I’m learning Linux via my DNS-323 and loving every minute of it, even when it falls apart!

cp /mnt/HD_a2/.transmission-daemon/settings.json /mnt/HD_a2/.transmission-daemon/settings.json.bkup

If you ever need to restore it because of a typo using vi, then do this

cp /mnt/HD_a2/.transmission-daemon/settings.json.bkup /mnt/HD_a2/.transmission-daemon/settings.json

Thank you for these great instructions

Hi Daniel,

I tried transmission 2.50 last night and everything went well so you are right that something went wrong with your installation.

Next time make sure you stop transmission first (sh /ffp/start/transmission.sh stop). Followed by package upgrade (funpkg -u ). Then start it again (sh /ffp/start/transmission.sh start) ]]> https://www.shadowandy.net/2009/01/transmission-142-for-dns-323.htm#comment-24475 Thu, 01 Mar 2012 01:22:14 +0000 http://18.142.186.164/wp/?p=2636#comment-24475 Well. I just went ahead and uninstalled and reinstalled the whole thing. Apparently the settings.json got corrupted at some point. Now it is working normally. 🙂

Hi Daniel,

I have not tried Transmission 2.50. Let you know when I upgrade it over the weekend.

/mnt/HD_a2 # /ffp/start/transmission.sh start
Starting transmission-daemon
[00:49:09.939] JSON parser failed in /mnt/HD_a2/.transmission-daemon/settings.json at line 1, column 1: “d13:activity-dat”

Any idea of what I could do to fix it?

ian,

You just need to put in the fun_plug.tgz file into Volume_1 and restart the NAS. It should unpack and your fun_plug will be accessible again. Then follow the instructions to set up transmission and you should be good to go.