[ZBX-13477] Proxy Crash VMware Collector Created: 2018 Feb 15  Updated: 2018 Feb 16  Resolved: 2018 Feb 15

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 3.4.6
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: AndrwSmmr Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: crash, proxy, server, vmware
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File proxy_crash_vmware     File zabbix-crash.tar    
Issue Links:
Duplicate
duplicates ZBX-13441 Zabbix Server stopped Closed

 Description   

My VMware Proxy crashes regularly because of the VMware Collector.
I originally deployed a Proxy for monitoring VMware because my Main Server kept crashing. (Because of VMware Collector)

I would really appreciate any help:

 19359:20180215:115611.533 === Backtrace: ===
 19359:20180215:115611.534 14: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](zbx_log_fatal_info+0x176) [0x5644a912ff72]
 19359:20180215:115611.534 13: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](+0xd5401) [0x5644a9130401]
 19359:20180215:115611.534 12: /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f492488f390]
 19359:20180215:115611.534 11: /lib/x86_64-linux-gnu/libc.so.6(cfree+0x22) [0x7f4921a05512]
 19359:20180215:115611.534 10: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](zbx_strdup2+0x32) [0x5644a9142853]
 19359:20180215:115611.534 9: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](+0x6e48d) [0x5644a90c948d]
 19359:20180215:115611.534 8: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](+0x713ca) [0x5644a90cc3ca]
 19359:20180215:115611.534 7: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](+0x73677) [0x5644a90ce677]
 19359:20180215:115611.534 6: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](vmware_thread+0x303) [0x5644a90d0548]
 19359:20180215:115611.534 5: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](zbx_thread_start+0x37) [0x5644a914063c]
 19359:20180215:115611.534 4: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](MAIN_ZABBIX_ENTRY+0xb34) [0x5644a908ecc7]
 19359:20180215:115611.534 3: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](daemon_start+0x31f) [0x5644a912f5ca]
 19359:20180215:115611.534 2: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](main+0x305) [0x5644a908e17d]
 19359:20180215:115611.534 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f49219a1830]
 19359:20180215:115611.534 0: /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000005 sec, querying VMware services](_start+0x29) [0x5644a908c8e9]

I attached the full crash log.
How do I attach the Objectdump ? its 40MBs big...

Thanks!



 Comments   
Comment by AndrwSmmr [ 2018 Feb 15 ]

Proxy is running on Ubuntu 16.04.3 LTS 4.4.0-112-generic #135

Comment by Vladislavs Sokurenko [ 2018 Feb 15 ]

Looks like a duplicate of ZBX-13441

Could you please increase log level of vmware collectors and attach log ?

zabbix_proxy -R log_level_increase='vmware collector'
Comment by AndrwSmmr [ 2018 Feb 15 ]

Log with increased log level. Thank you!

Comment by Vladislavs Sokurenko [ 2018 Feb 15 ]

For some reason log level is only increase of one process of vmware collectors, can you please try again and make sure that all processes have started when you increase log level ?

Comment by Glebs Ivanovskis (Inactive) [ 2018 Feb 15 ]

Thank you for the log file!

 29598:20180215:145103.065 In vmware_service_get_hv_list()
 29598:20180215:145133.068 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x10000001c]. Crashing ...

This is definitely a Duplicate of ZBX-13441. Closing.

Update to 3.4.7rc2, recompile Zabbix with the patch attached to ZBX-13441 or try to increase VMwareTimeout as a temporary countermeasure.

Comment by AndrwSmmr [ 2018 Feb 16 ]

I doubled the timeout from 30 -> 60 seems stable now.

Thank you very much for your quick help!

Generated at Sat Apr 27 02:53:26 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.