Firefly won’t start on NSLU2

[Renno]

I’m mystified I’m afraid. After weeks of smugly assuming that set-up problems are what happened to everybody else, I’ve been struck down.

I’m running uNSLUng 6.8 beta on my NSLU2, with svn-1400. Everything has been working perfectly for several weeks. The library can still be viewed in XP on the slug, and anyway nothing has changed there.

There’s no problem at my Soundbridge end, I can play Internet Radio, but “no library” when I try to play firefly.

I can’t access the web admin page on port 3689. When I do “ipkg install mt-daapd” it says “Package mt-daapd (svn-1400-1) installed in root is up to date. Nothing to be done”

I did renew my McAfee suite yesterday – but whilst nothing should have changed, there doesn’t seem to be any problem accessing port 3689. How would I check?

Any ideas?

Paul

[fizze]

what do you get when you do a

ps aux

on the slug?

there should be a couple of processes called “mt-daapd”. if there arent, then mt-daapd/direfly isnt runnig.

whats the uptime of the slug?

[Renno]

Thanks for the reply. Planning to settle down for a glass of wine and plan Christmas – not as nice music less!

No sign of an mt-daapd procedure

ps aux
PID TTY Uid Size State Command
1 root 1212 S /bin/init
2 root 0 S [keventd]
3 root 0 S [ksoftirqd_CPU0]
4 root 0 S [kswapd]
5 root 0 S [bdflush]
6 root 0 S [kupdated]
7 root 0 S [mtdblockd]
8 root 0 S [khubd]
9 root 0 S [jffs2_gcd_mtd4]
10 root 0 S [usb-storage-0]
11 root 0 S [scsi_eh_1]
16 root 0 S [sd-mc-thread]
19 root 0 S [usb-storage-1]
20 root 0 S [scsi_eh_0]
30 root 0 S [kjournald]
52 root 0 D [ixp425_csr]
53 root 0 S [ixp425 ixp0]
56 ttyS0 root 1916 S /bin/sh
57 root 1936 S /sbin/syslogd -n
58 root 1924 S /sbin/klogd -n
151 root 0 S [kjournald]
165 root 0 S [kjournald]
254 root 10940 S upnpd &>/dev/null
276 root 10940 S upnpd &>/dev/null
277 root 10940 S upnpd &>/dev/null
281 root 10940 S upnpd &>/dev/null
282 root 10940 S upnpd &>/dev/null
361 root 2152 S /usr/sbin/thttpd -C /etc/thttpd.conf
385 root 6156 S /usr/sbin/smbd -D
387 root 4824 S /usr/sbin/nmbd -D
404 root 6156 S /usr/sbin/smbd -D
414 root 1952 S /usr/sbin/QuickSet
419 root 1904 S /usr/sbin/USB_Detect
420 root 1900 S /usr/sbin/USB_Detect
427 root 1884 S /usr/sbin/onetouch_detect
428 root 1884 S /usr/sbin/onetouch_detect
442 root 1296 S /usr/sbin/crond
450 root 1928 S /usr/sbin/CheckResetButton
452 root 1196 S /usr/sbin/CheckPowerButton
454 root 1196 S /usr/sbin/do_umount
546 root 2152 S /usr/sbin/thttpd -C /etc/thttpd.conf
560 root 1276 S /bin/inetd
710 root 1256 S /usr/sbin/telnetd
711 ttyp0 root 1932 S -sh
734 root 10940 S upnpd &>/dev/null
747 root 1256 S /usr/sbin/telnetd
748 ttyp1 root 1920 S -sh
749 ttyp1 root 1984 R ps aux

Is there a slug uptime page in the web interface? I rebooted yesterday evening, so it’s been back up for approx 24 hours.

Assuming firefly isn’t running, shouldn’t /opt/etc/init.d/S60mt-daapd get it up and running. After this, nothing happens.

[sansp00]

Looks like the process crashed/terminated …
Do you have anything in the /var/log/messages file that could explain this ?!?
Patrick S.

[Renno]

Ok, I think we may have a problem!

tail -f /var/log/messages
<38>Nov 17 20:18:36 login[745]: root login on `ttyp1′ from `192.168.1.11′
<38>Nov 17 20:19:31 login[748]: root login on `ttyp1′ from `192.168.1.11′
<25>Nov 17 20:28:49 mt-daapd[786]: Starting with debuglevel 9
<25>Nov 17 20:28:49 mt-daapd[786]: Starting rendezvous daemon
<25>Nov 17 20:28:49 mt-daapd[788]: Starting signal handler
<25>Nov 17 20:28:50 mt-daapd[788]: Initializing database
<25>Nov 17 20:28:53 mt-daapd[788]: Query: vacuum
<25>Nov 17 20:28:53 mt-daapd[788]: Error: database disk image is malformed
<25>Nov 17 20:28:53 mt-daapd[787]: Rendezvous socket closed (daap server crashed?) Aborting.
<78>Nov 17 21:01:00 cron[442]: running /usr/sbin/hwclock -s &>/dev/null
^

I’m still a bit green around the gills regarding this. It doesn’t look good. Is it just the case of re-installing firefly?

[fizze]

well, it looks that the database went down.

could it be that the unit was doing an automated scan during which you rebooted it? (prolly even hard reboot?)

well, just delete your songs.db and you should be fine anyhow.
you will lose your smart playlists though, that you defined through the web-interface.

if you dont like that wait for ron to give a detailed explanation 😉

[Renno]

Thanks. This is where my ignorance kicks in. Where is songs.db and how do I delete it??

Paul

[sansp00]

The file is in /opt/var/mt-daapd normally …
If not, go in the mt-daapd.conf (/opt/etc/mt-daapd/mt-daapd.conf) file and look for the db_dir which should indicate where it is.
Hope this helps !
Patrick S.

[rpedde]

I love these threads. I could have gone to bed already.

🙂

Thanks, y’all.

— Ron

[Renno]

Thanks to all. A silent glass of wine last night, but songs with my cup of tea this morning.

Paul

[Author]

Posts