[ZBX-20803] Zabbix server crash in poller with Oracle ODBC Created: 2022 Mar 28 Updated: 2024 Apr 10 Resolved: 2022 Jul 19 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | None |
Fix Version/s: | 6.4 (plan) |
Type: | Problem report | Priority: | Trivial |
Reporter: | Kim Jongkwon | Assignee: | Vladislavs Sokurenko |
Resolution: | Fixed | Votes: | 0 |
Labels: | odbc, oracle | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Zabbix 5.0.14 |
Attachments: |
![]() |
||||
Issue Links: |
|
||||
Team: | |||||
Sprint: | Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022) | ||||
Story Points: | 0.25 |
Description |
Poller crashes due to Oracle ODBC monitoring. Error: 15433:20220220:100029.492 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ... 15433:20220220:100029.511 ====== Fatal information: ====== 15433:20220220:100029.523 Program counter: 0x7f0b83d58004 15433:20220220:100029.531 === Registers: === 15433:20220220:100029.538 r8 = 7f0b445bead0 = 139686368242384 = 139686368242384 15433:20220220:100029.546 r9 = 0 = 0 = 0 15433:20220220:100029.557 r10 = 1 = 1 = 1 15433:20220220:100029.565 r11 = 7f0b445be920 = 139686368241952 = 139686368241952 15433:20220220:100029.595 r12 = 0 = 0 = 0 15433:20220220:100029.627 r13 = 0 = 0 = 0 15433:20220220:100029.638 r14 = 0 = 0 = 0 15433:20220220:100029.645 r15 = 0 = 0 = 0 15433:20220220:100029.653 rdi = 7f0b445bead0 = 139686368242384 = 139686368242384 15433:20220220:100029.660 rsi = a = 10 = 10 15433:20220220:100029.668 rbp = 7f0b445c0fc0 = 139686368251840 = 139686368251840 15433:20220220:100029.675 rbx = 0 = 0 = 0 15433:20220220:100029.682 rdx = 0 = 0 = 0 15433:20220220:100029.691 rax = 7f0b445bec10 = 139686368242704 = 139686368242704 15433:20220220:100029.698 rcx = 7f0b445c0d30 = 139686368251184 = 139686368251184 15433:20220220:100029.706 rsp = 7f0b445be7d0 = 139686368241616 = 139686368241616 15433:20220220:100029.712 rip = 7f0b83d58004 = 139687433175044 = 139687433175044 15433:20220220:100029.720 efl = 10206 = 66054 = 66054 15433:20220220:100029.726 csgsfs = 2b000000000033 = 12103423998558259 = 12103423998558259 15433:20220220:100029.737 err = 4 = 4 = 4 15433:20220220:100029.757 trapno = e = 14 = 14 15433:20220220:100029.770 oldmask = fffffffe3e7bb207 = 18446744066167910919 = -7541640697 15433:20220220:100029.780 cr2 = 30 = 48 = 48 15433:20220220:100029.787 === Backtrace: === 15433:20220220:100029.795 13: /usr/sbin/zabbix_server: poller #3 [got 3 values in 0.064312 sec, idle 1 sec](zbx_backtrace+0x46) [0x53a7a6] 15433:20220220:100029.801 12: /usr/sbin/zabbix_server: poller #3 [got 3 values in 0.064312 sec, idle 1 sec](zbx_log_fatal_info+0x263) [0x53ab03] 15433:20220220:100029.809 11: /usr/sbin/zabbix_server: poller #3 [got 3 values in 0.064312 sec, idle 1 sec]() [0x53af86] 15433:20220220:100029.817 10: /lib64/libpthread.so.0(+0x117e0) [0x7f0b83d597e0] 15433:20220220:100029.823 9: /lib64/libpthread.so.0(+0x10004) [0x7f0b83d58004] 15433:20220220:100029.830 8: /lib64/libgcc_s.so.1(+0xf44a) [0x7f0b46b7144a] 15433:20220220:100029.837 7: /lib64/libgcc_s.so.1(_Unwind_ForcedUnwind+0x125) [0x7f0b46b71a25] 15433:20220220:100029.845 6: /lib64/libpthread.so.0(__pthread_unwind+0x40) [0x7f0b83d580c0] 15433:20220220:100029.856 5: /lib64/libpthread.so.0(+0x85d5) [0x7f0b83d505d5] 15433:20220220:100029.863 4: /usr/lib/oracle/19.11/client64/lib/libclntshcore.so.19.1(SltsqSigFunc+0x5a) [0x7f0b56a9920a] 15433:20220220:100029.869 3: /usr/lib/oracle/19.11/client64/lib/libclntshcore.so.19.1(+0xa8e8b) [0x7f0b56a9be8b] 15433:20220220:100029.876 2: /usr/lib/oracle/19.11/client64/lib/libclntshcore.so.19.1(sslsshandler+0x81) [0x7f0b56a9b8b1] 15433:20220220:100029.883 1: /lib64/libpthread.so.0(+0x117e0) [0x7f0b83d597e0] 15433:20220220:100029.891 0: /lib64/libc.so.6(clone+0x31) [0x7f0b80eba401] Zabbix known issues have announced a crash of Oracle 11.2.0.4.0 client. As a workaround, I have stopped ODBC and using a Zabbix Agent2. |
Comments |
Comment by Vladislavs Sokurenko [ 2022 Jun 30 ] |
Thank you for your report, this is a duplicate of |
Comment by Alexander Vladishev [ 2022 Jul 19 ] |
Known issues updated for the supported versions: 4.0, 5.0, 6.0, 6.2, 6.4 |