Bug #471
closed
Zabbix Server keeps crashing
100%
Description
Zabbix server keeps crashing and nothing is found in the logs except for:
13207:20150801:181504.309 One child process died (PID:13224,exitcode/signal:1). Exiting ...
There is no more information in the other log, no fs full…
Raising the log verbosity to the maximum did not help discover the source of the crash.
Files
Updated by Marc Dequènes over 8 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
It seems the antiflood firewall function was banning the incoming flow from the proxy to the server. I moved zabbix-trapper to the fast services and raised the burst limit a bit. Maybe this was causing the death of the server because a recent look to the logs showed a strange timing coincidence. So I keep this into surveillance.
Updated by Marc Dequènes over 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 10 to 100
Zabbix moved to Korutopi (see #480) and is working nicely now.
Updated by Marc Dequènes over 8 years ago
- File zabbix_crash_trace.log zabbix_crash_trace.log added
- Status changed from Resolved to Delegated
- Assignee deleted (
Marc Dequènes) - % Done changed from 100 to 50
Again. This time I got a nice trace and opened a ticket:
https://support.zabbix.com/browse/ZBX-10010
Updated by Marc Dequènes about 7 years ago
- Status changed from Delegated to Resolved
- Assignee set to Marc Dequènes
- % Done changed from 50 to 100
The problem was error handling when sending XMPP notifications was not done well. I've got no idea if this was improved so I will not close Zabbix's BR.
Anyway I proposed a patch to libiksemel to solve the XMPP problem and submitted it on Debian#803204. Version 1.4-3 shipped the fix and since then it works nicely and we don't experience this problem, so I'm closing this BR.