You are here: Home » Topic » mt-daapd aborts shortly after starting up

mt-daapd aborts shortly after starting up

This topic contains 16 replies, has 3 voices, and was last updated by  sonichouse 10 years, 6 months ago.

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #2312

    Anonymous

    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: Aborting

    Any idea what could be causing this?

    Thanks!

    #16581

    sonichouse
    Participant

    @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: Aborting

    Any 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.

    #16582

    Anonymous

    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? 😕

    #16583

    sonichouse
    Participant

    @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
    #16584

    Anonymous

    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.

    #16585

    Anonymous

    Oh I get it, you put -d5 after the command to run it…

    #16586

    sonichouse
    Participant

    @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.

    #16587

    Anonymous

    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: Aborting

    #16588

    sonichouse
    Participant

    @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: Aborting

    Which version are you running ?

    #16589

    Anonymous

    I 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…

    #16590

    sonichouse
    Participant

    @markturner wrote:

    I 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…

    You can get a more recent version from http://nightlies.fireflymediaserver.org/ the most recent stable one is 1596, although I run 1696 and sqlite3 on my slug with no problems.

    Have you updated your ipkg config files to check for the later builds ?.

    I have created a /etc/ipkg/firefly.conf with

    src firefly http://ipkg.fireflymediaserver.org/armeb

    You will need to do
    ipkg update
    ipkg upgrade mt-daapd

    note that this will blow away your playlists if you haven’t backed them up – as they are now stored in the db.

    #16591

    Anonymous

    Doing that installed the 1586 version, which seems to be working fine. Lots of interesting errors in the log about unknown meta code, but presumably those are benign errors!

    Thanks for your help, much appreciated!

    #16592

    Anonymous

    Oh dear, looks like I spoke too soon. Just got the same error again:

    2008-03-20 01:19:39 (00000400): Rendezvous socket closed (daap server crashed?) Aborting.

    I’ll try running it in debug mode…

    #16593

    Anonymous

    OK, so it now says this at the end:

    2008-03-20 01:45:30 (00000400): Found music file: 04 Ghost Hardware.mp3
    2008-03-20 01:48:42 (00000400): Rendezvous socket closed (daap server crashed?) Aborting.
    2008-03-20 01:48:42: Aborting

    Does this mean that file is the bad one? Or is the one it tried to scan after that the bad one?

    #16594

    EVILRipper
    Participant

    That’s probably the bad one.
    Try moving it out of the scanning directory, and see if it scans any further.

Viewing 15 posts - 1 through 15 (of 17 total)

The forum ‘General Discussion’ is closed to new topics and replies.