New Transmission add-on thread

ReadyJabba wrote:
Installed transmissionr6_3.00.3_all.deb on fresh install of 6.0.8 - all default settings. Transmission starts fine, but doesnt start on reboot. Toggle the app off/on and it works. Then fails on reboot again. Any ideas?

Does anyone with 3.00.3 installed have it successfully restart after a reboot?

Anyone with ideas on what I can try? Alternatively, is it possible to trigger start.sh from a url?

I have updated to v3.00.4 (OS6.1.1) and still see the Transmission app fail to restart after reboot. App switch says its on, so I need to toggle twice to start it. After that, it works flawlessly until the next reboot, either manual or scheduled.

And suggestions on how to debug, logs to check?

Will take a look

Hi,

Transmission APP has been working fine up until (and including) 2.80, but 2.82 is failing to start. Regular start was failing, so II debugged it down to starting the daemon in foreground mode as:

/usr/local/bin/transmission-daemon --log-debug -f

And it is giving:

"Illegal instruction"

for some weird reason. Same thing does not happen on 2.80 or previous versions

BTW, I have Radiator 4.2.24 on a ReadyNAS NVX Pioneer edition

super-poussin wrote:
Will take a look

Logs from Systemd-journal filtered for Transmission as follows (10:30 was when I initiated NAS reboot with Transmission running ok)

Sep 02 10:30:18 ReadyNAS transmission[6986]: Connect failed
Sep 02 10:30:18 ReadyNAS transmission[6986]: Error connecting to readynasd -2
Sep 02 10:30:18 ReadyNAS transmission[6986]: Error processing nml request
Sep 02 10:30:18 ReadyNAS transmission[6986]: Stopping bittorrent client transmission-daemon...
Sep 02 10:30:24 ReadyNAS transmission[6986]: Stopping bittorrent client transmission-daemon succeeded
Sep 02 10:31:15 ReadyNAS transmission[2318]: Connect failed
Sep 02 10:31:15 ReadyNAS transmission[2318]: Error connecting to readynasd -2
Sep 02 10:31:15 ReadyNAS transmission[2318]: Error processing nml request
Sep 02 10:31:15 ReadyNAS transmission[2318]: Starting bittorrent client transmission-daemon...
Sep 02 10:31:15 ReadyNAS transmission[2318]: Starting bittorrent client transmission-daemon succeeded
Sep 02 10:31:15 ReadyNAS systemd[1]: PID file /var/run/transmission-daemon.pid not readable (yet?) after start.

After reboot, app switch says its on but no connection is possible to Transmission until the app switch is toggled.

Then at 10:40 when I toggle the Transmission switch - at the end of which its working ok.

Sep 02 10:40:20 ReadyNAS transmission[3907]: Stopping bittorrent client transmission-daemon...
Sep 02 10:40:23 ReadyNAS transmission[3907]: Stopping bittorrent client transmission-daemon succeeded
Sep 02 10:40:31 ReadyNAS transmission[3986]: Starting bittorrent client transmission-daemon...
Sep 02 10:40:31 ReadyNAS transmission[3986]: Starting bittorrent client transmission-daemon succeeded
Sep 02 10:40:31 ReadyNAS systemd[1]: fvapp-transmissionr6.service: Supervising process 3996 which is not our child. We'll most likely not notice when it exits.

I've got Transmission 2.82 running on my Duo but for some reason every file it downloads it's setting different permissions over so that when I access it from my Mac I only have Read Only access. If I reset the permissions for the whole share where the download dir is then I can rename/delete/etc the new files/folders again. Any ideas what I need to change to stop this from happening? :?

Thanks,

Sy

Hi. I have a ReadyNAS Duo v1. I am running Radiator 4.1.12, and Transmission v 2.82.

After successfully connecting to Transmission via the Show Web Interface button using Frontview, the next time I tried to connect I couldn't. I now can't connect at all to operate. After a very long time of Waiting for the URL, it wil evenutally connect showing some torrent downloads underway. However, these look different, in that the bar graph is outline only rather than solid. I am unable to delete or pause any of these downloads, and I can't add any new downloads.

I have unsuccessfuly searched this forum and other online sources but can't find anything to fix it. Can anyone help me?

Thanks in advance

Hello everybody,

@markm1111 : I got the same problems, now I have Raidiator 4.2.24 on my Ultra2 and it's work fine.

My Nas is behind a Netgear WNR1000v3 router. Port used by Transmission (2.82) is open on it, but it's very slow...and setup interface says me "Port closed"
When i go to "Canyouseeme.org" port seems to be closed too...

How can I do ??

Thks,

Olivier

Hi all,

I think that i found a solution. not really the solution but the reason why Transmission interface says me "Port closed". I use a satelite connexion and my ping response time is very big, so i think Transmission doesn't have time to have a right answer from server.
I used "Nmap" tool to verify all open/closed port on my network and this tool says me that Transmission port is open !

ps : sorry for my English, i'm french...

Olivier