Zabbix_server stops sometimes by itself

[csf]

Hello,

Now the demon has died
Below there is last part of the zabbix_server.log:
......................
5663:20080213:093449 End update_triggers [31459]
5663:20080213:093449 Query [commit;]
5663:20080213:093449 In int_in_list(list:12884901888,value:10075)
5663:20080213:093449 End int_in_list(ret:FAIL)
5663:20080213:093449 In get_value(key:system.cpu.load)
5663:20080213:093449 In get_value_agent(host:snk-db,addr:172.16.6.153,key:system.cpu.load)
5663:20080213:093449 Sending [system.cpu.load
]
5663:20080213:093449 Before read
5663:20080213:093449 End get_value_agent(result:1.100000)
5663:20080213:093449 End get_value()
5663:20080213:093449 Query [begin;]
5663:20080213:093449 In process_new_value(system.cpu.load)
5663:20080213:093449 In add_history(key:system.cpu.load,value_type:0,type: 2)
5663:20080213:093449 In add_history(itemid:30889,DOUBLE:1.100000)
5663:20080213:093449 In add_history()
5663:20080213:093449 Query [insert into history (clock,itemid,value) values (1202891689,30889,1.100000)]
5663:20080213:093449 In add_trend()
5663:20080213:093449 Query [select num,value_min,value_avg,value_max from trends where itemid=30889 and clock=1202889600]
5663:20080213:093449 Query [insert into trends (clock,itemid,num,value_min,value_avg,value_max) values (1202889600,30889,1,1.100000,1.100000,1.100000)]
5663:20080213:093449 End of add_history
5663:20080213:093449 In update_item()
5663:20080213:093449 In calculate_item_nextcheck (30889,28800,0/1-5,07:00-16:59,1202891689)
5663:20080213:093449 Delay period [0/1-5,07:00-16:59]
5663:20080213:093449 0 sec at 1-5,07:00-16:59
5663:20080213:093449 In check_time_period(1-5,07:00-16:59)
5663:20080213:093449 Period [1-5,07:00-16:59]
5663:20080213:093449 1-5,7:0-16:59
5656:20080213:093449 One child process died. Exiting ...
5659:20080213:093449 Got signal. Exiting ...
5661:20080213:093449 Got signal. Exiting ...
5662:20080213:093449 Got signal. Exiting ...
5664:20080213:093449 Got signal. Exiting ...
5665:20080213:093449 Got signal. Exiting ...
5667:20080213:093449 Got signal. Exiting ...
5676:20080213:093449 Got signal. Exiting ...
5677:20080213:093449 Got signal. Exiting ...
5679:20080213:093449 Got signal. Exiting ...
5684:20080213:093449 Got signal. Exiting ...
5686:20080213:093449 Got signal. Exiting ...
5688:20080213:093449 Got signal. Exiting ...
5660:20080213:093449 Got signal. Exiting ...
5668:20080213:093449 Got signal. Exiting ...
5671:20080213:093449 Got signal. Exiting ...
5674:20080213:093449 Got signal. Exiting ...
5690:20080213:093449 Got signal. Exiting ...
5673:20080213:093449 Got signal. Exiting ...
5680:20080213:093449 Got signal. Exiting ...
5656:20080213:093451 ZABBIX Server stopped

[csf]

Hello All,

I am sorry, but really only I one have this problem ?
Here and now with version 1.4.5 all same.

Leonid.

[Alexei]

I do not think it is a good idea to have refresh rate set to 0 seconds. It seems that ZABBIX does not checks this in some cases. Probably division by zero or something like this has happened.

[csf]

Where there is this parameter ?
I cannot find.

[Alexei]

0/1-5,07:00-16:59

[csf]

OK.

I have removed this check.
Up to following time :>)


Many thanks for answer.

Leonid.

[csf]

Hello,


And again. This is End of zabbix_server.log:


29696:20080404:052725 Query [update triggers set value=1,lastchange=1207279645,error='' where triggerid=20766]
29696:20080404:052725 In process_event(eventid:0,object:0,objectid:20766)
29696:20080404:052725 Query [select description,priority,comments,url from triggers where triggerid=20766]
29696:20080404:052725 In get_latest_event_status(triggerid:20766
29696:20080404:052725 Query [select eventid,value,clock from events where source=0 and object=0 and objectid=20766 order by clock desc limit 2]
29696:20080404:052725 event_prev_status 1 event_last_status 0 event->value 1
29696:20080404:052725 In DBget_maxid(events,eventid)
29696:20080404:052725 Query [select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid']
29696:20080404:052725 Query [update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='eventid']
29696:20080404:052725 Query [select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid']
29696:20080404:052725 108309
29696:20080404:052725 Query [insert into events(eventid,source,object,objectid,clock,value) values(108309,0,0,20766,1207279645,1)]
29696:20080404:052725 In process_actions(source:TRIGGERS,eventid:108309)
29696:20080404:052725 Query [select actionid,evaltype,status,eventsource from actions where status=0 and eventsource=0 and actionid>=100000000000000*0 and actionid<=(100000000000000*0+99999999999999) ]
29696:20080404:052725 In check_action_conditions (actionid:4)
29696:20080404:052725 Query [select conditionid,actionid,conditiontype,operator,value from conditions where actionid=4 order by conditiontype]
29696:20080404:052725 In check_action_condition [actionid:4,conditionid:27,cond.value:20306]
29696:20080404:052725 CONDITION_TYPE_TRIGGER [20306:20306]
29696:20080404:052725 Condition is FALSE
29696:20080404:052725 End check_action_condition()
29696:20080404:052725 In check_action_condition [actionid:4,conditionid:28,cond.value:20476]
29696:20080404:052725 CONDITION_TYPE_TRIGGER [20476:20476]
29696:20080404:052725 Condition is FALSE
29696:20080404:052725 End check_action_condition()
29696:20080404:052725 In check_action_condition [actionid:4,conditionid:29,cond.value:20497]
29696:20080404:052725 CONDITION_TYPE_TRIGGER [20497:20497]
29696:20080404:052725 Condition is FALSE
29696:20080404:052725 End check_action_condition()
29696:20080404:052725 End check_action_conditions (result:FALSE)
29696:20080404:052725 Conditions do not match our event. Do not execute operations.
29696:20080404:052725 In check_action_conditions (actionid:7)
29696:20080404:052725 Query [select conditionid,actionid,conditiontype,operator,value from conditions where actionid=7 order by conditiontype]
29696:20080404:052725 In check_action_condition [actionid:7,conditionid:96,cond.value:20978]
29696:20080404:052725 CONDITION_TYPE_TRIGGER [20978:20978]
29696:20080404:052725 Condition is FALSE
29696:20080404:052725 End check_action_condition()
29696:20080404:052725 End check_action_conditions (result:FALSE)
29696:20080404:052725 Conditions do not match our event. Do not execute operations.
29696:20080404:052725 In check_action_conditions (actionid:8)
29696:20080404:052725 Query [select conditionid,actionid,conditiontype,operator,value from conditions where actionid=8 order by conditiontype]
29696:20080404:052725 In check_action_condition [actionid:8,conditionid:91,cond.value:10105]
29696:20080404:052725 Query [select distinct h.hostid from hosts h, items i, functions f, triggers t where h.hostid=i.hostid and i.itemid=f.itemid and f.triggerid=t.triggerid and t.triggerid=20766]
29696:20080404:052725 Condition is FALSE
29696:20080404:052725 End check_action_condition()
29696:20080404:052725 In check_action_condition [actionid:8,conditionid:90,cond.value:is unreachable]
29696:20080404:052725 In substitute_simple_macros()
29696:20080404:052725 In substitute_simple_macros (data:Processor load is too high on {HOSTNAME})
29696:20080404:052725 Query [select expression from triggers where triggerid=20766]
29695:20080404:052725 One child process died. Exiting ...
29699:20080404:052725 Got signal. Exiting ...
29700:20080404:052725 Got signal. Exiting ...
29701:20080404:052725 Got signal. Exiting ...
29703:20080404:052725 Got signal. Exiting ...
29704:20080404:052725 Got signal. Exiting ...
29705:20080404:052725 Got signal. Exiting ...
29707:20080404:052725 Got signal. Exiting ...
29713:20080404:052725 Got signal. Exiting ...
29714:20080404:052725 Got signal. Exiting ...
29717:20080404:052725 Got signal. Exiting ...
29718:20080404:052725 Got signal. Exiting ...
29719:20080404:052725 Got signal. Exiting ...
29720:20080404:052725 Got signal. Exiting ...
29721:20080404:052725 Got signal. Exiting ...
29722:20080404:052725 Got signal. Exiting ...
29723:20080404:052725 Got signal. Exiting ...
29724:20080404:052725 Got signal. Exiting ...
29732:20080404:052725 Got signal. Exiting ...
29733:20080404:052725 Got signal. Exiting ...
29734:20080404:052725 Got signal. Exiting ...
29736:20080404:052725 Got signal. Exiting ...
29740:20080404:052725 Got signal. Exiting ...
29742:20080404:052725 Got signal. Exiting ...
29744:20080404:052725 Got signal. Exiting ...
29746:20080404:052725 Got signal. Exiting ...
29698:20080404:052725 Got signal. Exiting ...
29702:20080404:052725 Got signal. Exiting ...
29709:20080404:052725 Got signal. Exiting ...
29748:20080404:052725 Got signal. Exiting ...
29697:20080404:052725 Got signal. Exiting ...
29695:20080404:052727 ZABBIX Server stopped

[csf]

Hello Alexei,

Have you any ideas in last case ?

[ploochan]

did anyone find out why the agent stops by itself? I have version 1.430 and from time to time the agents stops.
many thanks,

[rafael]

Zabbix Server Stopped

has any one solve this issue.

I am having the same issue. It started on version 1.6.4, I then upgrade it to 1.6.6 and the problem continues.


--------------------------------------------------------------------------
1530:20100106:123227 Query [select min(clock) from history_uint where itemid=200200000018101]
1526:20100106:123227 One child process died. Exiting ...
1530:20100106:123227 In delete_history(history_str,200200000018101,3132757 0199,1262799127)
1527:20100106:123227 Got signal. Exiting ...
1529:20100106:123227 Got signal. Exiting ...
1528:20100106:123227 Got signal. Exiting ...
1531:20100106:123227 Got signal. Exiting ...
1532:20100106:123227 Got signal. Exiting ...
1533:20100106:123227 Got signal. Exiting ...
1535:20100106:123227 Got signal. Exiting ...
1530:20100106:123227 Got signal. Exiting ...
1540:20100106:123227 Got signal. Exiting ...
1526:20100106:123229 Query [SET CHARACTER SET utf8]
1526:20100106:123229 In free_database_cache()
1526:20100106:123229 End of free_database_cache()
1526:20100106:123229 ZABBIX Server stopped. ZABBIX 1.6.6 (revision 7836).

[jthakrar]

I have seen similar issues when running some "custom agent" (DB2) using Zabbix 1.8.
(Atleast I saw the child process exit message).

Can you check if in your script you do an exit with a non-zero exit code?

I had them to handle "abnormal conditions" and whenever those conditions occurred, Zabbix would die.

Long story short, check your script and "recode" exit NN to exit 0.

-- Jayesh