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

Endpoint Reporting issue: via Message Router

Hi ,

I have Message router services installed to manage Roaming users. we have abt 200 roming users installed and it worked perfect almost for 10 months.

Issue : now we have more then 80% users are not reporting on console.

User are abel to download latest defenation file from message router. but not able to get new policy updates from server below is the log which i am getting on sophos message routers.

24.04.2014 17:00:17 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:00:17 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:00:47 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:00:47 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:00:48 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:00:48 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:00:50 08BC I Logged off Router$Phiangailiu-Christie:216028
24.04.2014 17:00:50 1394 I Routing to parent: id=0158F5EA, origin=Router$SCDELADC01:2385266, dest=EM, type=EM-RouterLogoff
24.04.2014 17:00:50 0C58 I Sent message (id=0158F5EA) to Router$scdelav01
24.04.2014 17:00:55 08BC I RouterTableEntry state (router, logging on): Router$Phiangailiu-Christie:216028 is active consumer (will try to notify), active supplier
24.04.2014 17:00:55 08BC I Writing router table file
24.04.2014 17:00:55 08BC W Notification threshold calls will not be attempted, because the number of notification threshold threads is 0
24.04.2014 17:00:55 08BC I Logged on Router$Phiangailiu-Christie:216028 as a router
24.04.2014 17:00:55 1394 I Routing to parent: id=0158F5EF, origin=Router$SCDELADC01:2385266, dest=EM, type=EM-RouterLogon
24.04.2014 17:00:55 1280 I Sent message (id=0158F5EF) to Router$scdelav01
24.04.2014 17:01:06 1394 I Routing to parent: id=0158F58A, origin=Router$Phiangailiu-Christie:216028.Agent, dest=EM, type=EM-EntityEvent
24.04.2014 17:01:06 0D2C I Sent message (id=0158F58A) to Router$scdelav01
24.04.2014 17:01:19 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:01:19 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:01:19 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:01:19 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:01:33 1394 I Routing to parent: id=0158F5A4, origin=Router$Phiangailiu-Christie:216028.Agent, dest=EM, type=EM-GetStatus-Reply
24.04.2014 17:01:33 0C58 I Sent message (id=0158F5A4) to Router$scdelav01
24.04.2014 17:01:50 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:01:50 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:01:51 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:01:51 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:02:22 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:02:22 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:02:23 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:02:23 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:02:55 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:02:55 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:02:55 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:02:55 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:03:26 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:03:26 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:03:26 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:03:26 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:03:57 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:03:57 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:03:57 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:03:57 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:04:28 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:04:28 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:04:28 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:04:28 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=1358F6C8, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=2758F6C8, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=3B58F6C8, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=4F58F6C8, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=6358F6C8, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=7758F6C8, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=0158F6C9, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:32 1394 I Routing to Router$RJSPO-SPARE:2484277: id=1558F6C9, origin=Router$scdelav01.EM, dest=Router$SCDELADC01:2385266.Router$RJSPO-SPARE:2484277.Agent, type=EM-SetConfiguration
24.04.2014 17:04:59 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:04:59 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:05:00 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:05:00 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:05:31 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:05:31 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:05:32 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:05:32 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:06:02 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:06:02 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:06:03 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:06:03 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:06:36 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:06:36 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:06:37 08BC W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:06:37 08BC E ACE_SSL (3020|2236) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:07:04 1394 I Routing to parent: id=0158F760, origin=Router$SCDELADC01:2385266.Agent, dest=EM, type=EM-GetStatus-Reply
24.04.2014 17:07:04 0C58 I Sent message (id=0158F760) to Router$scdelav01
24.04.2014 17:07:08 12C8 W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:07:08 12C8 E ACE_SSL (3020|4808) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
24.04.2014 17:07:08 128C W SSL connection alert, peer address 192.168.1.120
24.04.2014 17:07:08 128C E ACE_SSL (3020|4748) error code: 336151570 - error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
:49342


This thread was automatically locked due to age.
  • Hello se_ure,

    a remark first:

    User are able to download latest definition

    Updating (AutoUpdate) is not related to messaging (RMS),  furthermore a message relay is not necessarily a SUM (or has to host a CID). Thus one might work while the other fails.

    Is this log from a message relay (and is this relay your only one)? Looks like it works in principle, scdelav01 is your management server and endpoint messages are passed to it (from Phiangailiu-Christie and SCDELADC01) and policies sent from it are passed to an endpoint (RJSPO-SPARE).

    In this snippet the trouble seems to be with the device at 192.168.1.120 - is this an endpoint and are there (many) more addresses which fail the same way? And the inevitable question - has something been changed? BTW - which product versions are in use?

    Christian

    :49344