[ZBX-10010] crash regularly with "One child process died" Created: 2015 Oct 27  Updated: 2019 Dec 10

Status: Open
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.4.6
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Marc Dequènes (Duck) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: crash, jabber
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

The debian package for this version was backported from testing to stable (simple rebuild).

Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages zabbix-server-pgsql depends on:
ii adduser 3.113+nmu3
ii fping 3.10-2
ii libc6 2.19-18+deb8u1
ii libcurl3-gnutls 7.38.0-4+deb8u2
ii libiksemel3 1.4-2
ii libldap-2.4-2 2.4.40+dfsg-1+deb8u1
ii libodbc1 2.3.1-3
ii libopenipmi0 2.0.16-1.4
ii libpq5 9.4.5-0+deb8u1
ii libsnmp30 5.7.2.1+dfsg-1
ii libssh2-1 1.4.3-4.1
ii libxml2 2.9.1+dfsg1-5
ii lsb-base 4.1+Debian13+nmu1
ii ucf 3.0030

Versions of packages zabbix-server-pgsql recommends:
ii postgresql 9.4+165
pn snmpd <none>

Attachments: File zabbix_crash_trace.log    

 Description   

After a few (random number of) days, the server crashes. According to the trace, it seems related to the sending of alerts.

Since I switched from eJabberd to Prosody, XMMP messages do not work anymore, leading to "tls handshake failed" messages (visible in the attached log). I will fill another report when I find more details, as it only fails with this application. Maybe this failure is not handled properly in all cases. Nevertheless, this and upgrading Zabbix were the only changes that led to this situation. I don't remember exactly when it began, but most probably after upgrading to 2.4.5 or 2.4.6.

Regards.

 Comments   
Comment by richlv [ 2015 Oct 28 ] 
*** buffer overflow detected ***: /usr/sbin/zabbix_server: alerter [sending alerts] terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x731ff)[0x7fb7619771ff]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fb7619fa4c7]
/lib/x86_64-linux-gnu/libc.so.6(+0xf46e0)[0x7fb7619f86e0]
/lib/x86_64-linux-gnu/libc.so.6(+0xf6437)[0x7fb7619fa437]
/usr/sbin/zabbix_server: alerter [sending alerts](+0x7f143)[0x7fb764160143]
/usr/lib/x86_64-linux-gnu/libiksemel.so.3(iks_recv+0x96)[0x7fb763a86186]
/usr/sbin/zabbix_server: alerter [sending alerts](+0x7fc0e)[0x7fb764160c0e]
/usr/sbin/zabbix_server: alerter [sending alerts](send_jabber+0x6e)[0x7fb764160e8e]
/usr/sbin/zabbix_server: alerter [sending alerts](execute_action+0x2e2)[0x7fb76410e982]
/usr/sbin/zabbix_server: alerter [sending alerts](alerter_thread+0x264)[0x7fb76410ec84]
/usr/sbin/zabbix_server: alerter [sending alerts](zbx_thread_start+0x39)[0x7fb76415d829]
/usr/sbin/zabbix_server: alerter [sending alerts](MAIN_ZABBIX_ENTRY+0x571)[0x7fb76410e4f1]
/usr/sbin/zabbix_server: alerter [sending alerts](daemon_start+0x1b1)[0x7fb76415c301]
/usr/sbin/zabbix_server: alerter [sending alerts](main+0x2a2)[0x7fb764108fe2]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fb761925b45]
/usr/sbin/zabbix_server: alerter [sending alerts](+0x28231)[0x7fb764109231]
Generated at Sun Apr 06 00:04:09 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.