Ad Widget

Collapse

Server Process quits after receiving data from windows client

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • abi
    Member
    • Jun 2006
    • 81

    #1

    Server Process quits after receiving data from windows client

    hi,

    for some weeks now every now and then, our zabbix server suddenly quits
    after receiving data from a certain windows host. Ive already tried to update
    the client and server to the latest version and it doesnt help. Ive also tried
    to truncate the history table etc etc.. heres the log:

    004268:20070129:085223 In add_history(19076,STRING:SBYTRA75)
    004274:20070129:085223 In send_list_of_active_checks()
    004268:20070129:085223 In add_history_log()
    004269:20070129:085223 RESULT_STR [ ]
    004269:20070129:085223 In process_new_value()
    004269:20070129:085223 In add_history(net.if.out[eth0],,0,2)
    004269:20070129:085223 In add_history(19011,DOUBLE:215028815.000000)
    004261:20070129:085223 One server process died. Shutting down...
    004269:20070129:085223 In add_history()
    004261:20070129:085223 0. Killing PID=[4262]
    004269:20070129:085223 Executing query:insert into history (clock,itemid,value) values (1170057143,19011,215028815.000000)
    004263:20070129:085223 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004266:20070129:085223 In add_trend()
    004266:20070129:085223 SQL [select num,value_min,value_avg,value_max from trends where itemid=18246 and clock=1170054000]
    004266:20070129:085223 Executing query:select num,value_min,value_avg,value_max from trends where itemid=18246 and clock=1170054000
    004274:20070129:085223 Executing query:select i.key_,i.delay,i.lastlogsize from items i,hosts h where i.hostid=h.hostid and h.status=0 and i.status=0 and i.type=7 a
    nd h.host='localhost'
    004262:20070129:085223 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004261:20070129:085223 1. Killing PID=[4263]
    004261:20070129:085223 2. Killing PID=[4264]
    004264:20070129:085223 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004265:20070129:085223 Server [4]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004261:20070129:085223 3. Killing PID=[4265]
    004269:20070129:085223 In add_trend()
    004261:20070129:085223 4. Killing PID=[4266]
    004269:20070129:085223 SQL [select num,value_min,value_avg,value_max from trends where itemid=19011 and clock=1170054000]
    004261:20070129:085223 5. Killing PID=[4267]
    004269:20070129:085223 Executing query:select num,value_min,value_avg,value_max from trends where itemid=19011 and clock=1170054000
    004261:20070129:085223 6. Killing PID=[4268]
    004261:20070129:085223 7. Killing PID=[4269]
    004266:20070129:085223 Server [5]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004270:20070129:085223 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004261:20070129:085223 8. Killing PID=[4270]
    004269:20070129:085223 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004261:20070129:085223 9. Killing PID=[4271]
    004261:20070129:085223 10. Killing PID=[4272]
    004261:20070129:085223 11. Killing PID=[4273]
    004261:20070129:085223 12. Killing PID=[4274]
    004261:20070129:085223 13. Killing PID=[4275]
    004261:20070129:085223 14. Killing PID=[4276]
    004261:20070129:085223 ZABBIX server is down.
    004271:20070129:085223 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004272:20070129:085223 Server [11]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004275:20070129:085223 Server [14]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004273:20070129:085223 Server [12]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004276:20070129:085223 Server [15]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004274:20070129:085223 Server [13]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    004267:20070129:085223 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
    One strange thing: after disabling the host for monitoring a couple of
    days, it starts working again, a few weeks, until the server suddenly
    decides he doesnt like data from this host
    Last edited by abi; 07-02-2007, 14:34.
Working...