Transmission won't start on 9.1

[bayden]

I ran FreeNAS 9.1.1 x64 from USB and fail to start transmission 2.7.7 too. My HD is fresh and clean and just newly format to ZFS. Got the same error in var/log/messages

Code:

su: setpriority 'root' (root): Permission denied
root: /usr/local/etc/rc.d/transmission: WARNING: failed to start transmission 

Please give me a hand.

 

[jkh]

Please specify the version of the transmission plugin used.

 

[bayden]

Please specify the version of the transmission plugin used.

I am using 2.7.7_1.

 

[jkh]

Transmission was just updated to 2.82; please try that version of the plugin. I don't have the old version of the plugin to test and can only verify the results of the current version (which works as well as transmission generally does).

 

[emk2203]

Transmission was just updated to 2.82; please try that version of the plugin. I don't have the old version of the plugin to test and can only verify the results of the current version (which works as well as transmission generally does).

Just tried. Same as before. Shows 2.82, installs 2.77. Could you attach the .pbi to try it by direct upload?

I am getting a little frustrated here. Several people reported that the supposed Transmission 2.82 version installs in fact 2.77. Could anyone please acknowledge this and investigate? Telling us to install 2.82 in this situation is adding insult to injury.

 

[jkh]

Yeah, that's weird, sorry - looks like something has gone wrong with the freenas-plugins project build process! I'm researching this right now.

 

[emk2203]

Yeah, that's weird, sorry - looks like something has gone wrong with the freenas-plugins project build process! I'm researching this right now.

Thanks. If you could attach the "real" 2.82 .pbi here in the forum, we could install this manually in the meantime until you find the root cause.

 

[jkh]

Yep - what I'm trying to do right now is verify that the *real* 2.82 is actually being built, first. :)

I have a plugin build going as we speak, and it takes awhile (it does an entire buildworld to create the FreeBSD chroot environment for building the plugins, for one thing). As soon as it spits out a transmission plugin, I'll dissect it to make sure the current (2.82) version of the port is being used to build it, and if it passes that test, I'll attach it here.

For those following along at home, you can try this too! Just check out https://github.com/freenas/freenas-plugins.git and type "make". Your machine may even be faster than mine and beat me to it. :)

 

[tecepe]

Same issue still occurs on FreeNAS-9.1.1-RELEASE-x64, Transmission 2.82.

[root@freenas] /mnt/NasStorage/jails/bit_1/var/log# cat messages
Dec 16 04:38:26 bit_1 newsyslog[32896]: logfile first created
Dec 16 04:38:26 bit_1 syslogd: kernel boot file is /boot/kernel/kernel
Dec 16 04:38:26 bit_1 su: setpriority 'root' (root): Permission denied
Dec 16 04:39:26 bit_1 transmission-daemon[34916]: UDP Failed to set receive buffer: No buffer space available (tr-udp.c:59)
Dec 16 04:39:26 bit_1 transmission-daemon[34916]: UDP Failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c:78)

 

[matlock]

I just recently upgraded to 9.3 beta - and was having a similar issue with the transmission plugin not starting. The following is what fixed me...

Bash was not present in the transmission Jail directory:
/mnt/[storage]/Jails/transmission_1/usr/local/bin directory.
Did a copy paste from the main /usr/local/bin directory, rebooted

edited /mnt/[storage]/Jails/transmission_1/etc/rc.conf file and added the line transmission_enable="YES"

went to the plugin page from the web gui and enabled the transmission plugin. I've rebooted several times and the plugin auto starts now and have not had an issue.

Thanks for the suggestions on how to fix this.

 

[redheadedrod]

Running FreeNAS-9.3-STABLE-201506232120 with transmission-2.84_2-amd64 and having same problem.

Can not get it to turn on. I checked the transmission_1/etc/rc.conf file and it already had the transmission_enable="YES" line in it but did not have the bash command.

Copied the bash command over to the transmission_1/usr/local/bin directory. I did not reboot since doing this so I am not sure if that will fix it or not?
Copying many files over to the server at the moment so don't want to reboot just yet.

Not getting anything in the log....

[root@freenas /mnt/Main/jails/transmission_1/var/log]# cat messages
Jul 1 02:06:04 transmission_1 newsyslog[48410]: logfile first created
Jul 1 02:06:04 transmission_1 syslogd: kernel boot file is /boot/kernel/kernel

One more thing...

I tried this and got the following result...
[root@freenas /mnt/Main/jails/transmission_1/usr/pbi/transmission-amd64/etc/rc.d]# ./transmission start
./transmission: WARNING: run_rc_command: cannot run /usr/pbi/transmission-amd64/bin/transmission-daemon

But again I haven't been able to restart the server yet and I had to copy bash over but can't imagine that rebooting it would help with that...

 

[Joshua Parker Ruehlig]

Running FreeNAS-9.3-STABLE-201506232120 with transmission-2.84_2-amd64 and having same problem.

Can not get it to turn on. I checked the transmission_1/etc/rc.conf file and it already had the transmission_enable="YES" line in it but did not have the bash command.

Copied the bash command over to the transmission_1/usr/local/bin directory. I did not reboot since doing this so I am not sure if that will fix it or not?
Copying many files over to the server at the moment so don't want to reboot just yet.

Not getting anything in the log....

[root@freenas /mnt/Main/jails/transmission_1/var/log]# cat messages
Jul 1 02:06:04 transmission_1 newsyslog[48410]: logfile first created
Jul 1 02:06:04 transmission_1 syslogd: kernel boot file is /boot/kernel/kernel

One more thing...

I tried this and got the following result...
[root@freenas /mnt/Main/jails/transmission_1/usr/pbi/transmission-amd64/etc/rc.d]# ./transmission start
./transmission: WARNING: run_rc_command: cannot run /usr/pbi/transmission-amd64/bin/transmission-daemon

But again I haven't been able to restart the server yet and I had to copy bash over but can't imagine that rebooting it would help with that...

you really shouldn't have to do any of the stuff you are trying. starting transmission should be as easy as...
* installing transmission
* starting it on the Plugins > Installed tab

can you try install a new instance of transmission and see if the above steps work for you

 

[redheadedrod]

I just updated to the latest stable release of FreeNAS and rebooted and it is now working.

Now running FreeNAS-9.3-STABLE-201506292130

Not sure if it was the rebooting, updating the version or copying over the bash file but regardless it is now working. Thanks!

Rodney

 

[Joshua Parker Ruehlig]

I just updated to the latest stable release of FreeNAS and rebooted and it is now working.

Now running FreeNAS-9.3-STABLE-201506292130

Not sure if it was the rebooting, updating the version or copying over the bash file but regardless it is now working. Thanks!

Rodney

I can guarantee it's not related to bash. transmission and it's startup script don't use bash.

glad you got it working!

 

[Elixir2]

DUDE! I found the solution to this. I admit, I only read about half of this thread, because you guys were leading me in the wrong direction.
Sorry if I am resurrecting a year-old thread, but it needs to be done.

Here's the problem: both Transmission and some other plugin you have (in my case it was Plex) have the same MAC address on their IP. If you try to set Transmission as a static IP address in the Jails (i.e. turn of DHCP), then you can fool yourself into thinking that you have fixed it. I forced Transmission and Plex to have separate, distinct IP addresses. But Transmission STILL WON'T START.

So I originally had them both set DHCP, so I put it back that way, and f*ck if they didn't both have the same IP address again... I went to my server (router in your cases) and looked at the MAC address reservations I had previously put in there. Plex was 02ffb000050b and Transmission was 02ffb000060b. I went back to the Jails and looked and lo and behold they were both set to the same MAC. Once I corrected that and restarted both Jails, the Plugins were fixed, and auto-started instantly.

Also, the reported bug of SLOW LOADING on the installed Plugins tab... this is the cause of that too. Fix your MAC addresses, and a new bug should be introduced that each new plugin should get a unique MAC address, not the same one as appears to be happening in FreeNAS 9.10.

 

[Nogz]

DUDE! I found the solution to this. I admit, I only read about half of this thread, because you guys were leading me in the wrong direction.
Sorry if I am resurrecting a year-old thread, but it needs to be done.

Here's the problem: both Transmission and some other plugin you have (in my case it was Plex) have the same MAC address on their IP. If you try to set Transmission as a static IP address in the Jails (i.e. turn of DHCP), then you can fool yourself into thinking that you have fixed it. I forced Transmission and Plex to have separate, distinct IP addresses. But Transmission STILL WON'T START.

So I originally had them both set DHCP, so I put it back that way, and f*ck if they didn't both have the same IP address again... I went to my server (router in your cases) and looked at the MAC address reservations I had previously put in there. Plex was 02ffb000050b and Transmission was 02ffb000060b. I went back to the Jails and looked and lo and behold they were both set to the same MAC. Once I corrected that and restarted both Jails, the Plugins were fixed, and auto-started instantly.

Also, the reported bug of SLOW LOADING on the installed Plugins tab... this is the cause of that too. Fix your MAC addresses, and a new bug should be introduced that each new plugin should get a unique MAC address, not the same one as appears to be happening in FreeNAS 9.10.

Can you explain the steps you took to change the mac addresses? I am currently experiencing this problem right now and it is very frustrating.

EDIT: I figured it out.