zabbix_server.dump.bz2
zabbix_server.log.20120224jd
[ZBX-4696] zabbix_server crashes Created: 2012 Feb 24 Updated: 2017 May 30 Resolved: 2012 Sep 06 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 1.8.10 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Major |
| Reporter: | Jerome Doucerain | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
SuSE Linux Enterprise Server 10 SP4 |
||
| Attachments: |
zabbix_server.dump.bz2
zabbix_server.log.20120224jd
|
| Description |
|
After an upgrade to the most recent stable version (1.8.10), zabbix_server process begun to crash several times during the last 24 hours. I attached the zabbix_server log and the dump of the zabbix_server binary. |
| Comments |
| Comment by Alexei Vladishev [ 2012 Jul 28 ] |
|
Apologies for the long delay. Please tell me where where you are with this issue. Have you tried the latest 1.8.14, which I believe contains fixes for a couple of rare crash related issues. |
| Comment by Jerome Doucerain [ 2012 Jul 30 ] |
|
No problem for the delay. We did 2 things to stabilize the environnement. First we moved the zabbix server VM to a less busy physical server. Second for particular reasons we had to have the zabbix server answering on 2 differents TCP ports. The first TCP port was the regular 10051 which was handled directly by the zabbix_server process, and we also had the 10053 port handled by xinetd and which was forwarded to 10051 port. We worked at our setup to simplify things and managed to remove the tcp forwarding done by xinetd. So far the crash occurences seemed to disappear. We let 1.8.10 in place. |
| Comment by Alexei Vladishev [ 2012 Sep 06 ] |
|
Jerome, thanks for the follow up. I am closing it. |