-
Patch request
-
Resolution: Fixed
-
Trivial
-
4.0.5
-
VMware, Cento7, Mariadb, Apache
-
Team C
-
Sprint 63 (Apr 2020), Sprint 64 (May 2020), Sprint 65 (Jun 2020), Sprint 66 (Jul 2020), Sprint 67 (Aug 2020), Sprint 68 (Sep 2020)
-
1
No matter what VMwareCacheSize is set (from 128 MB to 2G) after about 24-48h of Zabbix running, it crashes.
33502:20190329:123748.940 __mem_malloc: skipped 0 asked 24 skip_min 18446744073709551615 skip_max 0 33502:20190329:123748.940 [file:vmware.c,line:92] zbx_mem_malloc(): out of memory (requested 24 bytes) 33502:20190329:123748.940 [file:vmware.c,line:92] zbx_mem_malloc(): please increase VMwareCacheSize configuration parameter 33502:20190329:123748.940 === memory statistics for vmware cache size === 33502:20190329:123748.940 min chunk size: 18446744073709551615 bytes 33502:20190329:123748.940 max chunk size: 0 bytes 33502:20190329:123748.940 memory of total size 2147482848 bytes fragmented into 15899688 chunks 33502:20190329:123748.940 of those, 0 bytes are in 0 free chunks 33502:20190329:123748.940 of those, 1893087856 bytes are in 15899688 used chunks 33502:20190329:123748.940 ================================ 33502:20190329:123748.940 === Backtrace: === 33502:20190329:123748.941 12: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](zbx_backtrace+0x35) [0x55a9f744cb59] 33502:20190329:123748.941 11: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](__zbx_mem_malloc+0x163) [0x55a9f7448590] 33502:20190329:123748.941 10: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](+0x79f3d) [0x55a9f73d0f3d] 33502:20190329:123748.941 9: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](+0x7bb81) [0x55a9f73d2b81] 33502:20190329:123748.941 8: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](+0x7c2e0) [0x55a9f73d32e0] 33502:20190329:123748.941 7: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](+0x81b19) [0x55a9f73d8b19] 33502:20190329:123748.941 6: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](vmware_thread+0x340) [0x55a9f73dab0c] 33502:20190329:123748.941 5: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](zbx_thread_start+0x37) [0x55a9f745a18c] 33502:20190329:123748.941 4: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](MAIN_ZABBIX_ENTRY+0xd06) [0x55a9f7390bf3] 33502:20190329:123748.941 3: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](daemon_start+0x31b) [0x55a9f744c3aa] 33502:20190329:123748.941 2: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](main+0x312) [0x55a9f738feeb] 33502:20190329:123748.941 1: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f15b38f8445] 33502:20190329:123748.941 0: /usr/sbin/zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000016 sec, querying VMware services](+0x38059) [0x55a9f738f059] 31718:20190329:123749.600 One child process died (PID:33502,exitcode/signal:1). Exiting ... zabbix_server [31718]: Error waiting for process with PID 33502: [10] No child processes 31718:20190329:123903.459 Zabbix Server stopped. Zabbix 4.0.5 (revision 90164).
According to logs, the cache is too small BUT, on the Self Monitoring Zabbix Cache Graph (atached) there is a lot of free space in VMware Cache.
Or there is some memory leak in cache or internal items can't correctly read the cache capacity.
