You are here: Home » Topic » daap server crashing

daap server crashing

This topic contains 8 replies, has 2 voices, and was last updated by  Anonymous 11 years, 9 months ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #2211

    Anonymous

    I am having a problem where ~10 minutes after re-starting mt-daapd, it ceases to advertise its Bonjour services. I can still access the webserver and doing a ps -ef I see that avahi-daemon is still running as well.

    From the log, the only relevant line that I could see was the following:

    2008-02-11 06:46:32: Rendezvous socket closed (daap server crashed?) Aborting.

    I am running this on Ubuntu Server v7.10 and have the following:
    – avahi-daemon: 0.6.20-2ubuntu3.2
    – mt-daapd: 0.2.4-1

    The only other “media” application I am running is SlimServer. Any help would be appreciated![/list]

    #16257

    rpedde
    Participant

    @Juggler wrote:

    I am having a problem where ~10 minutes after re-starting mt-daapd, it ceases to advertise its Bonjour services. I can still access the webserver and doing a ps -ef I see that avahi-daemon is still running as well.

    From the log, the only relevant line that I could see was the following:

    2008-02-11 06:46:32: Rendezvous socket closed (daap server crashed?) Aborting.

    I am running this on Ubuntu Server v7.10 and have the following:
    – avahi-daemon: 0.6.20-2ubuntu3.2
    – mt-daapd: 0.2.4-1

    The only other “media” application I am running is SlimServer. Any help would be appreciated![/list]

    Do you see mt-daapd when you look at the process list? If so, then the likely cause is your server is dropping or blocking inbound multicast. You’ll need to allow to and from 224.0.0.251 on 5353 udp (at a minimum… to unblock all multicast, you need to unblock 224.0.0.0/4).

    If you *don’t* see the mt-daapd process, then it’s crashing. Probably when scanning a file with bad header data. You can try specifying a log file in the config, and setting debuglevel to 5. Then start the server and watch what the last file scanned was. Move that file out of the way and scan again. Rinse & repeat as necessary.

    – Ron

    #16258

    Anonymous

    I uninstalled my previous version of mt-daapd with:

    $ sudo rm mt-daapd_0.2.4-1_i386.deb

    I then downloaded the svn-1696 nightly build and entered:

    $ sudo dpkg --install mt-daapd_0.9-svn-1696_edgy_i386.deb

    I got the following errors:

    (Reading database ... 42177 files and directories currently installed.)
    Preparing to replace mt-daapd 0.9-svn-1696 (using mt-daapd_0.9-svn-1696_edgy_i386.deb) ...
    Unpacking replacement mt-daapd ...
    dpkg: dependency problems prevent configuration of mt-daapd:
    mt-daapd depends on libflac7; however:
    Package libflac7 is not installed.
    mt-daapd depends on libsqlite0 (>= 2.8.17); however:
    Package libsqlite0 is not installed.
    dpkg: error processing mt-daapd (--install):
    dependency problems - leaving unconfigured
    Errors were encountered while processing:
    mt-daapd

    I see that I already have libflac8 (v1.1.4-3ubuntu1.1) and libsqlite3-0 (v3.4.2-1build1) installed. I did do a quick “apt-cache search” for both libflac8 and libsqlite0, but neither were found. What should be my next step?

    many thanks,
    J.

    #16259

    eliah

    I’m having quite a similar problem. mt-daapd installed from the Ubuntu repositories, which is apparently version svn-1586. After about 20 minutes, I get a crash, and here’s what the end of the logfile said (I upped the debug level to 5 following that suggestion here):


    2008-02-16 20:25:44 (b748a6c0): Found music file: Subfader_-_The_Classic_Rare_Jazz_Experience_Vol._7_-_Old_School_Jazz_2.mp3
    2008-02-16 20:38:02 (b6c3cb90): Rendezvous socket closed (daap server crashed?) Aborting.
    2008-02-16 20:38:02: Aborting

    Now, the fact that the crash is so far after the last scan, plus the fact that it scanned a bunch of other files just like it and didn’t crash, make me think that it’s probably not bad headers, but I don’t know. Any ideas?

    #16260

    Anonymous

    Not sure what happened, but I have had (fingers crossed!!!) everything working for over 24 hours now. I did a complete uninstall reinstall, including using the purge and autoremove parameters for apt-get.

    For my install, I decide to keep to the repositories and just did: apt-get install mt-daapd.

    thanks for your suggestions,
    J.

    #16261

    Anonymous

    Bahh… it crashed again. I can now only keep it running for < 1 hour at a time. I've increased the verbosity of the log to 9 and see the following at time of crash:

    2008-02-18 14:29:46 (b64e7b90): Write error: Broken pipe
    2008-02-18 14:29:46 (b64e7b90): Finished streaming file to remote: 770048 bytes
    2008-02-18 14:29:46 (b64e7b90): Entering config_set_status
    2008-02-18 14:29:46 (b64e7b90): Exiting config_set_status
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Terminating
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Freeing request headers
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Freeing response headers
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Freeing request vars
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Closing fd
    2008-02-18 14:29:46 (b64e7b90): With thread 11 exiting, 0 are still running

    What I did the moment before mt-daapd crashed was tho quit iTunes––I did not eject the server first.

    Following this, the only way to restart it is to first issue: killall mt-daapd. There seems to be some processes continuing to run even though nothing is being advertised.

    Note that the above conditions for the server to crash are not 100% repeatable…

    Any help?

    #16262

    rpedde
    Participant

    @Juggler wrote:

    Bahh… it crashed again. I can now only keep it running for < 1 hour at a time. I've increased the verbosity of the log to 9 and see the following at time of crash:

    2008-02-18 14:29:46 (b64e7b90): Write error: Broken pipe
    2008-02-18 14:29:46 (b64e7b90): Finished streaming file to remote: 770048 bytes
    2008-02-18 14:29:46 (b64e7b90): Entering config_set_status
    2008-02-18 14:29:46 (b64e7b90): Exiting config_set_status
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Terminating
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Freeing request headers
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Freeing response headers
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Freeing request vars
    2008-02-18 14:29:46 (b64e7b90): Thread 11: Closing fd
    2008-02-18 14:29:46 (b64e7b90): With thread 11 exiting, 0 are still running

    What I did the moment before mt-daapd crashed was tho quit iTunes––I did not eject the server first.

    Following this, the only way to restart it is to first issue: killall mt-daapd. There seems to be some processes continuing to run even though nothing is being advertised.

    Note that the above conditions for the server to crash are not 100% repeatable…

    Any help?

    That’s not a crash, that’s a multicast issue. Either your firewall is blocking upd 5353 to/from 224.0.0.251, or your router isn’t passing multicast.

    #16263

    Anonymous

    Is that the only cause of this error? I ask as I am running an all Mac environment and all Bonjour services are working: afp, printer discovery, etc. I also have a SqueezeBox which uses Bonjour for automatic player discovery.

    I am running DD-WRT on a Linksys WRT54GS. The only setting I could see re: multicast was for the WAN link where I do have it filtering the packets.

    Am I completely out-to-lunch here?

    #16264

    Anonymous

    I disabled the multicast WAN filtering on my router, but I am still getting the same errors. I don’t think it is to do with multicast being blocked.

    Any other thoughts?

Viewing 9 posts - 1 through 9 (of 9 total)

The forum ‘Setup Issues’ is closed to new topics and replies.