FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › mt-daapd aborts shortly after starting up
- This topic has 16 replies, 3 voices, and was last updated 16 years, 8 months ago by sonichouse.
-
AuthorPosts
-
19/03/2008 at 10:49 PM #2312AnonymousInactive
Hi, I have been happily using the mt-daapd software on my nslu2 for a few months now (thanks, by the way, it’s great software), but lately it’s not been working too well.
Here’s what the log says:
2008-03-19 22:42:48: Starting rendezvous daemon
2008-03-19 22:42:48: Current database version: 8
2008-03-19 22:42:48: Starting signal handler
2008-03-19 22:42:49: Loading playlists
2008-03-19 22:42:49: Initializing database
2008-03-19 22:42:54: Starting mp3 scan
2008-03-19 22:47:13: Rendezvous socket closed (daap server crashed?) Aborting.
2008-03-19 22:47:13: AbortingAny idea what could be causing this?
Thanks!
19/03/2008 at 10:51 PM #16581sonichouseParticipant@markturner wrote:
Hi, I have been happily using the mt-daapd software on my nslu2 for a few months now (thanks, by the way, it’s great software), but lately it’s not been working too well.
Here’s what the log says:
2008-03-19 22:42:48: Starting rendezvous daemon
2008-03-19 22:42:48: Current database version: 8
2008-03-19 22:42:48: Starting signal handler
2008-03-19 22:42:49: Loading playlists
2008-03-19 22:42:49: Initializing database
2008-03-19 22:42:54: Starting mp3 scan
2008-03-19 22:47:13: Rendezvous socket closed (daap server crashed?) Aborting.
2008-03-19 22:47:13: AbortingAny idea what could be causing this?
Thanks!
It is probably tripping over a rogue mp3 file that has been added.
Set the log level to 5 and it should tell you what file it is scanning.
19/03/2008 at 11:17 PM #16582AnonymousInactiveOK, I tried putting in “logfile /var/log/mt-daapd.log -d5” into the conf file and now I get nothing in the log at all!
Am I doing it wrong? 😕
19/03/2008 at 11:27 PM #16583sonichouseParticipant@markturner wrote:
OK, I tried putting in “logfile /var/log/mt-daapd.log -d5” into the conf file and now I get nothing in the log at all!
Am I doing it wrong? 😕
You need to set
debuglevel = 5
and leave the log entry as
logfile /var/log/mt-daapd.log
19/03/2008 at 11:33 PM #16584AnonymousInactiveNow I get this error on startup:
# /opt/etc/init.d/S60mt-daapd
Invalid config directive: debuglevel
Error reading config file (/opt/etc/mt-daapd/mt-daapd.conf)I can’t get into the web interface as it doesn’t stay running long enough so I’ve got to set this through the config file.
19/03/2008 at 11:38 PM #16585AnonymousInactiveOh I get it, you put -d5 after the command to run it…
19/03/2008 at 11:41 PM #16586sonichouseParticipant@markturner wrote:
Now I get this error on startup:
# /opt/etc/init.d/S60mt-daapd
Invalid config directive: debuglevel
Error reading config file (/opt/etc/mt-daapd/mt-daapd.conf)I can’t get into the web interface as it doesn’t stay running long enough so I’ve got to set this through the config file.
The debuglevel entry lives in the [general] section.
It should have been there by default.
19/03/2008 at 11:49 PM #16587AnonymousInactiveI don’t have a general section or any = signs in the file, seems to be different to what you’re talking about… I’m editing the /opt/etc/mt-daapd/mt-daapd.conf file, is there another one I should know about?
Anyway, no extra info was provided by the log with -d5, so I tried it with -d9, and it still didn’t give me any extra stuff:
2008-03-20 00:15:16: Starting rendezvous daemon
2008-03-20 00:15:16: Current database version: 8
2008-03-20 00:15:16: Starting signal handler
2008-03-20 00:15:17: Loading playlists
2008-03-20 00:15:17: Initializing database
2008-03-20 00:15:21: Starting mp3 scan
2008-03-20 00:19:36: Rendezvous socket closed (daap server crashed?) Aborting.
2008-03-20 00:19:36: Aborting19/03/2008 at 11:56 PM #16588sonichouseParticipant@markturner wrote:
I don’t have a general section or any = signs in the file, seems to be different to what you’re talking about… I’m editing the /opt/etc/mt-daapd/mt-daapd.conf file, is there another one I should know about?
Anyway, no extra info was provided by the log with -d5, so I tried it with -d9, and it still didn’t give me any extra stuff:
2008-03-20 00:15:16: Starting rendezvous daemon
2008-03-20 00:15:16: Current database version: 8
2008-03-20 00:15:16: Starting signal handler
2008-03-20 00:15:17: Loading playlists
2008-03-20 00:15:17: Initializing database
2008-03-20 00:15:21: Starting mp3 scan
2008-03-20 00:19:36: Rendezvous socket closed (daap server crashed?) Aborting.
2008-03-20 00:19:36: AbortingWhich version are you running ?
20/03/2008 at 12:03 AM #16589AnonymousInactiveI don’t know I got it from the ipkg optware package system.
The date at the top of the config file is 2005 though so having seen that I’m guessing it’s not too recent…
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.