If I go into my ReadyNAS (312 x86) 6.1.4 web add-ons I see Transmission 3.00.3. There is a On / Off option. The On is always showing. Does this not mean that Transmission is started? It always says On after a reboot.
What commands are need to be ran from a terminal to verify Transmission and Automatic is running?
Also is there a log file created anywhere to see what Automatic has done. Like when it is supposed to get the RSS feed every x number of minutes, does that trigger an entry into a log file?
I'm a windows user, and have minimal knowledge of UNIX, just enough to get me in trouble 🙂
+1 I see this regularly on my RN314 with 0S6.1.4 and Transmission 3.00.4. Sometimes it starts up...sometimes it doesnt. It didnt this morning, have to go to Apps and toggle off/on (it says its on)
But how do you know if Transmission is not running?
When you try to connect via a client, when you select the app from the dashboard, when you type in the correct url for Transmission into your browser, it doesnt connect.
After you toggle the app switch off then on, they all connect.
Sometimes (rarely) it will say transmission is running (toggled to ON) however I cant access it. If I toggle it off then back on, it works fine. However the majority of the time, when the NAS boots up each day, Plex is on, but transmission is off and needs to be started manually.
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
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. 🙂
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.
Running 6.1.6 on a RN102, just installed version 3.00.5 from poussin's dropbox, but still having the same issues with transmission failing to start when the nas starts.
Could this be a problem with the OS, and not the program? Maybe that is why Poussin has not addressed the issue, But then again this could be a limit to his programming?
I wouldn't dare to speculate... but I have several apps installed and this is the only one that exhibits this behavior. Others I use include PLEX, Automatic, DVBLink...
It's not impossible to imagine it could be an OS interaction, but it's not a system-wide behavior by any means.
Several months ago I bought into the ReadyNAS only to find these limitations. Unable to get Transmission to work properly, and unable to get a RSS feed to work using Automatic. I only had so long to try out the ReadyNAS and I was unable to get those two issues resolved. I returned the ReadyNAS, and bought into the Synology DS214Play. I have no problems with torrent downloads, RSS feeds, and using Plex. I mainly bought the NAS for Plex so the RSS feed and Plex was a must, and I am so pleased with the Synology DS214Play.
