Firefly web UI unavailable since 9.1.1 update

[brossow]

I applied the GUI update for 9.1.1 last night and ever since my Firefly web admin interface has been unavailable -- just times out eventually. I have restarted the NAS and have restarted both the jail and the Firefly service with no luck in getting the web UI back. Changing the port number for the service is equally useless. The service itself is still working and I can see it in iTunes, but that's only minimally useful if I can't manage it. Everything was working beautifully under 9.1.

Any suggestions? I'm at the neophyte end of the troubleshooting spectrum and appreciate any help you can offer. System info is below.

Thanks,
Brent


System Information
BuildFreeNAS-9.1.1-RELEASE-x64 (a752d35)
PlatformAMD E-350 Processor
Memory7769MB

Plugin name = Firefly
Version = 1696_8
PBI = firefly-1696_8-amd64
Jail = mt-daapd_1

 

[dlavigne]

Within the jail:

• does the firefly port show if you type "sockstat -4"?
• anything in /var/log/messages?

 

[brossow]

I'm embarrassed to say I don't know what you mean by "within the jail." If there's an easy explanation, I'm eager to learn more. If not, I'll just have to do without -- I don't want to be one of those annoying newbies who tries to use something that's way over his head (which, unfortunately, is where I'm at right now). I'm comfortable within the command line with a little guidance.

FWIW, I completely deleted the Firefly plugin and reinstalled it this afternoon and the results are the same. Again, it worked perfectly within 9.1. :(

 

[dlavigne]

No problem, you want to access the command line of the jail: http://doc.freenas.org/index.php/Adding_Jails#Accessing_the_Command_Line_of_a_Jail.

 

[brossow]

Thanks for that. I've set the port to 9000 for Firefly (IP address of the jail is 10.0.1.152) and this is the result of 'sockstat -4':

Code:

USER    COMMAND    PID  FD PROTO  LOCAL ADDRESS        FOREIGN ADDRESS
daapd    mt-daapd  8299  8  tcp4  *:9000                *:*
daapd    mt-daapd  8298  6  udp4  *:23976               *:*
daapd    mt-daapd  8298  7  udp4  *:5353                *:*
root     python2.7 7470  3  tcp4  10.0.1.152:12346      *:*
root     sshd      7285  5  tcp4  *:22                  *:*
root     syslogd   7185  7  udp4  *:514                 *:*

So yes, the Firefly port shows up on the first line.

The following is the content of /var/log/messages following the last reboot of Firefly:

Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Firefly Version svn-1696: Starting with debuglevel 2
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Error opening plugin dir /usr/lib/firefly/plugins. Ignoring
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Error opening plugin dir /usr/lib/mt-daapd/plugins. Ignoring
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Error opening plugin dir /lib/mt-daapd/plugins. Ignoring
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Error opening plugin dir /lib/mt-daapd/plugins. Ignoring
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Error loading plugin /usr/local/lib/mt-daapd/plugins/ssc-script.so: plugin declined to load
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Plugin loaded: rsp/svn-1696
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Plugin loaded: daap/svn-1696
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Starting rendezvous daemon
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8297]: Starting signal handler
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8299]: Initializing database
Sep 3 20:44:35 mt-daapd_1 mt-daapd[8299]: Full reload...
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Starting mp3 scan
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Starting playlist scan
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Updating playlists
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Scanned 0 songs in 0 seconds
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Starting web server from /usr/pbi/firefly-amd64/share/mt-daapd/admin-root on port 9000
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Registering rendezvous names
Sep 3 20:44:36 mt-daapd_1 mt-daapd[8299]: Serving 0 songs. Startup complete in 0 seconds

I'm guessing that the errors opening the various plugin directories (which don't exist; I checked) are the source of the problem. When I said earlier that the service was working and that I could see it in iTunes, I was premature. Yes, I can "see" it in the list of shared music sources in iTunes, but none of my music shows up now. Wishing I had left well enough alone and stayed with 9.1 but I've never had a problem upgrading like this before. :(

 

[brossow]

Well, this is interesting. I just installed a second instance of the Firefly plugin and set it up exactly the same as the first and it seems to be working again. The settings are exactly the same, so perhaps the first installation was corrupted during the upgrade from 9.1 to 9.1.1? (Not possible, since I deleted and reinstalled the plugin after the upgrade.) Not cool, but at least it's working. If it continues to work, I'll delete the first instance and see what happens. Thanks for the advice -- learned some new stuff!

 

[evilandy]

I've upgraded my FreeNAs from 8.2 to 8.3 (then the ZFS pool to 28) and finally FreeNAS 9.1 Release and cannot get Firefly to work.

I've followed the steps from above and looked in to the log via ee

ee /var/log/messages and can see the following:

Oct 12 14:19:48 mt-daapd_1 newsyslog[8281]: logfile first created
Oct 12 14:19:48 mt-daapd_1 syslogd: kernel boot file is /boot/kernel/kernel
Oct 12 14:19:49 mt-daapd_1 su: setpriority 'root' (root): Permission denied
Oct 12 14:27:23 mt-daapd_1 syslogd: exiting on signal 15
Oct 12 14:30:49 mt-daapd_1 syslogd: kernel boot file is /boot/kernel/kernel
Oct 12 14:35:14 mt-daapd_1 syslogd: exiting on signal 15
Oct 12 14:38:53 mt-daapd_1 syslogd: kernel boot file is /boot/kernel/kernel

sockstat -4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root python2.7 3867 3 tcp4 192.168.(number).(number):12346 *:*
root sshd 3653 5 tcp4 *:22 *:*
root syslogd 3564 7 udp4 *:514

As you can see, I'm having problems with the plugin installation.

Any help would be much welcomed.

Thanks,

EA

 

[evilandy]

After trying to delete the plugin, I receive "some error occurred" then lose access to the FreeNAS 9.1 GUI with the message "some error occurred" on every page. Finally, I lose complete connection.

 

[evilandy]

Okay, I changed my jail IP ranges and it's seemed to have fixed the problem. I then deleted the jail and re-installed. I'm not sure why this is a problem since the IP address haven't changed from version 8.2 but it worked.

 

[evilandy]

The other thing I've noticed is that firefly is now in Jail 2.