Zabbax-Server Stops after unexpected SQL-Result
Hello,
I can't exactly tell why, but suddenly our zabbix-server cannot be started anymore becaues it immediately stops after an probably unexpected Result from a query:
021770:20070125:130035 Executing query:select min(clock) from trends where itemid=10036
021770:20070125:130035 In delete_history(history,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history where itemid=10037
021770:20070125:130035 In delete_history(history_uint,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_uint where itemid=10037
021770:20070125:130035 In delete_history(history_str,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_str where itemid=10037
021770:20070125:130035 In delete_history(history_str,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_str where itemid=10037
021770:20070125:130035 In delete_history(history_log,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_log where itemid=10037
021770:20070125:130035 In delete_history(trends,10037,365,1169726435)
021770:20070125:130035 Executing query:select min(clock) from trends where itemid=10037
021793:20070125:130035 RESULT_STR [Ð]
021793:20070125:130035 In process_new_value()
021793:20070125:130035 In add_history(pdns.uptime,,2,4)
021793:20070125:130035 In add_history(17778,STRING:18.9 days)
021793:20070125:130035 In add_history_log()
021770:20070125:130035 One server process died. Shutting down...
021784:20070125:130035 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 0. Killing PID=[21784]
021786:20070125:130035 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 1. Killing PID=[21786]
021788:20070125:130035 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 2. Killing PID=[21788]
021792:20070125:130035 Server [4]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 3. Killing PID=[21792]
021770:20070125:130035 4. Killing PID=[21793]
021794:20070125:130035 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 5. Killing PID=[21794]
021796:20070125:130035 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 6. Killing PID=[21796]
021797:20070125:130035 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 7. Killing PID=[21797]
021799:20070125:130035 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 8. Killing PID=[21799]
021801:20070125:130035 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 9. Killing PID=[21801]
021770:20070125:130035 ZABBIX server is down.
How can I work around this ? I do not mind loosing all data from the past, but I do not want to setup all the triggers, users and stuff again.
I can't exactly tell why, but suddenly our zabbix-server cannot be started anymore becaues it immediately stops after an probably unexpected Result from a query:
021770:20070125:130035 Executing query:select min(clock) from trends where itemid=10036
021770:20070125:130035 In delete_history(history,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history where itemid=10037
021770:20070125:130035 In delete_history(history_uint,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_uint where itemid=10037
021770:20070125:130035 In delete_history(history_str,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_str where itemid=10037
021770:20070125:130035 In delete_history(history_str,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_str where itemid=10037
021770:20070125:130035 In delete_history(history_log,10037,7,1169726435)
021770:20070125:130035 Executing query:select min(clock) from history_log where itemid=10037
021770:20070125:130035 In delete_history(trends,10037,365,1169726435)
021770:20070125:130035 Executing query:select min(clock) from trends where itemid=10037
021793:20070125:130035 RESULT_STR [Ð]
021793:20070125:130035 In process_new_value()
021793:20070125:130035 In add_history(pdns.uptime,,2,4)
021793:20070125:130035 In add_history(17778,STRING:18.9 days)
021793:20070125:130035 In add_history_log()
021770:20070125:130035 One server process died. Shutting down...
021784:20070125:130035 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 0. Killing PID=[21784]
021786:20070125:130035 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 1. Killing PID=[21786]
021788:20070125:130035 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 2. Killing PID=[21788]
021792:20070125:130035 Server [4]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 3. Killing PID=[21792]
021770:20070125:130035 4. Killing PID=[21793]
021794:20070125:130035 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 5. Killing PID=[21794]
021796:20070125:130035 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 6. Killing PID=[21796]
021797:20070125:130035 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 7. Killing PID=[21797]
021799:20070125:130035 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 8. Killing PID=[21799]
021801:20070125:130035 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
021770:20070125:130035 9. Killing PID=[21801]
021770:20070125:130035 ZABBIX server is down.
How can I work around this ? I do not mind loosing all data from the past, but I do not want to setup all the triggers, users and stuff again.
Comment