Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 23 replies
  • Answers 2 answers
  • Subscribers 2 subscribers
  • Views 42973 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

Update manager - timeout error

KingRolo

Hello!

We installed new SEC 5.5. Before that it was Control Center ver 4.0.x.

When SEC runs Update wizard shows and after user name and password is entered its trying to connect (I guess) but the time out error pop up.

 

Also Sophos Management Service is not running properly - it starts then it stops.

Inside the folder "C:\ProgramData\Sophos\Remote Management System\3\Router\Logs" 2 log files are being created every minute with the same error.

 

Error in Router log:

18.07.2017 10:32:02 04F0 I SOF: C:\ProgramData/Sophos/Remote Management System/3/Router/Logs/Router-20170718-083202.log
18.07.2017 10:32:02 04F0 I Sophos Messaging Router 4.1.0.140 starting...
18.07.2017 10:32:02 04F0 I Setting ACE_FD_SETSIZE to 20640
18.07.2017 10:32:02 04F0 I Initializing CORBA...
18.07.2017 10:32:02 04F0 I Connection cache limit is 20512
18.07.2017 10:32:03 04F0 I Creating ORB runner with 16 threads
18.07.2017 10:32:04 04F0 I Compliant certificate hashing algorithm.
18.07.2017 10:32:04 04F0 E This machine may have more IP addresses than are supported or the port may already be in use.
18.07.2017 10:32:04 04F0 E Router::Start: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 40 (endpoint initialization failure in Acceptor Registry; low 7 bits of errno: 64 Unknown error), completed = NO

 

What could be wrong?

 

Regards,

Miha

 

 



This thread was automatically locked due to age.
  • 0

    Hello Miha,

    so this is a fresh install, which Server version (I assume it's a new one)?
    more IP addresses than are supported would be more than 62 - I don't think this is the case. Is some process using 8194 (netstat -nao | find ":8194")?

    Christian

  • 0 in reply to QC

    Hello QC!

    No, the command doesnt return anything.

    BR

  • 0 in reply to KingRolo

    What about Sophos Message Router? Why doesnt start properly?

    In Event viewer\system if full its error

    The Sophos Message Router service terminated unexpectedly.  It has done this 917 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

     

  • 0 in reply to KingRolo

    Hello Miha,

    so the Management Service starts and stops - what about the Message Router (and the other Sophos services)? Are there events in the Windows Application log? If there is no useful information then turning on verbose logging for the router might provide some.

    Christian

  • 0 in reply to QC

    18.07.2017 15:58:16 4CE0 I SOF: C:\ProgramData/Sophos/Remote Management System/3/Router/Logs/Router-20170718-135816.log
    18.07.2017 15:58:16 4CE0 I Sophos Messaging Router 4.1.0.140 starting...
    18.07.2017 15:58:16 4CE0 I Setting ACE_FD_SETSIZE to 20640
    18.07.2017 15:58:16 4CE0 I Initializing CORBA...
    18.07.2017 15:58:16 4CE0 I Connection cache limit is 20512
    18.07.2017 15:58:17 4CE0 D New context options = 1000004
    18.07.2017 15:58:17 4CE0 D Router::ConfigureSslContext: configuration finished.
    18.07.2017 15:58:17 4CE0 T IPAddressSet::InitialiseWithHost() called
    18.07.2017 15:58:17 4CE0 T Added host network address:192.168.0.2:0
    18.07.2017 15:58:17 4CE0 T Added host network address:127.0.0.1:0
    18.07.2017 15:58:17 4CE0 T IPAddressSet::InitialiseWithHost() returns
    18.07.2017 15:58:17 4CE0 D Creating ORB...
    18.07.2017 15:58:17 4CE0 I Creating ORB runner with 16 threads
    18.07.2017 15:58:17 1E78 D RunORB thread started
    18.07.2017 15:58:17 4C94 D RunORB thread started
    18.07.2017 15:58:17 4FFC D RunORB thread started
    18.07.2017 15:58:17 46E0 D RunORB thread started
    18.07.2017 15:58:17 322C D RunORB thread started
    18.07.2017 15:58:17 21B8 D RunORB thread started
    18.07.2017 15:58:17 4F3C D RunORB thread started
    18.07.2017 15:58:17 4594 D RunORB thread started
    18.07.2017 15:58:17 04EC D RunORB thread started
    18.07.2017 15:58:17 4978 D RunORB thread started
    18.07.2017 15:58:17 4080 D RunORB thread started
    18.07.2017 15:58:17 4474 D RunORB thread started
    18.07.2017 15:58:17 36B4 D RunORB thread started
    18.07.2017 15:58:17 3758 D RunORB thread started
    18.07.2017 15:58:17 4600 D RunORB thread started
    18.07.2017 15:58:17 0CC8 D RunORB thread started
    18.07.2017 15:58:18 4CE0 I Compliant certificate hashing algorithm.
    18.07.2017 15:58:18 4CE0 D Not requesting a new certificate.
    18.07.2017 15:58:18 4CE0 D Resolving the root object adapter...
    18.07.2017 15:58:18 4CE0 E This machine may have more IP addresses than are supported or the port may already be in use.
    18.07.2017 15:58:18 4CE0 E Router::Start: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
    TAO exception, minor code = 40 (endpoint initialization failure in Acceptor Registry; low 7 bits of errno: 64 Unknown error), completed = NO

    18.07.2017 15:58:18 4CE0 I Restarting...

  • 0 in reply to KingRolo

    What about full of errors from "C:\ProgramData\Sophos\Remote Management System\3\Agent\Logs\Agent-20170718-080534.log":

    18.07.2017 16:06:19 1F24 W MSClient::Connect: failed to get router's IOR from supplied address and port.
    18.07.2017 16:06:19 1F24 W NoRouterIORException: Caught MSClient::Connect: failed to get router's IOR from supplied address and port.
    ClientConnection::Reconnect()

     

    Log starts with:

    18.07.2017 10:05:34 16C0 I SOF: C:\ProgramData/Sophos/Remote Management System/3/Agent/Logs/Agent-20170718-080534.log
    18.07.2017 10:05:34 16C0 I Sophos Management Agent 4.1.0.140 starting...
    18.07.2017 10:05:34 16C0 I Starting AdapterManager ...
    18.07.2017 10:05:34 1F54 I Starting AdapterMonitor thread ...
    18.07.2017 10:05:34 1F54 I Loading new adapters: 1 registered adapters; 0 loaded adapters.
    18.07.2017 10:05:34 1F54 I Detected new adapter SDDM.
    18.07.2017 10:05:34 1F54 I Loading adapter SDDM ...
    18.07.2017 10:05:34 1F54 I SDDMA: Using host 127.0.0.1 and port 51234.
    18.07.2017 10:05:34 4998 I SDDMA: Connecting to SDDM...
    18.07.2017 10:05:34 4998 I SDDMA: An uninitialized socket was created.
    18.07.2017 10:05:34 4998 I SDDMA: Connection to SDDM successful.
    18.07.2017 10:05:34 4998 I SDDMA: Logon key written successfully.
    18.07.2017 10:05:34 1F54 I Adapter SDDM has been loaded successfully.
    18.07.2017 10:05:34 4998 I SDDMA: Logon key sent.
    18.07.2017 10:05:34 4998 I SDDMA: Socket connection authenticated.
    18.07.2017 10:05:34 4894 I SDDMA: IndicationsProcessor::ConnectionCallback() called.
    18.07.2017 10:05:34 37F0 I SDDMA: The adapter is connected to SDDM.
    18.07.2017 10:05:34 37F0 I SDDMA: Sending a Status Report upstream (forced)...
    18.07.2017 10:05:34 37F0 I SDDM state observer notified that SDDM is running
    18.07.2017 10:05:34 37F0 I SDDM state observer received a status: <?xml version="1.0" encoding="utf-8" ?><status xmlns="com.sophos\mansys\status" xmlns:csc="com.sophos\msys\csc" xmlns:xsi="www.w3.org/.../XMLSchema-instance" type="sddm"><csc:CompRes policyType="9" Res="Same" RevID="ebf82b11-a9cd-4d08-b05c-251bcf7d5ce1"/><csc:CompRes policyType="10" Res="Same" RevID="76c87d99-0e0d-4853-b02e-ba5aeb316b54"/><csc:CompRes policyType="11" Res="Same" RevID="09cdcf02-6673-45e2-9049-36619153b9aa"/><csc:CompRes policyType="12" Res="Same" RevID="5354a0ea-0371-4947-ba03-ad5bfd84adfa"/><csc:CompRes policyType="13" Res="Same" RevID="ea42c825-5324-46b4-9923-c34a66faa735"/><version number="1"/><updateManager xmlns="www.sophos.com/.../common.xsd" status="OK" softwareVersion="1.6.1.124"><updateOperation id="programsUpdate" lastNonNullFinishedAt="" lastFinishedAt="" /><updateOperation id="supplementsUpdate" lastNonNullFinishedAt="" lastFinishedAt="" /><defaultShare user="BIZILJ\master" password="Bwi18K5yyF80ZSQkQzBTD8FKbi2IrGnMUPU="/><currency></currency></updateManager></status>
    18.07.2017 10:05:34 37F0 I SDDMA: Status report dispatched.
    18.07.2017 10:05:36 16C0 I InitialiseClientLibraryLocal Agent, SOFTWARE\Sophos\Remote Management System\ManagementAgent\Private, , 1, ...

  • 0 in reply to KingRolo

    Hello Miha,

    these are caused by the router not listening.
    The verbose router log doesn't tell more - it looks like the router can't get the port, it might check all three though: 8192,8193,8194.

    Christian

  • 0 in reply to QC

    Hello QC!

    What do you advise?

    BR, Miha

  • 0 in reply to KingRolo

    Hello Miha,

    thanks - but I can't scroll in the screenshot [:D]. You say there isn't any output for 8194?

    I assume that RouterNT.exe creates a new process when restarting. In the screenshot it's the process with ID 3740, it listens (and even has two remote connections) on 8192 and should do so on 8193 and 8194 as well. Apparently it doesn't - what's the process with ID 3608 that listens on port 8193? 

    Christian

Unfiltered HTML