Troubleshooting firefly on NV+ v2

(5.3.SMILEY should read 5.3.8....)

I think the 5.3.8 update has overwritten your config file and trashed your settings to a non-working state. I am jumping to this conclusion because mine stopped working about the time of the update from 5.3.7 to 5.3.8.

If you ssh in to the NAS and check /var/log/mt-daapd.log, you'll probably find the database type is not correct (sqlite but it should be sqlite3, plus default paths etc are all reset to useless settings).

Thanks for suggestion, Tony. I took a look at the log file, but the settings seem to be OK. It is sqlite3 and the paths etc all look OK to my non-expert eye. I still can't connect to the firefly homepage.

Cheers,
John

Can you copy the log showing a restart. Here's mine:

2013-10-30 12:26:54 (4035a000): Firefly Version svn-1676: Starting with debuglevel 2
2013-10-30 12:26:54 (4035a000): Plugin loaded: daap/svn-1676
2013-10-30 12:26:54 (4035a000): Plugin loaded: rsp/svn-1676
2013-10-30 12:26:54 (4035a000): Plugin loaded: ssc-script/svn-1676
2013-10-30 12:26:54 (4035a000): Starting rendezvous daemon
2013-10-30 12:26:54 (4035a000): Starting signal handler
2013-10-30 12:26:54 (4035a000): Initializing database
2013-10-30 12:26:54 (4035a000): Full reload...
2013-10-30 12:26:55 (4035a000): Starting web server from /usr/share/mt-daapd/admin-root on port 3689
2013-10-30 12:26:55 (4035a000): Registering rendezvous names
2013-10-30 12:26:55 (4035a000): Serving 0 songs. Startup complete in 1 seconds
2013-10-30 12:26:55 (4035a000): Rescanning database
2013-10-30 12:26:56 (4035a000): Starting playlist scan
2013-10-30 12:26:56 (4035a000): Updating playlists
2013-10-30 12:26:56 (4035a000): Scanned 28 songs (was 0) in 1 seconds

Sorry it has taken me so long to get this done, Tony, but I looked at the log file, and the final entries are as follows:-

2013-07-11 09:05:34 (4035a000): Firefly Version svn-1676: Starting with debuglevel 2
2013-07-11 09:05:34 (4035a000): Plugin loaded: daap/svn-1676
2013-07-11 09:05:34 (4035a000): Plugin loaded: rsp/svn-1676
2013-07-11 09:05:34 (4035a000): Plugin loaded: ssc-script/svn-1676
2013-07-11 09:05:34 (4035a000): Starting rendezvous daemon
2013-07-11 09:05:34 (4035a000): Starting signal handler
2013-07-11 09:05:34 (4035a000): Initializing database
2013-07-11 09:05:36 (4035a000): Starting web server from /usr/share/mt-daapd/admin-root on port 3689
2013-07-11 09:05:36 (4035a000): Registering rendezvous names
2013-07-11 09:05:36 (4035a000): Serving 2556 songs. Startup complete in 2 seconds
2013-07-12 08:02:31 (413d2470): Cannot resolve /usr/share/mt-daapd/admin-root//favicon.ico
2013-07-12 08:02:31 (413d2470): Thread 11: Entering ws_returnerror (404: Not found)
2013-07-12 08:02:31 (413d2470): Cannot resolve /usr/share/mt-daapd/admin-root//favicon.ico
2013-07-12 08:02:31 (413d2470): Thread 12: Entering ws_returnerror (404: Not found)
2013-07-16 15:19:12 (4035a000): Got shutdown signal.
2013-07-16 15:19:12 (4035a000): Stopping gracefully
2013-07-16 15:19:12 (4035a000): Stopping rendezvous daemon
2013-07-16 15:19:12 (4035a000): Closing database
2013-07-16 15:19:12 (4035a000): Done!

Looking at the dates, it seems that the service is not running. Is there a way to force this ?

Thanks,
John

Hi John, I've been travelling....

A reboot should restart it? Or, from a terminal: service mt-daapd start

Check the 'services' file at /etc/default/services (change the entry DAAP=0 to DAAP=1) to enable the Firefly service. Is it enabled?

Seems the problem was with the mt-daapd.conf file, which contained a lot of errors and wrong entries (primarily wrong database type, sqlite instead of sqlite3, and incorrect path to music files).

Once changed, it has all come back as before.

Many thanks for your pointers, Tony, and persistence in seeing this through to a solution.

Regards,
John

No problem at all. Looking at you July dates, that looks like when you upgraded to 5.3.8, which messed up my settings in the exact same way when I did the 5.3.8 upgrade too! Pretty poor really.

Tony, John - thanks for this. I had exactly the same problem. Thought my days of using command line interfaces and vi were 25 years behind me but I got there eventually. I did find multiple mt-daap.conf files and through trial and error changing each and re-booting got there in the end. I was going to try and figure out which edit did the job and report here to help others who must be having the problem so I renamed one copy of the the file and re-booted but it appeared again. No idea why and at this point I've decided to cut my loses before I do any damage (root access with someone who hasn't touched a command line for so long). Maybe if you know what directory the offending file resides in you could report it here. I also didn't manage to get it to write the log file either even though I specified it in the conf file.

Thanks again

Duncan

This is what I did to get Firefly working:

To enable Firefly service edit: /etc/default/services
and change the entry DAAP=0 to DAAP=1

The Firefly config file is: /etc/mt-daapd.conf
change database type to sqlite3
change runas = nobody to runas = root
change mp3_dir = /media/Music

The log file is: /var/log/mt-daapd.log

Restart the NV+ v2 to activate all the settings