Ad Widget

Collapse

Hosts - ZBX_TCP_READ() failed [Interrupted system call]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • uwe
    Junior Member
    • Nov 2008
    • 2

    #1

    Hosts - ZBX_TCP_READ() failed [Interrupted system call]

    Hello

    i added a host with Template_linux - the monitoring works for some days.
    But now i get the error "ZBX_TCP_READ() failed [Interrupted system call]".
    Change from ip to dns and back, restart agentd and server nothing helps. It does not work for 2 days now.
    For testing i cloned the host and now the monitoring works again. OK but this can not be a reliable solution.
    How can it be? Is a that problem of the zabbix-database or depends it on the
    history?

    Greetings
    uwe
  • mlange
    Member
    • Sep 2008
    • 78

    #2
    We had this problem too (but using Zapcat agent) but couldn't find a satisfying solution. Restarting the monitored server made the problem disappear. This is caused by a lot of open connections (which probably reach an os limitation) and zabbix is not able to connect to the instance. You can have a look here: http://www.zabbix.com/forum/showthread.php?p=38289

    Comment

    • uwe
      Junior Member
      • Nov 2008
      • 2

      #3
      zabbix-server stop and dead processes

      Hello mlange

      thanks for your hint.
      I did zabbix-server stop and after that i saw many zabbix-prossess on ps aux.
      So i killed them, starting zabbix-server und the error was gone. It seems to be a problem on zabbix server. Syslog does not have an error message. Zabbix_server.log - i did not have the log of that problem day.
      We will see next days...

      Zabbix Monitoring for this server works on until now, but gives no error on zabbix itself. That means we need another kind of monitoring processes in zabbix.

      Greetings
      uwe

      Comment

      • jobauer
        Junior Member
        • Dec 2009
        • 1

        #4
        Get value from agent failed: ZBX_TCP_READ()

        I have the same issue. get monitoring values via zapcat works for some hours and then stop. I use zabbix 1.6.6 and zapcat 1.2 (also tried 1.3-beta same issue).

        Logfile on zabbix server:
        29387:20091215:115210 Item [solr461]jmx[Catalina:type=Server][serverInfo]] error: Get value from agent failed: ZBX_TCP_READ() failed [Interrupted system call]

        Logfile on client (zapcat 1.3-beta in DEBUG mode):
        20091215 115100,071 org.kjkoster.zapcat.zabbix.ZabbixAgent DEBUG - accepted connection from 10.38.22.15
        20091215 115205,121 org.kjkoster.zapcat.zabbix.ZabbixAgent DEBUG - accepted connection from 10.38.22.15
        20091215 115310,176 org.kjkoster.zapcat.zabbix.ZabbixAgent DEBUG - accepted connection from 10.38.22.15


        normally this looks like this:
        20091215 045108,841 org.kjkoster.zapcat.zabbix.ZabbixAgent DEBUG - accepted connection from 10.38.22.15
        20091215 045108,841 org.kjkoster.zapcat.zabbix.QueryHandler DEBUG - started worker
        20091215 045108,841 org.kjkoster.zapcat.zabbix.QueryHandler DEBUG - received 'jmx[Catalina:type=ThreadPool,name=jk-11012][currentThreadsBusy]'
        20091215 045108,841 org.kjkoster.zapcat.zabbix.JMXHelper DEBUG - JMX query[Catalina:type=ThreadPool,name=jk-11012][currentThreadsBusy]
        20091215 045108,841 org.kjkoster.zapcat.zabbix.JMXHelper DEBUG - found MBean class org.apache.tomcat.util.modeler.BaseModelMBean
        20091215 045108,842 org.kjkoster.zapcat.zabbix.QueryHandler DEBUG - sending '1'
        20091215 045108,842 org.kjkoster.zapcat.zabbix.QueryHandler DEBUG - sent bytes 5a 42 58 44 01 01 00 00 00 00 00 00 00 31
        20091215 045108,842 org.kjkoster.zapcat.zabbix.QueryHandler DEBUG - worker is done
        20091215 045111,718 org.kjkoster.zapcat.zabbix.ZabbixAgent DEBUG - accepted connection from 10.38.22.15
        20091215 045111,719 org.kjkoster.zapcat.zabbix.QueryHandler DEBUG - started worker

        has anybody else seen this? Which versions of zabbix and zapcat are recommended? Anything i can do for further testing?

        Thanks a lot in advance
        joseph

        Comment

        • mlange
          Member
          • Sep 2008
          • 78

          #5
          There is no newer version of the Java Agent available. I assume that the number of requests on the agent is too high. We are having a lot of these errors in the logs but they obviously don't seem to break anything.

          Comment

          Working...