Ad Widget

Collapse

Zabbix Won't Stay Running

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • emonhello
    Junior Member
    • Jan 2018
    • 18

    #1

    Zabbix Won't Stay Running

    My Zabbix serve won't stay running. Here is an excerpt of the log file.
    1494:20180220:130422.128 __zbx_zbx_setproctitle() title:'vmware collector #3 [updated 0, removed 0 VMware services in 0.000006 sec, querying VMware services]'
    1493:20180220:130422.175 __mem_malloc: skipped 0 asked 176 skip_min 4294967295 skip_max 0
    1493:20180220:130422.176 [file:vmware.c,line:86] zbx_mem_malloc(): out of memory (requested 173 bytes)
    1493:20180220:130422.176 [file:vmware.c,line:86] zbx_mem_malloc(): please increase VMwareCacheSize configuration parameter

    I am monitoring the Zabbix server and the VMwareCache is showing at 99% and all other cache's are over 80% free. I am monitoring 3 ESXi hosts with 35 VMs.
    My VMware settings are as follows.

    StartVMwareCollectors=5
    VMwareFrequency=30
    VMwarePerfFrequency=30
    VMwareCacheSize=512M
    VMwareTimeout=20

    I am new to Zabbix. I really need some help.
  • tcilmo
    Senior Member
    • Nov 2016
    • 122

    #2
    Originally posted by emonhello
    My Zabbix serve won't stay running. Here is an excerpt of the log file.
    1494:20180220:130422.128 __zbx_zbx_setproctitle() title:'vmware collector #3 [updated 0, removed 0 VMware services in 0.000006 sec, querying VMware services]'
    1493:20180220:130422.175 __mem_malloc: skipped 0 asked 176 skip_min 4294967295 skip_max 0
    1493:20180220:130422.176 [file:vmware.c,line:86] zbx_mem_malloc(): out of memory (requested 173 bytes)
    1493:20180220:130422.176 [file:vmware.c,line:86] zbx_mem_malloc(): please increase VMwareCacheSize configuration parameter

    I am monitoring the Zabbix server and the VMwareCache is showing at 99% and all other cache's are over 80% free. I am monitoring 3 ESXi hosts with 35 VMs.
    My VMware settings are as follows.

    StartVMwareCollectors=5
    VMwareFrequency=30
    VMwarePerfFrequency=30
    VMwareCacheSize=512M
    VMwareTimeout=20

    I am new to Zabbix. I really need some help.
    Does increasing the VMwareCacheSize value help at all?

    Comment

    • emonhello
      Junior Member
      • Jan 2018
      • 18

      #3
      Originally posted by tcilmo
      Does increasing the VMwareCacheSize value help at all?
      It doesn't seem to. The sever runs fine for a while. Today it ran for a couple hours. From the other posts I have read, 512M for my small environment seems over kill.

      Comment

      • tcilmo
        Senior Member
        • Nov 2016
        • 122

        #4
        Has it always done this, or did it just start? Any changes introduced into the environment recently?

        Comment

        • emonhello
          Junior Member
          • Jan 2018
          • 18

          #5
          Originally posted by tcilmo
          Has it always done this, or did it just start? Any changes introduced into the environment recently?
          I did attempt to add a router, but it isn't working. I does seem since I added the router it bombs our faster than it did before I added the router. I can disable discovery for the router, but it will continue to stop on and give me that error. It may just take longer. I just can't seem find anything meaningful in the log that points me to the problem. It seems my VMware cache is just fine even though it is listing it as full..it isn't according to the graph Zabbix cache usage, % free

          Comment

          • tcilmo
            Senior Member
            • Nov 2016
            • 122

            #6
            That is odd. Shot in the dark, have you checked Monitoring -> Graphs -> Zabbix server -> Zabbix Cache usage graph to see if anything else might need adjusted.

            Someone else had your problem awhile back.



            What version of Z are you running?

            Comment

            • emonhello
              Junior Member
              • Jan 2018
              • 18

              #7
              Originally posted by tcilmo
              That is odd. Shot in the dark, have you checked Monitoring -> Graphs -> Zabbix server -> Zabbix Cache usage graph to see if anything else might need adjusted.

              Someone else had your problem awhile back.



              What version of Z are you running?
              Version 3.4 on Centos 7.
              All the metrics in the Zabbix graphs look great to me. Nothing even close to borderline bad.

              Comment

              • tcilmo
                Senior Member
                • Nov 2016
                • 122

                #8
                Does the vmware cache size graph indicate that your allocated value is getting pegged?
                Found this for an older Z version: https://support.zabbix.com/browse/ZBXNEXT-2915

                However, the issue is still open.

                Comment

                • emonhello
                  Junior Member
                  • Jan 2018
                  • 18

                  #9
                  Originally posted by tcilmo
                  Does the vmware cache size graph indicate that your allocated value is getting pegged?
                  The "Zabbix cache usage, % free" graph shows min free % of 99.11, and the graph shows a warning threshold at 25% free. All the other Cache % free values are 90% or more.

                  Comment

                  • emonhello
                    Junior Member
                    • Jan 2018
                    • 18

                    #10
                    Setup

                    I used this post as a reference for my setup. The only thing I can think is that the SNMP configuration is messed up.

                    Comment

                    • emonhello
                      Junior Member
                      • Jan 2018
                      • 18

                      #11
                      Originally posted by emonhello
                      I used this post as a reference for my setup. The only thing I can think is that the SNMP configuration is messed up.

                      https://www.zabbix.com/forum/showthread.php?t=53002
                      The VCenter and ESXi servers show up, but the SNMP Availability is grey. Seems to me it should be green.

                      Comment

                      • tcilmo
                        Senior Member
                        • Nov 2016
                        • 122

                        #12
                        I am sure this is not the case, but your VMware cache line is not remarked out?

                        Here is our config for the VMware stuff.




                        ### Option: StartVMwareCollectors
                        # Number of pre-forked vmware collector instances.
                        #
                        # Mandatory: no
                        # Range: 0-250
                        # Default:
                        # StartVMwareCollectors=0
                        StartVMwareCollectors=2

                        ### Option: VMwareFrequency
                        # How often Zabbix will connect to VMware service to obtain a new data.
                        #
                        # Mandatory: no
                        # Range: 10-86400
                        # Default:
                        # VMwareFrequency=60

                        ### Option: VMwarePerfFrequency
                        # How often Zabbix will connect to VMware service to obtain performance data.
                        #
                        # Mandatory: no
                        # Range: 10-86400
                        # Default:
                        # VMwarePerfFrequency=60

                        ### Option: VMwareCacheSize
                        # Size of VMware cache, in bytes.
                        # Shared memory size for storing VMware data.
                        # Only used if VMware collectors are started.
                        #
                        # Mandatory: no
                        # Range: 256K-2G
                        # Default:
                        # VMwareCacheSize=8M
                        VMwareCacheSize=48M

                        ### Option: VMwareTimeout
                        # Specifies how many seconds vmware collector waits for response from VMware service.
                        #
                        # Mandatory: no
                        # Range: 1-300
                        # Default:
                        # VMwareTimeout=10

                        Comment

                        • emonhello
                          Junior Member
                          • Jan 2018
                          • 18

                          #13
                          VMs

                          All the VMs are discovered and are producing data.

                          Comment

                          • emonhello
                            Junior Member
                            • Jan 2018
                            • 18

                            #14
                            My Config snippet

                            ### Option: StartVMwareCollectors
                            # Number of pre-forked vmware collector instances.
                            #
                            # Mandatory: no
                            # Range: 0-250
                            # Default:
                            StartVMwareCollectors=5

                            ### Option: VMwareFrequency
                            # How often Zabbix will connect to VMware service to obtain a new data.
                            #
                            # Mandatory: no
                            # Range: 10-86400
                            # Default:
                            VMwareFrequency=30

                            ### Option: VMwarePerfFrequency
                            # How often Zabbix will connect to VMware service to obtain performance data.
                            #
                            # Mandatory: no
                            # Range: 10-86400
                            # Default:
                            VMwarePerfFrequency=30

                            ### Option:
                            # Size of VMware cache, in bytes.
                            # Shared memory size for storing VMware data.
                            # Only used if VMware collectors are started.
                            #
                            # Mandatory: no
                            # Range: 256K-2G
                            # Default:
                            VMwareCacheSize=512M

                            ### Option: VMwareTimeout
                            # Specifies how many seconds vmware collector waits for response from VMware service.
                            #
                            # Mandatory: no
                            # Range: 1-300
                            # Default:
                            VMwareTimeout=20

                            Comment

                            • emonhello
                              Junior Member
                              • Jan 2018
                              • 18

                              #15
                              What I tried

                              I disabled the Router discovery that wasn't working.
                              Also the SNMP piece of the VMware dicovery rule was throwing an error. I removed the SNMP piece of discovery.
                              I have restarted the server. I will post back if it crashes, or tomorrow if it doesn't.

                              Comment

                              Working...