You are not logged in.
Transmission-daemon recently started having issues stopping on one of my systems. When I reboot the system, I see the following message: "A stop job is running for Transmission BitTorrent Daemon". It takes anywhere from 5-10 minutes to complete, and has no (noticeable) issues starting up. This is only occurring on reboots. It takes seconds for this system to power down, and there are no errors/messages regarding the transmission-daemon (that I could see).
To shut the system down, I used:
sudo shutdown -h nowTo reboot the system, I have used both of these:
sudo shutdown -r now
sudo rebootIf I go to the web console while this message is shown (<hostname>:9091/transmission/web/), I get a message that the connection failed; which indicates the process is stopped.
Also restarting/stopping the process using systemctl hangs for 5-10 minutes at a prompt:
sudo systemctl restart transmission
sudo systemctl stop transmissionHowever, if I cancel while it is loading, the process is no longer running
[mukti@headcrab01 ~]$ ps aux | grep trans
mukti 358 0.0 0.3 2448 736 pts/0 S+ 22:19 0:00 grep transStarting the process is nearly instant
sudo systemctl start transmissionDoes anyone know what this is, or how I could fix it?
If it helps, this is my transmission setting.json file: https://gist.github.com/anonymous/6665800
Last edited by mukti (2013-09-23 03:24:29)
Offline
I think you need to dig through your journal to hopefully see what is getting stuck here.
Offline
journalctl shows no files found:
[mukti@headcrab01 ~]$ journalctl
No journal files were found.So I followed this debugging procedure: http://freedesktop.org/wiki/Software/sy … /#index3h2
I've uploaded the output file here: http://sprunge.us/eObR
From what I've gathered, the important information in this file is the following line:
[ 6672.666196] transmission-da: page allocation failure: order:0, mode:0x20After looking this up a bit, it looks like it may be related to the sysctl.conf change made a few days ago. I actually didn't realize that I had anything in sysctl.conf, so I never moved it to /etc/sysctl.d/99-sysctl.conf. After doing moving it, the system still seems to be having the same issues on a reboot.
EDIT:
I've tried modifying the memory line in /etc/sysctl.d/99-sysctl.conf to double the memory, but I'm still having the same issue:
#vm.min_free_kbytes=8192
vm.min_free_kbytes=16384Last edited by mukti (2013-09-23 05:02:19)
Offline