transmission service fails to start error

[mittens1]

Hi All

Ive have a ReadyNas NV+ and I have installed transmission version 2.22 and had problems, that if I ever stop the service manually through Radiator, I can never restart the service. When I try and start the service, it gives me a "failed to start" error pop up message, however many times I try.

I updated to the beta version also, hoping it would solve the problem, again, it still happens.

The only way Ive managed to get it started again, is to remove the add on, and then reinstall it all over again....

Help appreciated 🙂

Chris

[mittens1]

I've also tried to reboot the device, and this is not working / allowing me to restart the service...

any help is much appreciated. ive searched these forums for a solution, but found nothing that actually fixes the problem 😞

[Wizball]

Hi
ReadyNAs
NV+
Transmission
Transmission_2.23b01.bin
Firmware
4.1.7

I have the same problem here as well.
I though it was because of some edits I was doing to the configuration but tried it with a brand new install not touch the files and get the same problem.
I have changed teh admin password so edited the
transstart.sh
transtop.sh
with notepad++ ensuring the the encoding was ANSI and even tried changing the encoding to UTF8 as another thread has suggested.

any suggestions woudl be much appreciated

[super_poussin]

PM me and provide me ssh access 🙂


Super-Poussin
If you like my add-ons please donate 🙂

[Wizball]

Have tried to PM you but only shows in outbox not in sent messages.

[mittens1]

Hi Super Poussin - Ive sent you a PM, but its also not leaving my outbox...?

[sjw]

Same here since 2.22.
Re-start the NAS and Transmission isn't running.
Start the Service in RAIDiator and it say failed to start - BUT checking in SSH and it has started. Until the next NAS restart and I need to repeat the whole process. On;y realised it had started when I received an email telling me it had finished. Was that sent to the mails listed for other NAS events?

[super_poussin]

sjw wrote:
Same here since 2.22. Re-start the NAS and Transmission isn't running. Start the Service in RAIDiator and it say failed to start - BUT checking in SSH and it has started. Until the next NAS restart and I need to repeat the whole process. On;y realised it had started when I received an email telling me it had finished. Was that sent to the mails listed for other NAS events?

did you check the transtop.sh , and the blocklist.sh to see if the TRANSOPT line is in with correct password ?

[mittens1]

Ive checked that, and that appears to be fine. I havent changed the default password either.

[sjw]

The line in the transtop.sh file is

TRANSOPT=" localhost:8181 -n admin:password1"

- and I've not changed it.
There is no password shown in the blocklist.sh file.
Its contents are:

#!/bin/sh
# *************
# transmissionblocklist update  by super-poussin
# *************
# Variables
#
# Path to transmission-remote
REMOTE="/usr/local/bin/transmission-remote"

# Options to be passed to transmission-remote

# *************



$REMOTE $TRANSOPT --blocklist-update > /c/addons-config/Transmission/blocklist.log

Remember that when I start it via RAIDiator it reports that it failed to start but does indeed start.. - but fails to start automatically on reboot..

[super_poussin]

Add the same TRANSOPT=. Line in blocklist and it will work


Super-Poussin
If you like my add-ons please donate 🙂

[sjw]

OK will add the line

TRANSOPT=" localhost:8181 -n admin:password1"

to the blocklist.sh file and check.

Why wasn't it already in there if it is needed to start at bootup?

[super_poussin]

a problem at install in old version, will check install scrip tagain for sparc

[sjw]

Thanks - that's fixed it. 🙂

[pippotaz]

Hello I have the same problem as mittens on my Duo with Transmission v2.30b04 (clean install) , here are my .sh :

blocklist.sh (blocklist.log is empty)

#!/bin/sh
# *************
# transmissionblocklist update  by super-poussin
# *************
# Variables
#
# Path to transmission-remote
REMOTE="/usr/local/bin/transmission-remote"

# Options to be passed to transmission-remote
TRANSOPT=" localhost:8181 -n admin:password1"
# *************



$REMOTE $TRANSOPT --blocklist-update > /c/addons-config/Transmission/blocklist.log

transtart.sh

#!/bin/sh
# *************
# transmission start  by super-poussin
# *************
# Variables
#
# Path to transmission-remote
REMOTE="/usr/local/bin/transmission-remote"

# Options to be passed to transmission-remote
TRANSOPT=" localhost:8181 -n admin:password1"
# *************



#LIST=`cat /c/addons-config/Transmission/seeding.txt`
#for ID in $LIST; do
#    $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
#done

#LIST=`cat /c/addons-config/Transmission/downloading.txt`
#for ID in $LIST; do
#    $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
#done

#LIST=`cat /c/addons-config/Transmission/idle.txt`
#for ID in $LIST; do
#    $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
#done

transtop.sh

#!/bin/sh
# *************
# transmission stop  by super-poussin
# *************
# Variables
#
# Path to transmission-remote
REMOTE="/usr/local/bin/transmission-remote"

# Options to be passed to transmission-remote
TRANSOPT=" localhost:8181 -n admin:password1"
# *************



    $REMOTE $TRANSOPT --exit

[super_poussin]

everythin is ok in your script file if of course your transmission password is password1.

can you try to install the addon again over the previous one without uninstalling the version

[pippotaz]

Sorry for the late reply, I've tried reinstalling over the existing addon and I can access transmission only until I restart the NAS.

After a restart I cannot access the addon (either trough the interface or via third party software) but vpsinfo shows this:

obody    1292  0.0  0.3 31248 3264 ?        SNs  18:52   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1293  0.0  0.3 31248 3264 ?        SN   18:52   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1294  0.1  0.3 31248 3264 ?        SN   18:52   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1295  0.0  0.3 31248 3264 ?        SN   18:52   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1300  0.0  0.3 31248 3264 ?        RN   18:52   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon



root      1604  0.0  0.2  5536 2096 ?        S    18:58   0:00 /bin/bash /etc/frontview/addons/bin/TRANSMISSION/start.sh
nobody    1626  0.0  0.3 23056 3248 ?        SNs  18:58   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1627  0.0  0.3 23056 3248 ?        SN   18:58   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1628  0.3  0.3 23056 3248 ?        SN   18:58   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
nobody    1632  0.0  0.3 23056 3248 ?        SN   18:58   0:00 /usr/local/bin/transmission-daemon -g /c/addons-config/Transmission/transmission-daemon
root      1651  0.0  0.2  5536 2096 ?        S    18:59   0:00 /bin/sh /c/addons-config/Transmission/blocklist.sh
root      1652  0.0  0.2  6816 2976 ?        S    18:59   0:00 /usr/local/bin/transmission-remote localhost:8181 -n admin:password1 --blocklist-update

[pippotaz]

Nevermind, Installed 2.31 over twice and now it works !

[danone1]

Hello,
I tried to install Transmission 2.42 but get "service Transmission failed to start". Tried also to install twice the same 2.42 bin, but got the same error.
The passwords (settings.json, blocklist.sh, transtart.sh and transtop.sh) are matching with the nas admin.
The transmission client works until I restart my nas NV+.
Dan

[Sym0n1]

Can this bug be fixed? :?

[sjw]

Yeah, get a Synology.
The straw that broke the camel's back was an update that prevented access to all shares (not just for me). Netgear did nothing for weeks - and didn't respond officially.

Switching was the best thing I did. Not even comparable.