I use Ubuntu 10.04 Server.And use sudo apt-get install transmission-daemon to install transmission-daemon
Then I edit /etc/transmission-daemon/settings.json
Then I use sudo /etc/init.d/transmission-daemon restart.It told me OK.
But I use sudo netstat -antup 9091 is not open .There is only four 51413 opened by transmission-da
Thank you very much!
I don't know there is config file in /var/lib/transmission-daemon/info, the "rpc-enabled" in it is false.Now I can connect it by web ui
so , the settings.json in /etc/transmission-daemon/ is useless?
The settings.json is used by the daemon no doubt about that, the question is: where is the real one?
My guess is that the package builders for Ubuntu did some extra work which is normal, like add a new user to run the daemon as (security feature), add init.d script and parameters file (in /etc/conf.d perhaps? that's the standard but you can see the /etc/init.d/transmission-daemon script to see where it loads the parameters from). One of those parameters defines where the configuration is stored, /var/lib/transmission-daemon doesn't sound like a standard place, the one in /etc/transmission does sound like some kind of standard, but who knows?
If nobody changed the default parameter, then the daemon uses a .transmission directory in the home dir of the user that is running it.
Also remember that the daemon writes to settings.json when its running, each time you change a parameter say through the Web client (speed limits, download directories, etc.) and when it shuts down. Newer versions try to not overwrite parameters you changed in that file, but the only sure way is to stop the daemon, edit the file, then start the daemon... and if the same parameter was specified in the file and in the start-up of the daemon, I think the parameter passed to the daemon wins (it does at least for the speeds which I have as fixed on the start-up and settings.json has as the last speed I set through Qtr or the Web client).
rb07 wrote:The settings.json is used by the daemon no doubt about that, the question is: where is the real one?
My guess is that the package builders for Ubuntu did some extra work which is normal, like add a new user to run the daemon as (security feature), add init.d script and parameters file (in /etc/conf.d perhaps? that's the standard but you can see the /etc/init.d/transmission-daemon script to see where it loads the parameters from). One of those parameters defines where the configuration is stored, /var/lib/transmission-daemon doesn't sound like a standard place, the one in /etc/transmission does sound like some kind of standard, but who knows?
If nobody changed the default parameter, then the daemon uses a .transmission directory in the home dir of the user that is running it.
rb07 wrote:
Also remember that the daemon writes to settings.json when its running, each time you change a parameter say through the Web client (speed limits, download directories, etc.) and when it shuts down. Newer versions try to not overwrite parameters you changed in that file, but the only sure way is to stop the daemon, edit the file, then start the daemon... and if the same parameter was specified in the file and in the start-up of the daemon, I think the parameter passed to the daemon wins (it does at least for the speeds which I have as fixed on the start-up and settings.json has as the last speed I set through Qtr or the Web client).
Transmission only touches settings.json at loading and closing, never in between without a HUP signal. Transmission will completely wipe any changes made to settings.json when it closes.
I need some help as I get an error message (connection refused) when I want to run the transmission web gui. I installed transmission 1.92 on my qnap nas. Unfortunately, I am not familiar with linux, I followed a detailed descreption how to install transmission and what needed to be changed in settings.json.
Runner42 wrote:I need some help as I get an error message (connection refused) when I want to run the transmission web gui.
That "Connection refused" is not coming from transmission-daemon.
I don't know what you mean by "run the transmission web gui".
What exactly are you doing? It sounds like you want to access the web client but are not using the port, i.e. http://<IP-address-of-your-NAS>:9091/ or you installed the daemon but didn't start it.
I don't know what you mean by "run the transmission web gui".
What exactly are you doing? It sounds like you want to access the web client but are not using the port, i.e. http://<IP-address-of-your-NAS>:9091/ or you installed the daemon but didn't start it.[/quote]
I mean I clicked on transmission remote gui twice that I had previously installed. In the tools and options menu I inputted the ip address of my nas, the 9091 port, the user and the password.
I checked it and I was surprised that the transmission daemon had not started. It used to work.
I got this error message:
It is weird. As I said transmission-daemon had used to work. However, that time I could not also run the remote gui. Then I got an error message saying error 403, something wrong with the rpc-whitelist.
In the description that I followed it said I should change from true to false in the row of "rpc-whitelist-enabled": true,
I also tried to input the ip address of my nas in the settings.json row "rpc-whitelist": "127.0.0.1" It did not work either, I got the same error message of 403.
Is even telling you the line where you botched settings.json, I should have seen it in your message above, but its difficult with so much cruft: your rpc-password line is wrong, the value starts with opening quotes, never closes the quotes, and it is missing the comma at the end. Or is it really on the rpc-whitelist-enabled line? did you just change that?
It is weird. As I said transmission-daemon had used to work.
Nothing weird, if the daemon doesn't start you can't communicate with it. If you change something like settings.json and screw up, the daemon doesn't start.
However, that time I could not also run the remote gui. Then I got an error message saying error 403, something wrong with the rpc-whitelist.
In the description that I followed it said I should change from true to false in the row of "rpc-whitelist-enabled": true,
I also tried to input the ip address of my nas in the settings.json row "rpc-whitelist": "127.0.0.1" It did not work either, I got the same error message of 403.
That was just some nonsense, you should try to understand what you are doing, not just follow whatever someone said.
[15:50:29.269] Transmission 2.04 (11151) started (session.c:622)
[15:50:29.269] Couldn't read "/usr/local/etc/transmission/home/stats.json": No such file or directory (utils.c:496)
[15:50:29.269] Couldn't read "/usr/local/etc/transmission/home/stats.benc": No such file or directory (utils.c:496)
[15:50:29.269] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:767)
[15:50:29.269] RPC Server Adding address to whitelist: 127.0.0.* (rpc-server.c:767)
[15:50:29.269] RPC Server Serving RPC and Web requests on port 666 (rpc-server.c:940)
[15:50:29.269] RPC Server Whitelist enabled (rpc-server.c:944)
[15:50:29.269] Bound socket 7 to port 51413 on 0.0.0.0 (net.c:389)
[15:50:29.269] Bound socket 8 to port 51413 on :: (net.c:389)
[15:50:29.269] setrlimit( RLIMIT_NOFILE, 3520 ) (fdlimit.c:846)
[15:50:29.269] socket limit is 240 (fdlimit.c:854)
[15:50:29.269] DHT Initializing DHT (tr-dht.c:330)
[15:50:29.269] Couldn't read "/usr/local/etc/transmission/home/dht.dat": No such file or directory (utils.c:496)
[15:50:29.269] DHT Generating new id (tr-dht.c:378)
[15:50:29.269] DHT DHT initialized (tr-dht.c:409)
[15:50:29.269] LPD Local Peer Discovery disabled (session.c:636)
[15:50:29.269] Using settings from "/usr/local/etc/transmission/home" (daemon.c:443)
[15:50:29.269] Writing 1963 bytes to temporary file "/usr/local/etc/transmission/home/settings.json.tmp.QpHm2M" (bencode.c:1638)
[15:50:29.269] Renaming "/usr/local/etc/transmission/home/settings.json.tmp.QpHm2M" as "/usr/local/etc/transmission/home/settings.json" (bencode.c:1647)
[15:50:29.269] Saved "/usr/local/etc/transmission/home/settings.json" (bencode.c:1651)
[15:50:29.269] Watching "/data/torrents" for new .torrent files (daemon.c:473)
[15:50:29.269] Using readdir to watch directory "/data/torrents" (watch.c:161)
[15:50:29.269] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
[15:50:29.269] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
[15:50:37.284] Port Forwarding (UPnP) upnpDiscover failed (errno 22 - Unknown error: 0) (upnp.c:105)
[15:50:37.284] Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 22 - Unknown error: 0) (upnp.c:125)
[15:50:37.284] Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled! (upnp.c:128)
[15:50:37.284] Port Forwarding Port Forwarding (port-forwarding.c:89)
[15:50:37.284] Port Forwarding (NAT-PMP) readnatpmpresponseorretry failed. natpmp returned -7 (the gateway does not support nat-pmp); errno is 61 (Connection refused) (natpmp.c:72)
[15:50:37.284] Port Forwarding Port Forwarding (port-forwarding.c:89)
[15:51:10.345] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:234)
[15:51:39.399] DHT Finished bootstrapping (tr-dht.c:244)
# transmission-daemon -a 192.168.1.34,192.168.1.35 -r 192.168.1.3 --no-auth -p 666 --watch-dir /data/torrents --incomplete-dir /data/torrents/incomplete --download-dir /data/downloads -f
[16:45:04.858] Transmission 2.04 (11151) started (session.c:622)
[16:45:04.858] RPC Server Adding address to whitelist: 192.168.1.34 (rpc-server.c:767)
[16:45:04.858] RPC Server Adding address to whitelist: 192.168.1.35 (rpc-server.c:767)
[16:45:04.858] RPC Server Serving RPC and Web requests on port 666 (rpc-server.c:940)
[16:45:04.858] RPC Server Whitelist enabled (rpc-server.c:944)
[16:45:04.858] DHT Generating new id (tr-dht.c:378)
[16:45:04.858] Using settings from "/root/.config/transmission-daemon" (daemon.c:443)
[16:45:04.858] Saved "/root/.config/transmission-daemon/settings.json" (bencode.c:1651)
[16:45:04.858] Watching "/data/torrents" for new .torrent files (daemon.c:473)
[16:45:04.859] Using readdir to watch directory "/data/torrents" (watch.c:161)
[16:45:04.859] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
[16:45:04.859] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
ANd I'm able to connect to 666 port.
It even starts in background from command line this way:
Trying 192.168.1.3...
Connected to k.
Escape character is '^]'.
GET
HTTP/1.1 400 Bad Request
Content-Type: text/html
Connection: close
Date: Tue, 04 Jan 2011 09:30:09 GMT
Content-Length: 134
<HTML><HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD><BODY>
<H1>Method Not Implemented</H1>
Invalid method in request<P>
</BODY></HTML>
Connection closed by foreign host.