Crashing Vmware collector

[gabo]

Hello, I have a problem with the zabbix server, it is giving a minimum once a day, it usually falls between 3 or 4 times, apparently because of the log it is due to the vmware collector, I detail all the information that I consider necessary to receive a help.

This is the crashing in the /var/log/zabbix/zabbix_server.log

13836:20200226:043903.328 Got signal [signal:11(SIGSEGV),reason:128,refaddrnil)]. Crashing ...
13836:20200226:043903.328 ====== Fatal information: ======
13836:20200226:043903.328 Program counter: 0x7f1eecc68bcc
13836:20200226:043903.328 === Registers: ===
13836:20200226:043903.328 r8 = 1 = 1 = 1
13836:20200226:043903.328 r9 = 55ebf8e62800 = 94471981508608 = 94471981508608
13836:20200226:043903.328 r10 = 67 = 103 = 103
13836:20200226:043903.328 r11 = 1118 = 4376 = 4376
13836:20200226:043903.328 r12 = 55ebf86b4497 = 94471973454999 = 94471973454999
13836:20200226:043903.328 r13 = 17 = 23 = 23
13836:20200226:043903.328 r14 = 0 = 0 = 0
13836:20200226:043903.328 r15 = 0 = 0 = 0
13836:20200226:043903.328 rdi = 10ec8348e5894855 = 1219493948222425173 = 1219493948222425173
13836:20200226:043903.328 rsi = 7f1eeec698e0 = 139770831739104 = 139770831739104
13836:20200226:043903.328 rbp = 55ebf8ec60b0 = 94471981916336 = 94471981916336
13836:20200226:043903.328 rbx = f0758948 = 4034234696 = 4034234696
13836:20200226:043903.328 rdx = f87d8948 = 4168976712 = 4168976712
13836:20200226:043903.328 rax = 0 = 0 = 0
13836:20200226:043903.328 rcx = 55ebf8eccd00 = 94471981944064 = 94471981944064
13836:20200226:043903.328 rsp = 7ffff18d07d8 = 140737245939672 = 140737245939672
13836:20200226:043903.328 rip = 7f1eecc68bcc = 139770798181324 = 139770798181324
13836:20200226:043903.328 efl = 10206 = 66054 = 66054
13836:20200226:043903.328 csgsfs = 33 = 51 = 51
13836:20200226:043903.328 err = 0 = 0 = 0
13836:20200226:043903.328 trapno = d = 13 = 13
13836:20200226:043903.328 oldmask = 0 = 0 = 0
13836:20200226:043903.328 cr2 = 0 = 0 = 0
13836:20200226:043903.328 === Backtrace: ===
13836:20200226:043903.417 15: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](zbx_backtrace+0x35) [0x55ebf86b29d5]
13836:20200226:043903.417 14: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](zbx_log_fatal_info+0x119) [0x55ebf86b2bf0]
13836:20200226:043903.417 13: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](+0xf0f05) [0x55ebf86b2f05]
13836:20200226:043903.417 12: /lib64/libpthread.so.0(+0xf680) [0x7f1eeff73680]
13836:20200226:043903.417 11: /lib64/libc.so.6(cfree+0x1c) [0x7f1eecc68bcc]
13836:20200226:043903.417 10: /lib64/libxml2.so.2(xmlHashFree+0xf5) [0x7f1eeec5e9f5]
13836:20200226:043903.417 9: /lib64/libxml2.so.2(xmlFreeDoc+0x3c) [0x7f1eeec55c9c]
13836:20200226:043903.417 8: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](+0x7ff5c) [0x55ebf8641f5c]
13836:20200226:043903.417 7: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](+0x803c6) [0x55ebf86423c6]
13836:20200226:043903.417 6: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](vmware_thread+0x352) [0x55ebf8643170]
13836:20200226:043903.417 5: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](zbx_thread_start+0x32) [0x55ebf86bff8d]
13836:20200226:043903.417 4: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](MAIN_ZABBIX_ENTRY+0xd38) [0x55ebf85faf8d]
13836:20200226:043903.417 3: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](daemon_start+0x31b) [0x55ebf86b2226]
13836:20200226:043903.417 2: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](main+0x312) [0x55ebf85fa253]
13836:20200226:043903.417 1: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f1eecc053d5]
13836:20200226:043903.417 0: /usr/sbin/zabbix_server: vmware collector #23 [updated 0, removed 0 VMware services in 0.000023 sec, querying VMware services](+0x37429) [0x55ebf85f9429]
13836:20200226:043903.417 === Memory map: ===


This is the zabbix_server.conf

# grep -i vmware /etc/zabbix/zabbix_server.conf
### Option: StartVMwareCollectors
# Number of pre-forked vmware collector instances.
StartVMwareCollectors=25
### Option: VMwareFrequency
# How often Zabbix will connect to VMware service to obtain a new data.
VMwareFrequency=12000
### Option: VMwarePerfFrequency
# How often Zabbix will connect to VMware service to obtain performance data.
VMwarePerfFrequency=24000
### Option: VMwareCacheSize
# Size of VMware cache, in bytes.
# Shared memory size for storing VMware data.
# Only used if VMware collectors are started.
VMwareCacheSize=1536M
### Option: VMwareTimeout
# Specifies how many seconds vmware collector waits for response from VMware service.
#VMwareTimeout=10

[tim.mooney]

A crash from a SEGV is always indicative of a software bug.

You don't say what version of Zabbix you're using, but if you're not using the latest version in either 4.0 LTS or 4.4.x, you may want to read the release notes for any later versions, to see if they mention fixes for VMWare crashes.

If you are running the latest version in your release series, you probably want to report the bug on the Zabbix bug tracker. The fact that it happens often for you (you can reproduce it) means it will likely be something that could be diagnosed and fixed.