FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › Installing mt-daapd on Suse 10
- This topic has 17 replies, 3 voices, and was last updated 17 years, 11 months ago by rpedde.
-
AuthorPosts
-
04/12/2006 at 5:41 PM #7056hhnougatGuest
Hi Ron,
since my last post I’m gone a step further. I’m able start and stop mt-daapd.
But when I’m requesting the status I get the reply: deadWhat does that mean? Because if I start mt-daapd it says done.
Any ideas?
Best regards
Jan04/12/2006 at 6:29 PM #7057hhnougatGuestIf I punch in chkconfig -a mt-daapd on the command line I get the following reply:
0:off 1:off 2:off 3:on 4:off 5:on 6:off
Is this any good?
05/12/2006 at 4:39 AM #7058rpeddeParticipant@hhnougat wrote:
Hi Ron,
since my last post I’m gone a step further. I’m able start and stop mt-daapd.
But when I’m requesting the status I get the reply: deadWhat does that mean? Because if I start mt-daapd it says done.
Any ideas?
Best regards
Janlook at /var/log/messages. There will be a message telling you why it won’t start. Maybe because “/var/cache/mt-daapd” doesn’t exist, or isn’t readable by the “runas” user?
08/12/2006 at 11:31 AM #7059hhnougatGuestWhat exactly has to be in the mentioned folder?
08/12/2006 at 11:36 AM #7060hhnougatGuestHi Ron,
now I had alook at the message file as you recommended.
Dec 8 12:24:36 ham01004 mt-daapd[15107]: Firefly Version svn-1450: Starting with debuglevel 1
Dec 8 12:24:36 ham01004 mt-daapd[15107]: Error opening plugin dir. Ignoring
Dec 8 12:24:36 ham01004 mt-daapd[15107]: Starting rendezvous daemon
Dec 8 12:24:36 ham01004 mt-daapd[15109]: Starting signal handler
Dec 8 12:24:37 ham01004 mt-daapd[15109]: db_sqlite2_open: unable to open database: @dbdir@/songs.db (@dbdir@/songs.db)
Dec 8 12:24:37 ham01004 mt-daapd[15109]: Error opening db: Misc SQL Error: unable to open database: @dbdir@/songs.db
Dec 8 12:24:37 ham01004 mt-daapd[15109]: Stopping signal handler
Dec 8 12:24:37 ham01004 mt-daapd[15109]: Got shutdown signal. Notifying daap server.It seems there is a database missing. Where do I get that from?
09/12/2006 at 12:25 AM #7061rpeddeParticipant@hhnougat wrote:
Dec 8 12:24:37 ham01004 mt-daapd[15109]: db_sqlite2_open: unable to open database: @dbdir@/songs.db (@dbdir@/songs.db)
Dec 8 12:24:37 ham01004 mt-daapd[15109]: Error opening db: Misc SQL Error: unable to open database: @dbdir@/songs.db
Dec 8 12:24:37 ham01004 mt-daapd[15109]: Stopping signal handler
Dec 8 12:24:37 ham01004 mt-daapd[15109]: Got shutdown signal. Notifying daap server.That’s the template config. Wasn’t there a config file (mt-daapd.conf) generated in your contrib directory?
@dbdir@ should have been replaced with the right path — /var/cache/mt-daapd, probably.
18/12/2006 at 9:32 AM #7062hhnougatGuestHi Ron,
step by step I’m getting further with the setup of mt-daapd.
I’ve got the mt-daapd running on a virtuel machine. But when I start the service on the live machine Igot the following message:”Waiting for music directory to appear…”
The music directory and the directory for the songs.db are on the same physical drive. Everything else is on a diffrent one (the main drive).
Is there anything I’ve to take in account about this constalation?
19/12/2006 at 4:12 AM #7063rpeddeParticipant@hhnougat wrote:
I’ve got the mt-daapd running on a virtuel machine. But when I start the service on the live machine Igot the following message:”Waiting for music directory to appear…”
That has something to do with your init script (/etc/init.d/mt-daapd). Check that. Something isn’t right with that. Or so I’d guess. That isn’t a message from mt-daapd. Sounds like it’s waiting for a file system to mount or something. Might see if there is a place in the init script to specifiy what you mp3 directory is.
— Ron
-
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.