mt-daapd crashes “Address already in use”

[politby]

Greetings,

I’m running mt-daapd on an NLSU2. Yesterday I tried running it with only about 15 mp3 files in the directory, and it seemed to work fine.
Now, when I have copied all my 4,000 some files to the directory, mt-daapd crashes during the mp3 file scan:

2005-04-04 22:39:39: Starting rendezvous daemon
2005-04-04 22:39:39: Starting signal handler
2005-04-04 22:39:39: Initializing database
2005-04-04 22:39:39: Starting mp3 scan
2005-04-04 22:40:49: Starting web server from /opt/share/mt-daapd/admin-root on
port 3689
2005-04-04 22:40:49: Could not open port: Address already in use
2005-04-04 22:40:49: Error staring web server: Address already in use
2005-04-04 22:40:49: Aborting
2005-04-04 22:40:49: Rendezvous socket closed (daap server crashed?) Aborting.
2005-04-04 22:40:49: Aborting

What could be causing this?

regards,
/POL

[rpedde]

It means another instance of mt-daapd is already running. You will probably have to delete your songs.gdb, if you had multiple mt-daapds running on the same database. The possibility of database corruption is pretty high.

For some reason the signal handling on the nslu2 is different than any of the other platforms I’ve run mt-daapd on, and I can’t get it to stop cleanly (except via the web interface). I’ve always had to do a “killall -9 mt-daapd” on the nslu2. Which is hackish, but I don’t have a better way (except the web interface).

— Ron

[politby]

Thanks, that was it. I was pretty sure I had rebooted the NSLU2 before I added all those files but apparently I hadn’t so when it came up again with only one instance running it did complete the scan and is now running fine.

regards
/POL

[Author]

Posts