Transmission won't start on 9.1

[leszek jaszczak]

Ok, I need a hand, I'm out of ideas. I had Transmission and minidlna running succesfully on Freenas 8.3. I upgraded to 9.1 via the gui upgrade. After the upgrade, I wound up deleting and reinstalling my jails and plugins as the migration was troublesome and I was short on time.
Now minidlna works fine, Transmission will not start. The button stays off, I can't change it to on, no log messages I can find.
I have set up my jail IPs correctly I think as minidlna works. I've setup the transmission information as well.
Anyone have any ideas on why a clean install of transmission via the gui would fail to start? Or where to go next troubleshooting?
Thanks all,

 

[Whattteva]

Yeah, 9.1 plugins system is pretty buggy. You're lucky you actually GET buttons. I can't even get the plugins to work at all from the GUI so I gave up long ago. I have to do everything manually now and basically I just treat it like a normal FreeBSD system cause it's the only way I could get anything to work at all.

 

[dlavigne]

Any errors in /var/log/messages within the jail?

 

[leszek jaszczak]

I'm out of town, will check again and reply end of the week.

 

[Jason Hamilton]

I had an issue with mine where bash was missing from /usr/local/bin within the jail. So a quick cp from the main /usr/bin/bash and I was back in business. Let me know if that helps you.

 

[leszek jaszczak]

Ok, I'm back.

Bash was indeed not present in my Jail directory: /mnt/storage/Jail/usr/local/bin directory. I did a cp from the main /usr/local/bin directory, rebooted with no change. Still can't start Transmission.

I'm not sure about the log. The only messages that may be pertinent are as follows:
Aug 22 21:10:25 freenas manage.py: [py.warnings:193] /usr/local/lib/python2.7/site-packages/django/http/request.py:193: DeprecationWarning: HttpRequest.raw_post_data has been deprecated. Use HttpRequest.body instead. warnings.warn('HttpRequest.raw_post_data has been deprecated. Use HttpRequest.body instead.', DeprecationWarning)
Aug 22 21:10:25 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Aug 22 21:10:28 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v

A bit beyond me.

 

[Jason Hamilton]

I had this issue as well. You might want to try starting transmission by hand. Go into your jail and go to

Code:

cd /usr/pbi/transmission-amd64/etc/rc.d/

then

Code:

./transmission

and see if it throws any errors your way to help you figure out why its not working. Let me know if I can be of more help.

 

[leszek jaszczak]

Ok,
./transmission start yields;
Will not 'start' transmission because transmission_enable is NO.

IfIf I try ./transmission forcestart, I get:
./transmission: WARNING: run_rc_command: cannot run /usr/pbi/transmission-amd64/ bin/transmission-daemon

 

[Whattteva]

This means that you need to edit your /etc/rc.conf file and add the line transmission_enable="YES"
After that, try to start the service again.

 

[leszek jaszczak]

the /etc/rc.conf file:
transmission_enable="YES"
transmission_conf_dir="/usr/pbi/transmission-amd64/etc/transmission/home"
transmission_flags="-e /media "

 

[Whattteva]

Hm, strange.
Try this:
Try to hit the start button on the FreeNAS gui page.
After it fails, login to the jail via jexec and paste the output of /var/log/messages here.

 

[jkh]

Ok, I need a hand, I'm out of ideas. I had Transmission and minidlna running succesfully on Freenas 8.3. I upgraded to 9.1 via the gui upgrade.

9.1 or 9.1.1? 9.1.1 fixes a number of plugin issues. Please try to reproduce this with 9.1.1-RC2.

 

[leszek jaszczak]

Hm, I'm really new to some of this. Let's try.
Ok, got it. I don't have a userlog, I found this in Messages.

Aug 22 21:10:06 bit_1 newsyslog[3237]: logfile first created Aug 22 21:10:06 bit_1 syslogd: kernel boot file is /boot/kernel/kernel
Aug 22 21:10:06 bit_1 root: /etc/rc: WARNING: failed to start transmission
Aug 22 21:10:06 bit_1 su: setpriority 'root' (root): Permission denied
Aug 22 21:10:28 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to
Aug 22 21:23:48 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to
Aug 23 12:47:02 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to
Aug 23 13:41:02 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to
Aug 23 13:42:33 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to
Aug 23 13:51:33 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to

 

[leszek jaszczak]

I was just looking for 9.1.1 yesterday but didn't see it. I'll get it and post reply.

 

[leszek jaszczak]

hmm, the gui upgrade to 9.1.1 RC2 is stuck on "applying database schema changes" for some time now. That has not happened before.
Should I wait longer or restart?

 

[leszek jaszczak]

Update.
I applied 9.1.1 RC2, transmission will not start.
I deleted the plugin/jail and reinstalled it again. Still no luck.

 

[Whattteva]

What are the last few lines that appear in /var/log/messages?

 

[leszek jaszczak]

10 lines in the log:

Aug 23 16:57:34 bit_1 newsyslog[5874]: logfile first created
Aug 23 16:57:34 bit_1 syslogd: kernel boot file is /boot/kernel/kernel
Aug 23 16:57:35 bit_1 su: setpriority 'root' (root): Permission denied
Aug 23 16:58:51 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to start transmission
Aug 23 16:59:23 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to start transmission
Aug 23 16:59:56 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to start transmission
Aug 23 17:00:05 bit_1 root: /usr/local/etc/rc.d/transmission: WARNING: failed to start transmission
Aug 23 17:00:50 bit_1 last message repeated 2 times
Aug 23 17:02:59 bit_1 last message repeated 4 times
Aug 23 17:03:51 bit_1 last message repeated 2 times​

Ok, so this is a process permission problem I think.

 

[leszek jaszczak]

Well, I wound up solving by reinstalling 9.1.1. clean. Problem solved. Thanks all.

 

[MrBerns]

Is there a solution for this that doesn't require a reinstallation? I also have the "bit_1 su: setpriority 'root' (root): Permission denied" issue.