@rpedde wrote:
@onlineapps wrote:
Sort of fixed it. I had installed sqlite, but not sqlite3 😳
Right, but if the debian package was installed cleanly, it would have given you a config that used the right sql backend.
Now one thing I did do before was to delete /var/cache/mt-daapd. See, the purge (using
aptitude purge mt-daapd) didn’t delete it (it complained it wasn’t empty, or something like that). Should I have not done that?
Package should have done that already, but you can:
mkdir /var/cache/mt-daapd
chown nobody /var/cache/mt-daapdand it should start.
— Ron
Alright, now I got a:
Starting with debuglevel 2
Starting rendezvous daemon
*** WARNING *** The programme 'mt-daapd' uses the HOWL compatiblity layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
Starting signal handler
Initializing database
Full reload...
Signal handler started
Starting mp3 scan
Starting playlist scan
Scanned 349 songs in 9 seconds
Starting web server from /usr/share/mt-daapd/admin-root on port 3689
Listen port: Address already in use
Error staring web server: Address already in use
Aborting
Rendezvous socket closed (daap server crashed?) Aborting.
Aborting