-
Incident report
-
Resolution: Unresolved
-
Trivial
-
None
-
2.4.6
-
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>
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>
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.