Ad Widget

Collapse

ZBX_TCP_READ() failed error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • netwrm
    Junior Member
    • Mar 2008
    • 2

    #1

    ZBX_TCP_READ() failed error

    I am getting this error ons some of my hosts using Zabbix 1.4.4

    I fixed this by restarting the zabbix agend on the host server. Was wondering what causes it.
  • nelsonab
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2006
    • 1233

    #2
    I haven't gone and and read the source, but from experience it happens when the TCP link between agent and server has been created and is broken before the Server expects it to be torn down. It usually happens as one of two types from what I've seen either "Interrupted System Call" or "Connection reset by peer". The first "Interrupted System Call" happens when the agent takes too long to respond and an internal timeout counter in the server kills the link. I think the threshold is 30 seconds. The second occurs when the link has been created, the server tries to send data but the link dies for whatever reason.

    This is one of the more common error messages you will find in Zabbix and at times one of the most frustrating to debug, and usually it comes down to one tiny little stupid mistake.

    WOO HOO!!! 100th post... I think I'll go drink now...
    RHCE, author of zbxapi
    Ansible, the missing piece (Zabconf 2017): https://www.youtube.com/watch?v=R5T9NidjjDE
    Zabbix and SNMP on Linux (Zabconf 2015): https://www.youtube.com/watch?v=98PEHpLFVHM

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      Originally posted by nelsonab
      WOO HOO!!! 100th post... I think I'll go drink now...
      Just in case you are back already, the low level messages like this will be eliminated at some point. The messages do not provide any valuable information, they are confusing!
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • netwrm
        Junior Member
        • Mar 2008
        • 2

        #4
        tks guys

        tks guys it is appreciated!

        Comment

        • nelsonab
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Sep 2006
          • 1233

          #5
          Originally posted by Alexei
          Just in case you are back already, the low level messages like this will be eliminated at some point. The messages do not provide any valuable information, they are confusing!
          I would say don't get rid of it, but rather change the error message into something more meaningful. "Connection to agent took too long" would make for a much better error message for the timeout or "No reply from agent within X seconds."

          I believe make the error messages more descriptive and the "silly" problems people post about will reduce greatly.

          but that's just my 1.71 cents... damm dollar devaluation...
          RHCE, author of zbxapi
          Ansible, the missing piece (Zabconf 2017): https://www.youtube.com/watch?v=R5T9NidjjDE
          Zabbix and SNMP on Linux (Zabconf 2015): https://www.youtube.com/watch?v=98PEHpLFVHM

          Comment

          • Alexei
            Founder, CEO
            Zabbix Certified Trainer
            Zabbix Certified SpecialistZabbix Certified Professional
            • Sep 2004
            • 5654

            #6
            I fully agree with you.
            Alexei Vladishev
            Creator of Zabbix, Product manager
            New York | Tokyo | Riga
            My Twitter

            Comment

            Working...