Transmission still running after being told to stop

[springs]

Hi all,

Built a new ubuntu server and reinstalled transmission.

I need to edit the settings so i can access it remotely but every time i tell the daemon to stop it keeps restarting itself.

i run: /etc/init.d/transmission-daemon stop

and then /etc/init.d/transmission-daemon status

and it keeps saying that the daemon is still running.

Any ideas?

[rb07]

First: Is it really running? From your description there could be several different programs or scripts not working correctly... better do a "pgrep -l transmission-daemon" to see if it is really running (or look at the daemon's log, it will tell you when it is shutting down).

Second: Use Transmission's own tools:

Code: Select all

transmission-remote --exit
# or
transmission-remote -n <user>:<password> --exit
# or
transmission-remote <remote IP> -n <user>:<password> --exit

To make things clear: the start-up script (/etc/init.d/transmission-daemon) is from your distribution (Ubuntu), not from Transmission. So if it doesn't work correctly you should report it to Ubuntu. "Not working correctly" is either it doesn't stop the daemon, or it doesn't report the real status.

Also if what you say is correct: "keeps restarting" (that means the process ID keeps changing), you should look into other possibilities; something else could be restarting the daemon (or again the start-up script could be so badly made that it uses nohup, or something else to keep the daemon running -- the possibility of stopping didn't came into the mind of whoever wrote that script).

[springs]

the server is up and running and i can access it locally.

trying transmission-remote --exit

comes back as completed and successful but still shows as being up and i can still connect to it.

[rb07]

From what you said, there was a daemon at the default port, but does a second exit command returns an error?

It would be interesting if the "keeps restarting" bit is true... have you checked the PID? (just run "pidof transmission-da")

The log messages would be interesting (not to post here, just for you to look at), is the daemon stopping? is it starting again? Then, as I said, something else is doing that, you have to find out what that "something else" is.

One way to find out if something else is controlling the daemon is by looking at its parent ID, PPID in ps output (the process with that PID is the parent). Instead of using ps, you can also use "pstree -H $(pidof transmission-da)"

[springs]

first time running transmission-remote --exit it comes back ok.

second time it then fails to connect.

third and forth time it then goes back to saying ok.

also when logging back on to the web interface, the web gui is showing previous torrents that were deleted.

now just tried running "service transmission-daemon stop" which reads fine

then checking the status its now showing as stopped.

strange things are happening. not sure why its suddenly started working. didn't check if one or more processes were running at the same time though which might be the issue?

[rb07]

Yes, more than one could be the issue. It would be a case of "last one wins", last to save settings, last to record torrent status.

But if that is/was the case, it would show with ps, or pidof... and the log, the 2nd, and higher instance, would complain about the port(s) being in use.