-
Incident report
-
Resolution: Won't fix
-
Minor
-
None
-
2.2.10
-
None
-
CentOS 7 / epel-testing
Ran into ZBX-8494 setting up a proxy on Cent7. Tried using the version in epel-testing (2.2.10), which did not help.
Found out it may be ZBX-8494 by using gdb to watch zabbix_proxy as it crashed, got this:
(gdb) set follow-fork-mode child (gdb) run Starting program: /usr/sbin/zabbix_proxy [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New process 7920] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New process 7921] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [tcsetpgrp failed in terminal_inferior: No such process] Program received signal SIGFPE, Arithmetic exception. [Switching to Thread 0x7ffff7fdd840 (LWP 7921)] DCsync_functions (result=0x78a850) at dbconfig.c:2057 2057 i = function->triggerid % CONFIG_TIMER_FORKS;
Verified it was ZBX-8494 by wiping the proxy's db and rebuilding it properly. Apparently, I was sloppy the first time and included images.sql and data.sql.
Given that the 2.2 branch is still listed on the site as supported, it seems appropriate to backport the fix for ZBX-8494 to the 2.2 branch.
(JIRA won't let me identify 2.3.4 as the fix version, but that's where ZBX-8494 identifies the fix as being implemented.)