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

Security Heartbeat stopped working in 17.0.6 MR-6

Hi,

I'm Facing a problem with Heartbeat its stopped suddenly and the counter showing 0 and there is no logs at all when I checked the logs I found there is a certificate issue  so please anyone face the same problem and how do I fix it, I have opened a ticket with the support for more than 3 weeks until now they didn't fix it.

 

=================================

2018-04-22 17:13:22 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.104.7: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:23 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.15.3: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:23 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:23 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.24.2: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:23 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:23 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.99.2: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:23 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:23 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.36.11: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:24 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:24 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.99.16: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:26 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:27 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.212.4: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:29 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:29 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.102.8: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:30 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:30 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.212.2: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:31 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:31 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.38.3: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:32 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:32 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.208.9: unknown reason. Maybe server certificate not yet received by client.
2018-04-22 17:13:32 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:32 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.107.20: unknown reason. Maybe server certificate not yet received by client.
ep_cert.crt2018-04-22 17:13:33 INFO HBSessionHandler.cpp[4776]:89 removeDirtySessions - Number of sessions: 0
2018-04-22 17:13:34 WARN HBSession.cpp[4776]:334 bufferDisconnectEvent - Client connection failure from 172.17.12.9: unknown reason. Maybe server certificate not yet received by client.

 



This thread was automatically locked due to age.
Parents Reply Children