NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
1600dave
Oct 30, 2013Aspirant
Transmission doesn't start when NAS starts up
When my NAS starts up each day at 7am, Transmission is always turned off, Plex starts on its own though. is there any way to make Transmission startup when the NAS turns on?
btaroli
Jan 27, 2014Prodigy
Well, it's sad that we don't get decent access to the systemd journal from the FrontView UI, but you can query it via ssh. I did a simple "cat" output from it and got the following pattern. It clearly is having trouble when systemd launches it during startup, but it's not entirely clear why based on these entries.
FWIW, running 6.1.6RC11 and TransmissionR6 3.00.3
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
fvapp-transmissionr6.service: main process exited, code=killed, status=11
transmission-da[3146]: segfault at 4 ip 00007f909047cc79 sp 00007f908d1dfc60 error 6 in libc-2.13.so[7f90903d5000+180000]
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
fvapp-transmissionr6.service start request repeated too quickly, refusing to start.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
transmission-da[2800]: segfault at 4 ip 00007f2f47655c79 sp 00007f2f443b8c60 error 6 in libc-2.13.so[7f2f475ae000+180000]
fvapp-transmissionr6.service: main process exited, code=killed, status=11
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
fvapp-transmissionr6.service: main process exited, code=killed, status=11
transmission-da[2871]: segfault at 4 ip 00007fbc5eea5c79 sp 00007fbc5bc08c60 error 6 in libc-2.13.so[7fbc5edfe000+180000]
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
fvapp-transmissionr6.service: main process exited, code=killed, status=11
transmission-da[2896]: segfault at 4 ip 00007f35ee40dc79 sp 00007f35eb170c60 error 6 in libc-2.13.so[7f35ee366000+180000]
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
PID file /var/run/transmission-daemon.pid not readable (yet?) after start.
fvapp-transmissionr6.service: main process exited, code=killed, status=11
transmission-da[2957]: segfault at 4 ip 00007f4e2cadac79 sp 00007f4e2983dc60 error 6 in libc-2.13.so[7f4e2ca33000+180000]
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
PID file /var/run/transmission-daemon.pid not readable (yet?) after start.
transmission-da[3058]: segfault at 4 ip 00007fa137de0c79 sp 00007fa134b43c60 error 6 in libc-2.13.so[7fa137d39000+180000]
fvapp-transmissionr6.service: main process exited, code=killed, status=11
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
fvapp-transmissionr6.service: main process exited, code=killed, status=11
transmission-da[3090]: segfault at 4 ip 00007f6842bcec79 sp 00007f683f931c60 error 6 in libc-2.13.so[7f6842b27000+180000]
Stopping bittorrent client transmission-daemon...
Stopping bittorrent client transmission-daemon succeeded
Unit fvapp-transmissionr6.service entered failed state.
fvapp-transmissionr6.service holdoff time over, scheduling restart.
fvapp-transmissionr6.service start request repeated too quickly, refusing to start.
Starting bittorrent client transmission-daemon...
Starting bittorrent client transmission-daemon succeeded
fvapp-transmissionr6.service: Supervising process 4374 which is not our child. We'll most likely not notice when it exits.
FWIW, running 6.1.6RC11 and TransmissionR6 3.00.3
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!