Ad Widget

Collapse

Active Checks cause Zabbix to shut down

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jwhitby
    Junior Member
    • Mar 2007
    • 2

    #1

    Active Checks cause Zabbix to shut down

    I have been using zabbix for quite some time now to monitor several hundred hosts via SNMP. I recently decided to try and use the zabbix agent on 10 windows 2003 machines instead of SNMP polling. However after starting the agent as soon as it makes contact with the zabbix server the process shuts down.

    I also did a clean install of zabbix with the same results. Truncated log is below.


    Code:
    011419:20070316:121100 Sleeping for 5 seconds
    011435:20070316:121100 No items to update for minnextcheck.
    011435:20070316:121100 Nextcheck:-1 Time:1174047060
    011435:20070316:121100 Sleeping for 5 seconds
    011446:20070316:121100 After accept()
    011446:20070316:121100 In process_trapper_child
    011446:20070316:121100 Before read(65000)
    011446:20070316:121100 Read 29 bytes
    011446:20070316:121100 After read() 3 [29]
    011446:20070316:121100 Got data:ZBX_GET_ACTIVE_CHECKS
    aeWP-1
    
    011446:20070316:121100 Trapper got [ZBX_GET_ACTIVE_CHECKS
    aeWP-1]
    011446:20070316:121100 In autoregister(aeWP-1)
    011446:20070316:121100 Executing query:select hostid from hosts where host='aeWP-1'
    011446:20070316:121100 Query::select hostid from hosts where host='aeWP-1'
    011446:20070316:121100 Query failed:MySQL server has gone away [2006]
    011415:20070316:121100 One server process died. Shutting down...
    011415:20070316:121100 0. Killing PID=[11416]
    011415:20070316:121100 1. Killing PID=[11417]
    011415:20070316:121100 2. Killing PID=[11418]
    011419:20070316:121100 Server [4]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 3. Killing PID=[11419]
    011420:20070316:121100 Server [5]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 4. Killing PID=[11420]
    011421:20070316:121100 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 5. Killing PID=[11421]
    011422:20070316:121100 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 6. Killing PID=[11422]
    011426:20070316:121100 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 7. Killing PID=[11426]
    011427:20070316:121100 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 8. Killing PID=[11427]
    011428:20070316:121100 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 9. Killing PID=[11428]
    011429:20070316:121100 Server [11]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 10. Killing PID=[11429]
    011431:20070316:121100 Server [12]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 11. Killing PID=[11431]
    011433:20070316:121100 Server [13]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 12. Killing PID=[11433]
    011435:20070316:121100 Server [14]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011415:20070316:121100 13. Killing PID=[11435]
    011415:20070316:121100 14. Killing PID=[11437]
    011415:20070316:121100 15. Killing PID=[11440]
    011415:20070316:121100 16. Killing PID=[11442]
    011415:20070316:121100 17. Killing PID=[11444]
    011415:20070316:121100 18. Killing PID=[11446]
    011415:20070316:121100 ZABBIX server is down.
    011416:20070316:121100 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011418:20070316:121100 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011437:20070316:121100 Server [15]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011440:20070316:121100 Server [16]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011442:20070316:121100 Server [17]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011444:20070316:121100 Server [18]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    011417:20070316:121100 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...

    If I bypass the process_trap() function in trapper.c by putting a return statement at the top of the function zabbix will keep running when an agent checks in, but of course autoregister and active checks won't work.


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

    #2
    I believe the problem has been fixed in the latest 1.1.x.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • jwhitby
      Junior Member
      • Mar 2007
      • 2

      #3
      This was done with a fresh install of 1.1.6

      Comment

      • welkin
        Senior Member
        • Mar 2007
        • 132

        #4
        I got the same Problem and i'm using Version : 1.1.6
        Maybe someone can supply a patch ?
        mfg
        welkin
        Last edited by welkin; 19-03-2007, 10:42.

        Comment

        Working...