SVN-1677 (Win32) – Couldn’t set socket to blocking

  • Post date

FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › SVN-1677 (Win32) – Couldn’t set socket to blocking

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • 21/10/2007 at 2:43 PM #1838
    swests
    Guest

    Hi

    Just updated from 1571 to 1677 and am now seeing hundreds of the following in the log.

    2007-10-21 15:25:14 (3be69f59): Couldn’t set socket to blocking

    Whatever is causung this seems to wake every 10 mins as shows below

    2007-10-21 15:25:14 (e0d3e3cc): Couldn’t set socket to blocking
    2007-10-21 15:25:14 (e0d3e3cc): Couldn’t set socket to blocking
    2007-10-21 15:36:25 (3beb8ec2): Couldn’t set socket to blocking
    2007-10-21 15:36:25 (3beb8ec2): Couldn’t set socket to blocking

    Running on Win2003 server (Not R2).

    Wierd as never had any other issues with this great software…

    What do you need to help debug?

    Simon

    21/10/2007 at 8:16 PM #13014
    rpedde
    Participant

    @swests wrote:

    2007-10-21 15:25:14 (e0d3e3cc): Couldn’t set socket to blocking
    2007-10-21 15:25:14 (e0d3e3cc): Couldn’t set socket to blocking
    2007-10-21 15:36:25 (3beb8ec2): Couldn’t set socket to blocking
    2007-10-21 15:36:25 (3beb8ec2): Couldn’t set socket to blocking

    In current svn, I’ve masked this by not trying to set socket options until later in the lifetime of the socket.

    But what’s strange is that this even appears. If there are no connections, that shouldn’t even show up. I noticed when waiting for sockets to become ready to read on windows, the WaitForMultipleObjects sometimes wakes up even when none of the sockets are readable. I’m wondering if this is the case here — that the wait on the accept socket is waking up even though a connection hasn’t happened.

    That never happens on unix (at least not without an EINTR), so I don’t really have an defensive code for it. Might need to add some defensive stuff for that.

    — Ron

    22/10/2007 at 9:26 PM #13015
    toecheese
    Participant

    I’m getting the exact same error. The server suddenly stops and I get tons of lines of:

    2007-10-22 13:53:12 (54c2c0bb): Couldn’t set socket to blocking

    I can restart the server but after awhile it does the same thing again.

    This is on Windows XP.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.