Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 4874 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SUM socket not listening at service startup...

Xt

Hello,

My SUM service is stopped for 24 hours.

When I restart it, port 51234 is sometimes not listening and I catch the SUM log error :

"The socket listener caught an exception: Failed to bind to the listening socket: error code was 10013"

I need to restart it few times in order to have it starting...

Sophos Agent is stopped before SUM start in order to prevent SYN socket having impact on the port 51234... but I still have sometimes this socket not mounted...

has anyone had this kind of issue ?

What can explain this behaviour ?

Thanks in advance,

Regards

:38659


This thread was automatically locked due to age.
  • 0

    Hello Xt,

    My SUM service is stopped for 24 hours

    just curious - for what reason?

    What can explain this behaviour ?

    Just a WAG - dunno if RouterNT has some safeguard built in to not use this port, if not it might have grabbed it to connect back to a client ... as said, a wild guess. netstat -ab (pipe the output to a file) should tell you if some other process has this port in use.

    Christian

    :38691
  • 0

    HI,

    You don't mention the OS as that would change the default ephemeral port range (2003 vs 2008 as an example) but if you think it's just a port conflict you could just change the port SUM uses to one higher in the range to reduce the chance:

    http://www.sophos.com/en-us/support/knowledgebase/65930.aspx

    As QC mentions, if Sophos is the only software on the computer the most likely process to grab a large number of ephemeral ports is the RouterNT.exe.  This is the obvious one that creates the contention.  I can only assume that SUM is performing a self update, causing the SUM service to restart which in turn forces SophosUpdateMgr to restart.  If the router has been running a while at this point it may have taken 51234 so you get the problem.

    Regards,

    Jak

    :38723