TLS connection has been closed during handshake

[davidbred]

We keep experiencing a situation where the zabbix queue spikes up to 36k missing items and when we check the logs we see the following.

26640:20170210:131226.819 failed to accept an incoming connection: from 10.x.x.x: TLS connection has been closed during handshake

We know this has happened when there have been networking issues and once the server gets into this state we have to restart the zabbix server service to get it to start working again.

RHEL 6 server and all agents are using encryption. Just wondering if anyone else has run into this.

[ayoub]

Same issue

Hello,

I have the same Issue on my agents

[andris]

We keep experiencing a situation where the zabbix queue spikes up to 36k missing items and when we check the logs we see the following.

26640:20170210:131226.819 failed to accept an incoming connection: from 10.x.x.x: TLS connection has been closed during handshake

We know this has happened when there have been networking issues and once the server gets into this state we have to restart the zabbix server service to get it to start working again.

Could be a bug, if server restart is required.
Consider opening a bug report at https://support.zabbix.com.

[ayoub]

Resolved for me

Hello

I found what was the problem !

On my Zabbix server, I forgot to set the network mask (NETMASK) so it was 10.1.1.1/32 when it shoud be 10.1.1.1/24

And I could access it using SSH even with the /32 NETMASK that's why I couldn't detect it from the first sight and even I didn't thought that it was a Network configuration issue on THE SERVER

[Surya.p]

Can some one plz help me to resolve this
failed to accept an incoming connection: from x.x.x.x: TLS connection has been closed during handshake