Ad Widget

Collapse

Hi some Problems with 1.1 (Server)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • axel
    Member
    • Aug 2005
    • 36

    #1

    Hi some Problems with 1.1 (Server)

    Code:
    003152:20060607:151406 ZABBIX server is up.
    zabbix_server: db.c:1577: DBescape_string: Assertion `from' failed.
    003152:20060607:151503 One server process died. Shutting down...
    003152:20060607:151503 ZABBIX server is down.
  • axel
    Member
    • Aug 2005
    • 36

    #2
    Code:
    026243:20060608:093902 Processing [99,6595]
    026243:20060608:093902 In process_new_value()
    026243:20060608:093902 In add_history(cpuidle,,2,4)
    026243:20060608:093902 In add_history(17319,STRING:99,6595)
    026243:20060608:093902 In add_history_log()
    026214:20060608:093902 One server process died. Shutting down...
    026214:20060608:093902 0. Killing PID=[26226]
    026214:20060608:093902 1. Killing PID=[26227]
    026214:20060608:093902 2. Killing PID=[26228]
    026214:20060608:093902 3. Killing PID=[26231]
    026214:20060608:093902 4. Killing PID=[26232]
    026214:20060608:093902 5. Killing PID=[26233]
    026214:20060608:093902 6. Killing PID=[26238]
    026214:20060608:093902 7. Killing PID=[26239]
    026214:20060608:093902 8. Killing PID=[26240]
    026214:20060608:093902 9. Killing PID=[26241]
    026214:20060608:093902 10. Killing PID=[26242]
    026214:20060608:093902 11. Killing PID=[26243]
    026214:20060608:093902 12. Killing PID=[26246]
    026214:20060608:093902 13. Killing PID=[26247]
    026214:20060608:093902 14. Killing PID=[26248]
    026214:20060608:093902 ZABBIX server is down.
    026228:20060608:093902 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiti
    ng...
    026226:20060608:093902 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026227:20060608:093902 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026231:20060608:093902 Server [4]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026232:20060608:093902 Server [5]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026233:20060608:093902 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026238:20060608:093902 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026239:20060608:093902 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026240:20060608:093902 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026241:20060608:093902 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026246:20060608:093902 Server [13]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026247:20060608:093902 Server [14]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026248:20060608:093902 Server [15]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    026242:20060608:093902 Server [11]. Got QUIT or INT or TERM or PIPE signal. Exiting.... Exit
    Last edited by axel; 08-06-2006, 09:49.

    Comment

    • axel
      Member
      • Aug 2005
      • 36

      #3
      OK i think i know now why the server is going down.

      I have 3 Checks with sender

      Example

      026243:20060608:093902 In add_history(cpuidle,,2,4)
      026243:20060608:093902 In add_history(17319,STRING:99,6595)
      "After this server crash"

      My Sender Check

      /usr/bin/zabbix_sender localhost 10051 MA-Gateway cpuidle `grep cpuidle /tmp/gateway_zabbix.txt |cut -d\ -f2`

      /usr/bin/zabbix_sender localhost 10051 MA-Gateway cpuidle 99,6595

      i Think the value "99,6595" make the Problem ?

      If i stop the sender checks i have no problems
      Last edited by axel; 08-06-2006, 13:36.

      Comment

      • sauron
        Senior Member
        • Jan 2005
        • 215

        #4
        My the value "99,6595" make the Problem ?
        Yep. Need 99.6595.

        Comment

        Working...