Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 0 subscribers
  • Views 26942 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

Endpoints show as disconnected in Enterprise Console

TR27

Hi,

My setup is as follows:

  • 10 servers on a domain
  • 1 standalone server, not on the domain
  • Enterprise Console installed on the server not in the domain, all servers protected
  • I installed Sophos on all servers by manually browsing to x.x.x.x\SophosUpdate\CIDs\S000\SAVSCFXP and running the setup file.
  • All servers show up and are arranged into their respective policy groups in Enterprise Console and all can update fine.

My issue is that after a couple of days the servers eventually show as if they're disconnected and have a red X through them. They can still update fine but they show as disconnected.  If i re-run the setup file this will keep them connected in the Console for another couple of days, until they eventually drop off again.

I am not sure where to troubleshoot? I was told that installing SEC on a non-member server would not be an issue, so i am not too sure what is causing the endpoints to drop off. Any ideas would be appreciated?

:48214


This thread was automatically locked due to age.
Parents
  • 0

    Thanks for the response. It does look like an issue in sending the logoff message. I have found this from 3 separate endpoints:

    ENDPOINT 1:

    05.03.2014 14:53:27 09CC E GetterWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO
    05.03.2014 14:53:27 09CC E Failed to get messages, logging Router$XXXX off
    05.03.2014 14:53:53 09AC E Failed to send message (id=01169EA1) because of unknown exception, adding message back to queue
    05.03.2014 14:53:53 09AC E Failed to send messages, logging Router$XXXX off
    05.03.2014 14:53:53 09AC E SenderWorker: Caught CORBA user exception, ID 'IDL:SophosMessaging/NotLoggedOn:1.0' during logoff
    05.03.2014 14:53:53 09AC E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0'
    Unknown vendor minor code id (0), minor code = 0, completed = NO

    ENDPOINT2:
    05.03.2014 14:51:10 0C28 E Failed to send message (id=01169CAD) because of unknown exception, adding message back to queue
    05.03.2014 14:51:10 0C28 E Failed to send messages, logging Router$XXXX off
    05.03.2014 14:51:10 0C28 E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO

    ENDPOINT 3:
    05.03.2014 14:43:00 0F84 I Routing to parent: id=01169D44, origin=Router$XXXXX:9012.Agent, dest=EM, type=EM-GetStatus-Reply
    05.03.2014 14:53:22 0564 E Failed to send message (id=01169D31) because of unknown exception, adding message back to queue
    05.03.2014 14:53:22 0564 E Failed to send messages, logging Router$XXXX off
    05.03.2014 14:53:22 0564 E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO

    Have you seen this error before?

    Given that they all occured around the same time I am assuming that would  indicate a network issue?

    :48234
Reply
  • 0

    Thanks for the response. It does look like an issue in sending the logoff message. I have found this from 3 separate endpoints:

    ENDPOINT 1:

    05.03.2014 14:53:27 09CC E GetterWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO
    05.03.2014 14:53:27 09CC E Failed to get messages, logging Router$XXXX off
    05.03.2014 14:53:53 09AC E Failed to send message (id=01169EA1) because of unknown exception, adding message back to queue
    05.03.2014 14:53:53 09AC E Failed to send messages, logging Router$XXXX off
    05.03.2014 14:53:53 09AC E SenderWorker: Caught CORBA user exception, ID 'IDL:SophosMessaging/NotLoggedOn:1.0' during logoff
    05.03.2014 14:53:53 09AC E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0'
    Unknown vendor minor code id (0), minor code = 0, completed = NO

    ENDPOINT2:
    05.03.2014 14:51:10 0C28 E Failed to send message (id=01169CAD) because of unknown exception, adding message back to queue
    05.03.2014 14:51:10 0C28 E Failed to send messages, logging Router$XXXX off
    05.03.2014 14:51:10 0C28 E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO

    ENDPOINT 3:
    05.03.2014 14:43:00 0F84 I Routing to parent: id=01169D44, origin=Router$XXXXX:9012.Agent, dest=EM, type=EM-GetStatus-Reply
    05.03.2014 14:53:22 0564 E Failed to send message (id=01169D31) because of unknown exception, adding message back to queue
    05.03.2014 14:53:22 0564 E Failed to send messages, logging Router$XXXX off
    05.03.2014 14:53:22 0564 E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO

    Have you seen this error before?

    Given that they all occured around the same time I am assuming that would  indicate a network issue?

    :48234
Children
No Data
Unfiltered HTML