Updated and Subsonic Plugin won't switch on

Status
Not open for further replies.

BenH

Cadet
Joined
Nov 30, 2015
Messages
6
Hi,

I've searched to see if this is a known issue but wanted to post here before I raise it as an issue.

I just upgraded FreeNAS to FreeNAS-9.3-STABLE-201511280648

This switched off the Subsonic plugin I was running (5.2.1). I then couldn't turn this plugin back 'on'. I updated the plugin to 5.3 thinking maybe the newer OS required the most recent plugin. Still no joy. The plugin is listed as installed etc but hitting the slider switch shows it thinking for a second or two before remaining 'off'.

If anyone can help that would be great. Otherwise I'll raise it as a ticket to be looked at.

Thanks, Ben
 

BenH

Cadet
Joined
Nov 30, 2015
Messages
6
There's 3 lines referencing subsonic.

Nov 30 08:31:30 freenas manage.py: [freeadmin.navtree:627] An error occurred while unserializing from http://192.168.1.71/plugins/subsonic/3/_s/treemenu: No JSON object could be decoded

Nov 30 08:39:31 freenas manage.py: [common.pipesubr:71] Popen()ing: /sbin/umount -f '/mnt/ZFS/jails_2/subsonic_1/var/music'

Nov 30 08:52:55 freenas manage.py: [common.pipesubr:71] Popen()ing: /sbin/mount_nullfs '/mnt/ZFS/Music/Music' '/mnt/ZFS/jails_2/subsonic_1/var/music'

I'm guessing the first is the issue and the other two are just the jail being mounted etc
 

pirateghost

Unintelligible Geek
Joined
Feb 29, 2012
Messages
4,219
A lot of plugins on my server show as off but they are indeed running just fine.
 

BenH

Cadet
Joined
Nov 30, 2015
Messages
6
Trying to start it in the shell also doesn't work.

[root@freenas ~]# service subsonic start
subsonic does not exist in /etc/rc.d or the local startup
directories (/etc/ix.rc.d /usr/local/etc/rc.d)
 
D

dlavigne

Guest
Was that run in the jail shell or the FreeNAS shell? It should fail in the FreeNAS shell, but not the jail shell.
 

BenH

Cadet
Joined
Nov 30, 2015
Messages
6
Hi dlavigne and thanks.

Yes, I ran it from the FreeNAS shell that time. Woops.

However, running it from the subsonic shell also gives an error.

root@subsonic_1:/ # service subsonic start
Starting subsonic.
su: pam_start: system error
/usr/local/etc/rc.d/subsonic: WARNING: failed to start subsonic

I also tried service -e and get this.

root@subsonic_1:/ # service -e
/etc/rc.d/cleanvar
/etc/rc.d/newsyslog
/etc/rc.d/syslogd
/etc/rc.d/virecover
/etc/rc.d/motd
/usr/local/etc/rc.d/subsonic
/etc/rc.d/cron

Does '/usr/local/etc/rc.d/subsonic' indicate it has started? in which case the question has to be why isn't the jail realising the service is running, no?
 

BenH

Cadet
Joined
Nov 30, 2015
Messages
6
ok. so its not running. just enabled?

root@subsonic_1:/ # service subsonic stop
subsonic not running?​
 
D

dlavigne

Guest
Yeah, -e just indicates that it's good to go in rc.conf. Not sure why you're getting a PAM error that is preventing startup.
 
Status
Not open for further replies.
Top