[ZBX-11016] Zabbix Server crashed in poller, odbc related Created: 2016 Jul 21  Updated: 2017 May 30  Resolved: 2016 Jul 25

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

Type: Incident report Priority: Major
Reporter: Alexander Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: crash, odbc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Linux 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
MSQL: 5.7.12


Attachments: File dump.rar     File zabbix_server-debug4.rar    
Issue Links:
Duplicate
duplicates ZBX-7665 Zabbix 2.2.1 ODBC monitor crash - in ... Closed

 Description   

I updated Zabbix Server and Zabbix Server crashes,I don't know why
Backtrace in attachment.



 Comments   
Comment by Andrey Melnikov [ 2016 Jul 22 ]

Backtrace from initially attached log:

  8477:20160721:212231.612 Got signal [signal:11(SIGSEGV),reason:1,refaddr:(nil)]. Crashing ...
...
 8477:20160721:212231.620 === Backtrace: ===
  8477:20160721:212231.621 21: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](print_fatal_info+0xbd) [0x47e21d]
  8477:20160721:212231.621 20: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values]() [0x47e4e2]
  8477:20160721:212231.621 19: /lib/x86_64-linux-gnu/libc.so.6(+0x354a0) [0x7f6cc6eb34a0]
  8477:20160721:212231.621 18: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18(my_stat+0x92) [0x7f6cb7a693c2]
  8477:20160721:212231.621 17: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18(+0x4c7cc) [0x7f6cb7a607cc]
  8477:20160721:212231.622 16: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18(+0x4d5fd) [0x7f6cb7a615fd]
  8477:20160721:212231.622 15: /lib/x86_64-linux-gnu/libpthread.so.0(+0xead9) [0x7f6cc6a55ad9]
  8477:20160721:212231.622 14: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18(get_charset_by_csname+0x44) [0x7f6cb7a61a44]
  8477:20160721:212231.622 13: /usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so(myodbc_init+0xd4) [0x7f6cb7f7a754]
  8477:20160721:212231.622 12: /usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so(my_SQLAllocEnv+0x1c) [0x7f6cb7f7d28c]
  8477:20160721:212231.622 11: /usr/lib/x86_64-linux-gnu/libodbc.so.2(+0xd3dc) [0x7f6cc912c3dc]
  8477:20160721:212231.622 10: /usr/lib/x86_64-linux-gnu/libodbc.so.2(SQLConnect+0x20f) [0x7f6cc912e61f]
  8477:20160721:212231.623 9: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](odbc_DBconnect+0xf7) [0x4ae747]
  8477:20160721:212231.623 8: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](get_value_db+0x130) [0x431e10]
  8477:20160721:212231.623 7: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values]() [0x429a0e]
  8477:20160721:212231.623 6: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](poller_thread+0x108) [0x429bd8]
  8477:20160721:212231.623 5: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](zbx_thread_start+0x45) [0x47ef15]
  8477:20160721:212231.623 4: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](MAIN_ZABBIX_ENTRY+0x5ff) [0x41d4af]
  8477:20160721:212231.624 3: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](daemon_start+0x1c3) [0x47daa3]
  8477:20160721:212231.624 2: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](main+0x303) [0x418143]
  8477:20160721:212231.624 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f6cc6e9e830]
  8477:20160721:212231.624 0: /usr/sbin/zabbix_server: poller #8 [got 12 values in 0.275409 sec, getting values](_start+0x29) [0x4183f9]
...
  8467:20160721:212254.035 Zabbix Server stopped. Zabbix 3.0.3 (revision 60173).

unixODBC related.

Comment by Alexander [ 2016 Jul 22 ]

I don't understand you.

Comment by Aleksandrs Saveljevs [ 2016 Jul 25 ]

Very likely to be a duplicate of ZBX-7665, closing as such.

Generated at Thu Apr 25 14:45:20 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.