ZABBIX BUGS AND ISSUES

Zabbix server 1.6.5 hangs after PostgreSQL database restart

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.6.5
  • Fix Version/s: 1.8.2, 1.9.0 (alpha)
  • Component/s: Server (S)
  • Labels:
    None
  • Environment:
    CentOS 5, Zabbix 1.6.5
  • Zabbix ID:
    NA

Description

Hello,

we just noticed that Zabbix 1.6.5 hangs after PostgreSQL database restart. In previous versions server would simply die after noticing that the database is gone. In the latest version it simply starts returning loads of messages that database query result has failed or that result is NULL. Here's an example from zabbix_server log:
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_str where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_text where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_text where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_log where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_log where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from trends where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from trends where itemid=32272]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_uint where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_uint where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_str where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_str where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_text where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_text where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_log where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_log where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from trends where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from trends where itemid=44687]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_uint where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_uint where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_str where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_str where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_text where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_text where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history_log where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history_log where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from trends where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from trends where itemid=44766]
 13179:20090818:133528 [Z3005] Query failed: [0] Result is NULL [select min(clock) from history where itemid=27572]
 13179:20090818:133528 [Z3005] Query failed: [0] PGRES_FATAL_ERROR: [select min(clock) from history where itemid=27572]

(notice the timetamps :)))

It continued behaving like this even after the database came back online. Only after a restart of Zabbix server things got back to normal. I assume that the problem is that server doesn't do reconnection. This probably affects only the latest version because it has PostgreSQL error handling implemented.

Issue Links

Activity

Alexei Vladishev made changes -
Field Original Value New Value
Workflow jira [ 12278 ] Zabbix workflow [ 12492 ]
richlv made changes -
Assignee Alexei Vladishev [ alexei ]
richlv made changes -
Affects Version/s 1.6.5 [ 10044 ]
Affects Version/s 1.6 [ 10022 ]
Alexei Vladishev made changes -
Workflow Zabbix workflow [ 12492 ] Zabbix workflow2 [ 13498 ]
richlv made changes -
Assignee Alexander Vladishev [ sasha ]
Alexei Vladishev made changes -
Workflow Zabbix workflow2 [ 13498 ] Zabbix workflow [ 15160 ]
Alexei Vladishev made changes -
Assignee Alexander Vladishev [ sasha ]
Aleksandrs Saveljevs made changes -
Link This issue duplicates ZBX-18 [ ZBX-18 ]
Aleksandrs Saveljevs made changes -
Status Open [ 1 ] Closed [ 6 ]
Fix Version/s 1.8.2 [ 10060 ]
Fix Version/s 1.9 (trunk) [ 10046 ]
Resolution Fixed [ 1 ]

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: