- This topic has 6 replies, 4 voices, and was last updated 17 years, 6 months ago by
.
-
Posts
-
Hi,
I installed mt-daapd using the stable .deb package on Kubuntu Feisty. The MP3s are located in /media/WD Passport/Documents/Music (on my external hard drive). mt-daapd is installed on my main hard drive. I edited /etc/mt-daapd.conf to fit my needs. But when I start up mt-daapd (sudo mt-daapd), it doesn’t show up on my network. So I tried sudo mt-daapd -f. Here’s what happened:Config entry general/db_dir is deprecated. Please review the sample config
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
Error opening db: No backend database support for type: sqlite
Signal handler started
Stopping signal handler
Got shutdown signal. Notifying daap server.Any ideas?
Error opening db: No backend database support for type: sqlite
Guess what that means? You don’t have sqlite installed probably 😉
If you have sqlite3 installed, you need to adjust the config file to use sqlite3, otherwise just install the version you like more (2 or 3)…PS: Not sure if Kubuntu uses the same packet manager as Unbuntu with a K… just search for a package named “sqlite” or “sqlite3” there.
@onlineapps wrote:
I installed mt-daapd using the stable .deb package on Kubuntu Feisty. The MP3s are located in /media/WD Passport/Documents/Music (on my external hard drive). mt-daapd is installed on my main hard drive. I edited /etc/mt-daapd.conf to fit my needs. But when I start up mt-daapd (sudo mt-daapd), it doesn’t show up on my network. So I tried sudo mt-daapd -f. Here’s what happened:
This also looks like you had the 0.2.4 installed before, then upgraded over the top of it.
Try removing the app (with –purge), then re-installing it so you get the new config file. Then edit and start. Failing that, you can probably make it run by changing the db_type to “sqlite3”, which is probably what it is in the config shipped by the debian package.
— Ron
Sort of fixed it. I had installed sqlite, but not sqlite3 😳
Now though, there’s another problem. I purged mt-daapd and reinstalled it. Then, 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
Signal handler started
db_sqlite3_open: Misc SQL Error: unable to open database file (/var/cache/mt-daapd/songs3.db)
Error opening db: Misc SQL Error: unable to open database file
Stopping signal handler
Got shutdown signal. Notifying daap server.I then tried changing from sqlite3 to sqlite.
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
Error opening db: No backend database support for type: sqlite
Signal handler started
Stopping signal handler
Got shutdown signal. Notifying daap server.
Rendezvous socket closed (daap server crashed?) Aborting.
AbortingNow 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?
@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
@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
- The forum ‘Setup Issues’ is closed to new topics and replies.