Ad Widget

Collapse

Proxy failing to accept active agents

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • highpeak
    Member
    • Nov 2019
    • 30

    #1

    Proxy failing to accept active agents

    Proxy: 5.2.5 psql
    OS: ubuntu 18.04

    Since the upgrade, at random intervals I sueendly see the below entry in the Zabbix proxy log. The IP listed (172.16.8.27) is the IP of the zabbix proxy.

    Code:
    3007:20210313:150613.227 failed to accept an incoming connection: from 172.16.8.27: reading first byte from connection failed: [104] Connection reset by peer
    3005:20210313:150613.228 failed to accept an incoming connection: from 172.16.8.27: reading first byte from connection failed: [104] Connection reset by peer
    3005:20210313:150613.228 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3005:20210313:150613.228 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3006:20210313:150613.228 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3007:20210313:150613.231 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3004:20210313:150613.232 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3004:20210313:150613.232 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3004:20210313:150613.232 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    3006:20210313:150613.232 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected
    From this point on, all active agent updates are rejected.
  • lptarik
    Member
    • Oct 2021
    • 33

    #2
    Hello did you able to solve issue?

    Comment

    • highpeak
      Member
      • Nov 2019
      • 30

      #3
      I’m afraid I didn’t. I ended up splitting the proxy into two and applying a regular reboot schedule which has prevented a recurrence. But I don’t know what the root cause was.

      Comment

      • santosra02
        Junior Member
        • May 2023
        • 21

        #4
        Hi

        I managed to fix this error in my zabbix proxy just enabling the parameter "StartTrappers=17" in zabbix_proxy.conf and restarting the service.
        Last edited by santosra02; 10-10-2024, 11:06.

        Comment

        Working...