Transmission doesn't start when NAS starts up

In the add-ons Transmissiuon and Automatic always says 'On' when I go in there. However Automatic does not work. I have configured it correctly (I guess) but it never asccess's the ShowRSS site to pull the torrents. Is there a log somewhere that can give me a clue as to what is going on. It looks like Automatic is just not working. The automatic.conf file I'm working with is located in the /apps/automatic/config folder. If I rename that file and try to start Automatic it gets an error.

Anyone found a solution to this problem? or is there a way to be able to access frontview and turn on
apps remotely. Through readycloud it says I can only access the admin page when connected to the local network.

Using OS6.1.6 RC9 (and 6.1.5 if I recall correctly), Transmission 3.00.4 doesnt start after scheduled shutdown/restart. Mostly it's in toggled Off state, but occasionally it's toggled On but cant be accessed via browser etc until toggled off/on

6.1.6 RC 10 in RN104 - same problem (after reboot have to start transmission manually).
Poussin, please help!

Hello,

RN104 6.1.5, transmission 3.0.3 works like a charm, except the fact that when I restart the nAS (or shutdown and start some time after)
Transmission is turned off and I have to manually turn it on (in the GUI interface) to get it up and running.

It's a shame because I like it much better than qbittorrent but qbittorrent does start (whan it was already started on shutdown) on restart

I have exactly the same issue on my ReadyNAS 6.1.6RC10 (same issue in 6.1.5 as well). All my other apps started properly when ReadyNAS started (PHP, Wordpress, Plex) but not Transmission Version 3.00.3 that actually is Transmission 2.8.2. My ReadyNAS is set to powerup / powerdown every day at specific time. And every time I have to go to App to toggle Transmission ON.

I looked at /apps/transmissionr6/bin/start.sh TRANSMISSION_ARGS the dir are all there. I don't have /apps/automatic folder though so not sure where the config for apps automatic start is? Not sure if it is in /data/Transmission/config/settings.json ?

I have a similar problem...after reboot of the NAS Transmission is ON in frontview but I cant connect to it.
If I toggle on/off it works again, so I solved it by NOT turn the NAS on and off. :)

still running OS 6.0.8 and Transmission 3.00.3

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.

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

Poussin, please help us :(

6.1.6 RC13 RN 102 same issue here. Was also present in 6.1.5