Hi all,
I have an asus wl-500gp, and have been using transmission 2.13 (using oleg firmware, armel ipkg package) quite successfully until recently.
The first symptoms I observed was that while I was editing the json.settings after starting the daemon processes (4 of them ahd all the time, even when working) the values I changes were overwritten, by transmission as it seems. Even if I tried getting something useful in syslog couldn't see anything (loglevel 3 kept overwriting) until I run with "-f"(foreground) option and saw this:
$ transmission-daemon -f
[21:22:41.256] Transmission 2.13 (11501) started (session.c:624)
[21:22:41.264] Couldn't read "/usr/local/root/.config/transmission-daemon/stats.json": No such file or directory (utils.c:506)
[21:22:41.267] Couldn't read "/usr/local/root/.config/transmission-daemon/stats.benc": No such file or directory (utils.c:506)
[21:22:41.267] Cache Maximum cache size set to 2.00 MiB (128 blocks) (cache.c:253)
[21:22:41.268] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:789)
[21:22:41.268] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:962)
[21:22:41.269] RPC Server Whitelist enabled (rpc-server.c:966)
[21:22:41.269] Bound socket 10 to port 51413 on 0.0.0.0 (net.c:415)
[21:22:41.270] Bound socket 11 to port 51413 on :: (net.c:415)
[21:22:41.270] setrlimit( RLIMIT_NOFILE, 1024 ) (fdlimit.c:854)
[21:22:41.270] socket limit is 240 (fdlimit.c:862)
[21:22:41.271] DHT Initializing DHT (tr-dht.c:336)
[21:22:41.271] Couldn't read "/usr/local/root/.config/transmission-daemon/dht.dat": No such file or directory (utils.c:506)
[21:22:41.272] DHT Generating new id (tr-dht.c:384)
[21:22:41.272] DHT DHT initialized (tr-dht.c:411)
[21:22:41.273] Using settings from "/usr/local/root/.config/transmission-daemon" (daemon.c:483)
[21:22:41.273] Saved "/tmp/mnt/disc0_3/transmission/config/settings.json" (bencode.c:1683)
[21:22:41.274] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
[21:22:41.274] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
[21:22:49.346] Port Forwarding (UPnP) upnpDiscover failed (errno 2 - No such file or directory) (upnp.c:105)
[21:22:49.347] Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 0 - Success) (upnp.c:125)
[21:22:49.347] Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled! (upnp.c:128)
[21:22:49.348] Port Forwarding Starting (port-forwarding.c:95)
[21:23:02.476] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:241)
[21:23:24.696] DHT Finished bootstrapping (tr-dht.c:251)
any ideas whats' happening ?
transmission daemon starting but no activity (very low cpu)
Re: transmission daemon starting but no activity (very low c
If you edit settings.json when the daemon is running you should do a:raiderG wrote:The first symptoms I observed was that while I was editing the json.settings after starting the daemon processes (4 of them ahd all the time, even when working) the values I changes were overwritten, by transmission as it seems.
Code: Select all
killall -HUP transmission-daemon
That looks like a mess.raiderG wrote:Using settings from "/usr/local/root/.config/transmission-daemon" (daemon.c:483)
Saved "/tmp/mnt/disc0_3/transmission/config/settings.json" (bencode.c:1683)
But you are not telling us what are the parameters used with the daemon. The ipkg install doesn't leave a start-up script (or at least it didn't the last time I looked at it, which was very long ago), do you use a script? does it set parameters like which user runs transmission, where are the config/download/watch directories?
Re: transmission daemon starting but no activity (very low c
You are right it's a mess, but only that way I could make it so I could see some logs. And by the way I was updating my settings while daemon was stopped (all processes stopped) - no useThat looks like a mess.
But you are not telling us what are the parameters used with the daemon. The ipkg install doesn't leave a start-up script (or at least it didn't the last time I looked at it, which was very long ago), do you use a script? does it set parameters like which user runs transmission, where are the config/download/watch directories?
You see first a location in logs for what transmission-da without -g location_dir does (if specified that as transm-da -f -g /tmp/harddisk/transmission/settings)
when i launched transm-da -f it took the "default" settings.json and I made it a symlink to /tmp/harddisk/transmission/settings. Anyway even without that sym link it was the same.
Re: transmission daemon starting but no activity (very low c
So the only problem is the "no activity"?
None at all? You don't see tracker info for instance. Or is it only your torrents not doing anything?
None at all? You don't see tracker info for instance. Or is it only your torrents not doing anything?
Re: transmission daemon starting but no activity (very low c
I attach now my settings (doesn't let me to attach anything). This time put the settings to "default" location for daemon to take (the one that appears in logs) daemon starts, some CPU usage at start than drops suddenly to 0:
$ transmission-daemon -f
[22:02:51.213] Transmission 2.13 (11501) started (session.c:624)
[22:02:51.221] Couldn't read "/usr/local/root/.config/transmission-daemon/stats.json": No such file or directory (utils.c:506)
[22:02:51.224] Couldn't read "/usr/local/root/.config/transmission-daemon/stats.benc": No such file or directory (utils.c:506)
[22:02:51.224] Cache Maximum cache size set to 2.00 MiB (128 blocks) (cache.c:253)
[22:02:51.225] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:789)
[22:02:51.225] RPC Server Adding address to whitelist: (rpc-server.c:789)
[22:02:51.226] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:789)
[22:02:51.226] Bound socket 9 to port 51413 on 0.0.0.0 (net.c:415)
[22:02:51.227] Bound socket 10 to port 51413 on :: (net.c:415)
[22:02:51.227] setrlimit( RLIMIT_NOFILE, 1024 ) (fdlimit.c:854)
[22:02:51.228] socket limit is 240 (fdlimit.c:862)
[22:02:51.228] DHT Initializing DHT (tr-dht.c:336)
[22:02:51.228] Couldn't read "/usr/local/root/.config/transmission-daemon/dht.dat": No such file or directory (utils.c:506)
[22:02:51.229] DHT Generating new id (tr-dht.c:384)
[22:02:51.229] DHT DHT initialized (tr-dht.c:411)
[22:02:51.230] Using settings from "/usr/local/root/.config/transmission-daemon" (daemon.c:483)
[22:02:51.230] Saved "/tmp/local/root/.config/transmission-daemon/settings.json" (bencode.c:1683)
[22:02:51.231] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
[22:02:51.231] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
[22:02:59.303] Port Forwarding (UPnP) upnpDiscover failed (errno 2 - No such file or directory) (upnp.c:105)
[22:02:59.304] Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 0 - Success) (upnp.c:125)
[22:02:59.304] Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled! (upnp.c:128)
[22:02:59.305] Port Forwarding Starting (port-forwarding.c:95)
[22:03:14.453] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:241)
[22:03:32.633] DHT Finished bootstrapping (tr-dht.c:251)
Also, couldn't find a way to remove my rpv-enabled and the password hash keep rewriting to my settings file (modified it when daemon stopped and after started daemon)
$ transmission-daemon -f
[22:02:51.213] Transmission 2.13 (11501) started (session.c:624)
[22:02:51.221] Couldn't read "/usr/local/root/.config/transmission-daemon/stats.json": No such file or directory (utils.c:506)
[22:02:51.224] Couldn't read "/usr/local/root/.config/transmission-daemon/stats.benc": No such file or directory (utils.c:506)
[22:02:51.224] Cache Maximum cache size set to 2.00 MiB (128 blocks) (cache.c:253)
[22:02:51.225] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:789)
[22:02:51.225] RPC Server Adding address to whitelist: (rpc-server.c:789)
[22:02:51.226] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:789)
[22:02:51.226] Bound socket 9 to port 51413 on 0.0.0.0 (net.c:415)
[22:02:51.227] Bound socket 10 to port 51413 on :: (net.c:415)
[22:02:51.227] setrlimit( RLIMIT_NOFILE, 1024 ) (fdlimit.c:854)
[22:02:51.228] socket limit is 240 (fdlimit.c:862)
[22:02:51.228] DHT Initializing DHT (tr-dht.c:336)
[22:02:51.228] Couldn't read "/usr/local/root/.config/transmission-daemon/dht.dat": No such file or directory (utils.c:506)
[22:02:51.229] DHT Generating new id (tr-dht.c:384)
[22:02:51.229] DHT DHT initialized (tr-dht.c:411)
[22:02:51.230] Using settings from "/usr/local/root/.config/transmission-daemon" (daemon.c:483)
[22:02:51.230] Saved "/tmp/local/root/.config/transmission-daemon/settings.json" (bencode.c:1683)
[22:02:51.231] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
[22:02:51.231] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
[22:02:59.303] Port Forwarding (UPnP) upnpDiscover failed (errno 2 - No such file or directory) (upnp.c:105)
[22:02:59.304] Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 0 - Success) (upnp.c:125)
[22:02:59.304] Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled! (upnp.c:128)
[22:02:59.305] Port Forwarding Starting (port-forwarding.c:95)
[22:03:14.453] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:241)
[22:03:32.633] DHT Finished bootstrapping (tr-dht.c:251)
Also, couldn't find a way to remove my rpv-enabled and the password hash keep rewriting to my settings file (modified it when daemon stopped and after started daemon)
Re: transmission daemon starting but no activity (very low c
if I do transmission-remote -l to list my torrents nothing. I used to be able to see the web interface with nothing in it. But as I described above now seems to have also some issues with rpc enabled/password (i have a hash there for password and cannot get rid of that mess..)rb07 wrote:So the only problem is the "no activity"?
None at all? You don't see tracker info for instance. Or is it only your torrents not doing anything?
Re: transmission daemon starting but no activity (very low c
I have managed to make it accept adding new torrents (solved the issue with web-ui by setting rpc-enabled=true).
I thing that for most of the time the issue for inactivity was because *somehow* even though I have lots of torrents pending and some other big chunk of them for seeding, when you list them with transmission-remote -l or in web-ui you only see the newly added ones. I also added a watch dir like this, where my original pending torrents are also:
"watch-dir": "/tmp/harddisk/transmission/config/torrents",
"watch-dir-enabled": true
In the logs I couldn't see daemon reading that watch folder though. How can I make sure that transm reloads my torrents ? I have huge files in the middle that I want to resume ...Tnx!
I thing that for most of the time the issue for inactivity was because *somehow* even though I have lots of torrents pending and some other big chunk of them for seeding, when you list them with transmission-remote -l or in web-ui you only see the newly added ones. I also added a watch dir like this, where my original pending torrents are also:
"watch-dir": "/tmp/harddisk/transmission/config/torrents",
"watch-dir-enabled": true
In the logs I couldn't see daemon reading that watch folder though. How can I make sure that transm reloads my torrents ? I have huge files in the middle that I want to resume ...Tnx!
Re: transmission daemon starting but no activity (very low c
Try some simple tests:
- Stop the daemon, and make sure you don't have any copy of the daemon running (i.e. killall transmission-daemon);
- Run: transmission-daemon -d The output is the defaults, not interesting but may serve as reference;
- Run: transmission-daemon -d -g /usr/local/root/.config/transmission-daemon Change the directory to one you use, this is important, it should be the directory that has the torrents/ and resume/ subdirs. Check if the settings are correct (compared to your settings.json), in particular check that download-dir is correct;
- Run: transmission-daemon -f -T -g /usr/local/root/.config/transmission-daemon and in a different terminal run "transmission-remote -l"
Re: transmission daemon starting but no activity (very low c
You ran the daemon with different settings.json, the original one stored all its info in one place, then you changed to another and the daemon only sees the info on the new place.raiderG wrote:when you list them with transmission-remote -l or in web-ui you only see the newly added ones
Re: transmission daemon starting but no activity (very low c
Now I managed to run it normally and settings are saved proparly when reloading the settings. But when I want to add an already pending torrent file withrb07 wrote:You ran the daemon with different settings.json, the original one stored all its info in one place, then you changed to another and the daemon only sees the info on the new place.raiderG wrote:when you list them with transmission-remote -l or in web-ui you only see the newly added ones
transmission-remote "torrent"
(where torrent location is the watch-dir from settings) it doesn't report an error but can't see it with list option as pending
Also 'transmission-remote ""torent_notprsent_name" ' does not raise an error .. How to force to reload all my torrents from a folder ?