Transmission-daemon doesn't bind rpc port
All this is useless reading - jump straight to post #16
Hello, I've put together my home file server running debian wheezy and I have problems with transmission daemon rpc, the deamon itself is running but the server is not listening on the rpc port set in settings.json. Then I found out that settings.json is: Code:
- rw------- debian-transmission debian-transmission settings.json Code:
# chmod 660 settings.json Code:
- rw-rw---- debian-transmission debian-transmission settings.json Can anyone please help me? Why do those permissions reset after i reboot? Also, to avoid creating another thread, different sort of question though, in windows, there is Device Manager which shows me all the devices and whether the drivers are installed/mising or there is a conflict on device. Is there any way how can I check this in linux cli? or at least xfce as I don't need gnome/kde/whatever on my server. Thank you for suggestions ;) |
So is your transmission server not running as the debian-transmission user ? Permissions won't change themselves so it's probably one of the transmission applications doing it
|
with kbp on this
transmission deamon should be started with user debian-transmission. How are you starting it? |
hmm, as I am quite noob, I don't know to determine this, but I guess you want to know what ps -aux | grep transmission-daemon shows:
Code:
105 2074 0.0 0.0 91388 2552 ? Ss1 08:29 0:00 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info EDIT: How do I know how do I start it? How would I change the process owner if I need to? |
that looks good to me
when you install transmission-daemon in Debian it defaults to configuring the service to start, you can find the startup script here /etc/init.d/transmission-daemon some background reading here https://wiki.debian.org/Daemon I have to admit, I currently don't understand what is going wrong for you, it should be working 'as is' and regards your other question, the best I can think of right now is Code:
lspci -k |
yes, that's what I thought, when I do
Code:
# /etc/init.d/transmission-daemon restart |
OK ... nothing worked so I reinstalled the system and it doesn't work on clean install either ...
I noticed that /etc/transmission-daemon's rights are drwxrws--- (what does the 's' stand for?) tried chmod 770 but there is still the 's' right instead of 'x' for the owner which is debian-transmission stat %a transmission-daemon says - Access: (2770/drwxrws---) how do I change it to "real" 770? It looks like the user which runs the daemon can't access the file, because can't go into the directory where settings are located |
That's called a sticky bit, setting g+s (group sticky) on a directory means that no matter which user creates a file in the directory it's group will be the same as the directory. This is a way of ensuring that the group who owns the directory will always have access to every file in it.
|
Ok .. reinstalled for 7th (yes, seventh!!!) time, and went step by step
so: 1. clean install of debian 2. after reboot, apt-get update 3. then apt-get install transmission transmission-common transmission-daemon transmission-cli 4. after reboot, netstat shows connection on port 9091 (which is default), but as I have another daemon on NAS running on port 9091, I want to change the port to 9092 5. /etc/init.d/transmission-daemon stop (because I want to change the rpc port in settings.json) 6. now the test, right after "stop" I tried to start the daemon again and restart the computer without making any changes to settings.json, just stop and start the daemon, to see whether it still works 7. after reboot netstat shows no listening on 9091 or 9092 what the hell???????? I did all this via SSH as root where do I make mistake? People, gurus, please help, I start to have grey hair from this |
Quote:
It's unnecessary, but perhaps you realize that now? |
Quote:
|
I do hope that your netstat is
Code:
netstat -a |
Quote:
nope, did netstat -el but tried -a now as well and can't see the port there OK, no more reinstalls, tried to log daemon's activity, at least as much as is offered, here is the log: Code:
[22:34:45.175] Transmission 2.52 (13304) started (session.c:718) Code:
{ |
ok, I'm confused now
earlier we decided that transmission-daemon was running as debian-transmission ( post 4 ) but your log ( post 13 ) it would appear that root is running it... lets see if we can figure out what is going on Code:
sudo sh -x /etc/init.d/transmission-daemon start 2>&1 | grep start-stop Code:
+ start-stop-daemon --start --chuid debian-transmission --exec /usr/bin/transmission-daemon -- --config-dir /var/lib/transmission-daemon/info Code:
sudo service transmission-daemon stop Code:
sudo sh -c "sh -vx /etc/init.d/transmission-daemon start 2>&1 > /path/to/somelog.log" also post the contents of /etc/default/transmission-daemon |
yes, I got exactly what you wrote down, chuid is debian-transmission + all those paths are the same
but I can see where you point, but I was blind or it is way too late here and I'm waaay to tired lol log says something about /root/.config/...... right, it should say /etc/tranmsission..... but I don't know how the hell do I explain to that boody daemon to read from there lol /etc/defaults/trasmission-daemon: Code:
# defaults for transmission-daemon Code:
#!/bin/sh -e EDIT: it's really really late here and I wake up to work in 5 hours so I go sleep and will get back tomorrow to try anything you suggest, thank you for helping btw ;) EDIT2: there is a link in /var/lib/transmission-daemon/info/settings.json -> /etc/transmission-daemon/settings.json |
All times are GMT -5. The time now is 03:21 PM. |