You are here: Home » Topic » Rendezvous socket closed (daap server crashed?)

Rendezvous socket closed (daap server crashed?)

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #2620
    hcibeau
    Participant

    I’ve had many issues over the last few months. Mainly, I’m seeing the following:

    Rendezvous socket closed (daap server crashed?)
    Aborting

    On occasion, I’m able to play one song before this happens. The second song I try to play usually causes this. This only happened a few times today, though. At this point, even restarting the process doesn’t seem to have any effect on whether or not iTunes is able to play a song.

    This setup has been working fine for nearly a year… only started to give me issues a few months ago. I thought maybe it had something to do with new versions of iTunes but Im at a loss as to how to fix this.

    I tried the most recent stable as well as the newest stable nightly ( Version svn-1586 ) and I’m still having this same problem.

    Is this an known issue? I can’t seem to see any forum posts talking about this problem.

    #17674
    hcibeau
    Participant

    Any ideas here? I’d hate to abandon this altogether as I did rather enjoy using firefly this last year or so…

    #17675
    EVILRipper
    Participant

    Something causes the server to die.
    Overall, when firefly stumbles unto something it doesn’t like, it simply runs the shutdown script.

    Try raising the debuglevel up to 9 to find more clues in the log file.
    If level 9 doesn’t give any clues to you, post the last ~20 lines. Maybe we can find anything for you.

    #17676
    hcibeau
    Participant

    Here is the log after I just tried to play a song.

    [[email protected] altern8]# tail -25 /var/log/mt-daapd.log
    2008-09-03 15:50:54 (b7fb76c0): select(8, 5.000000)
    2008-09-03 15:50:59 (b7fb76c0): select(8, 5.000000)
    2008-09-03 15:51:04 (b7fb76c0): select(8, 5.000000)
    2008-09-03 15:51:05 (b6149b90): Thread 18: Entering ws_dispatcher (Connection from 10.42.12.43)
    2008-09-03 15:51:05 (b6149b90): Thread 18: got request
    2008-09-03 15:51:05 (b6149b90): Request: GET daap://10.42.12.20:3689/databases/1/items/595.mp3 HTTP/1.1
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Accept: */*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Accept=*/**
    2008-09-03 15:51:05 (b6149b90): Added *Accept=*/**
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Cache-Control: no-cache
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Cache-Control=no-cache*
    2008-09-03 15:51:05 (b6149b90): Added *Cache-Control=no-cache*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: User-Agent: iTunes/7.7.1 (Macintosh; N; Intel)
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *User-Agent=iTunes/7.7.1 (Macintosh; N; Intel)*
    2008-09-03 15:51:05 (b6149b90): Added *User-Agent=iTunes/7.7.1 (Macintosh; N; Intel)*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Client-DAAP-Access-Index: 2
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Client-DAAP-Access-Index=2*
    2008-09-03 15:51:05 (b6149b90): Added *Client-DAAP-Access-Index=2*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Client-DAAP-Validation: pÛÓÿ¿ä
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Client-DAAP-Validation=pÛÓÿ¿ä*
    2008-09-03 15:51:05 (b6149b90): Added *Client-DAAP-Validation=pÛÓÿ¿ä*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: rÀÃ[code]
    [[email protected] altern8]# tail -25 /var/log/mt-daapd.log
    2008-09-03 15:50:54 (b7fb76c0): select(8, 5.000000)
    2008-09-03 15:50:59 (b7fb76c0): select(8, 5.000000)
    2008-09-03 15:51:04 (b7fb76c0): select(8, 5.000000)
    2008-09-03 15:51:05 (b6149b90): Thread 18: Entering ws_dispatcher (Connection from 10.42.12.43)
    2008-09-03 15:51:05 (b6149b90): Thread 18: got request
    2008-09-03 15:51:05 (b6149b90): Request: GET daap://10.42.12.20:3689/databases/1/items/595.mp3 HTTP/1.1
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Accept: */*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Accept=*/**
    2008-09-03 15:51:05 (b6149b90): Added *Accept=*/**
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Cache-Control: no-cache
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Cache-Control=no-cache*
    2008-09-03 15:51:05 (b6149b90): Added *Cache-Control=no-cache*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: User-Agent: iTunes/7.7.1 (Macintosh; N; Intel)
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *User-Agent=iTunes/7.7.1 (Macintosh; N; Intel)*
    2008-09-03 15:51:05 (b6149b90): Added *User-Agent=iTunes/7.7.1 (Macintosh; N; Intel)*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Client-DAAP-Access-Index: 2
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Client-DAAP-Access-Index=2*
    2008-09-03 15:51:05 (b6149b90): Added *Client-DAAP-Access-Index=2*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: Client-DAAP-Validation: pÛÓÿ¿ä
    2008-09-03 15:51:05 (b6149b90): Thread 18: Adding header *Client-DAAP-Validation=pÛÓÿ¿ä*
    2008-09-03 15:51:05 (b6149b90): Added *Client-DAAP-Validation=pÛÓÿ¿ä*
    2008-09-03 15:51:05 (b6149b90): Thread 18: Read: rÀÃ

    #17677
    EVILRipper
    Participant

    Does the crash happen with any song? Or possibly on the same song?
    I found a thread with the same error message where firefly stumbled unto a corrupt file.
    Try searching the forums if that’s not the issue.

    The log doesn’t give me any clues either…

    #17678
    hcibeau
    Participant

    It happens with many songs that have played in the past. It is possible that this is related to corrupted files… but how would I know if that is the case? Sometimes the same file will play the first time, and then die the second.

    #17679
    stretch
    Participant

    try using something other than iTunes to play the music streamed via Firefly to see if it’s a Firefly or iTunes problem.
    Easiest one is probably the Java Firefly client in the 3rd party software section of the forum.

    You could also try this tool for checking MP3’s
    http://mp3val.sourceforge.net/

    #17680
    hcibeau
    Participant

    Java Firefly client plays fine. I had an idea this might be an iTunes problem ( after a full year worth of upgrades ) … however, I’m now running the newest stable nightly so I had hoped that it would have accounted for some of the recent iTunes changes…

    So, any ideas as to where I go from here? 🙂

    #17681
    stretch
    Participant

    @hcibeau wrote:

    so I had hoped that it would have accounted for some of the recent iTunes changes…

    svn-1696 will celebrate its 1st birthday on the 29th October 2008

    @hcibeau wrote:

    So, any ideas as to where I go from here? 🙂

    http://forums.fireflymediaserver.org/viewtopic.php?p=21046#21046

    #17682
    Anonymous
    Inactive

    I had the exact same problem. Here is how I fixed it.

    I uninstalled iTunes v.7.7.1, and installed v7.6.2. Here is how I did that;

    1) drag the iTunes from the App folder to the trash.
    2) open the system monitor (from the utilities folder) and find and stop the iTunes helper.
    3) Empty the trash
    4) copy and rename the iTunes folder from the Music folder to somewhere else
    5) Download v7.6.2 from http://oldapps.com/download_iTunes_mac.php
    6) Install it as usual

    I suspect the new version of iTunes is somehow closing the socket when you click on a new song.

    In my case, I could restart the firefly server process and click on a song in iTunes. That song and all subsequent songs in the shared library would play in succession with no problem, but if I double clicked another song, no matter what song it was, the firefly server would shut itself down with the OP error msg.

    Until the error is fixed that is caused by the newest version of iTunes, just revert back to an earlier version.

    #17683
    Anonymous
    Inactive

    I actually think it’s worse than just closing a socket; it’s not even finding the server or seeing the files.

    Definitely needs some dev work to fix I guess. I’m sure these guys are working to solve it 🙂

Viewing 11 posts - 1 through 11 (of 11 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.