Ad Widget

Collapse

Zabbix Server Crashed Because of VMwareCacheSize Run out of Memory

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • trungson122
    Junior Member
    • Dec 2015
    • 2
    #1

    Zabbix Server Crashed Because of VMwareCacheSize Run out of Memory

    Hi all,

    My zabbix server has a problem recently. Zabbix Server sometimes stop and start immediately. I have checked Zabbix Server log file and it shows as below:

    2257:20180220:140324.749 __mem_malloc: skipped 0 asked 24 skip_min 4294967295 skip_max 0
    2257:20180220:140324.770 [file:vmware.c,line:86] zbx_mem_malloc(): out of memory (requested 24 bytes)
    2257:20180220:140324.771 [file:vmware.c,line:86] zbx_mem_malloc(): please increase VMwareCacheSize configuration parameter
    1772:20180220:140325.122 One child process died (PID:2257,exitcode/signal:1). Exiting ...
    2296:20180220:140325.122 Got signal [signal:11(SIGSEGV),reason:128,refaddrnil)]. Crashing ...
    2296:20180220:140325.126 ====== Fatal information: ======
    1772:20180220:140405.908 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).
    22616:20180220:140416.463 Starting Zabbix Server. Zabbix 3.4.6 (revision 76823).

    I have googled this problem, most of solutions are increasing VMwareCacheSize. I have increased this parameter and configured shared memory on my linux Server as following:

    [root@static zabbix]# ipcs -lm

    ------ Shared Memory Limits --------
    max number of segments = 4096
    max seg size (kbytes) = 10485760
    max total shared memory (kbytes) = 42949672960
    min seg size (bytes) = 1

    [root@static zabbix]# cat /etc/sysctl.conf
    # sysctl settings are defined through files in
    # /usr/lib/sysctl.d/, /run/sysctl.d/, and /etc/sysctl.d/.
    #
    # Vendors settings live in /usr/lib/sysctl.d/.
    # To override a whole file, create a new file with the same in
    # /etc/sysctl.d/ and put new settings there. To override
    # only specific settings, add a file with a lexically later
    # name in /etc/sysctl.d/ and put new settings there.
    #
    # For more information, see sysctl.conf(5) and sysctl.d(5).
    #
    kernel.shmmax=10737418240
    kernel.shmall=10737418240

    My Zabbix Server Config File as below:

    ############ ADVANCED PARAMETERS ################

    ### Option: StartPollers
    # Number of pre-forked instances of pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    StartPollers=30

    ### Option: StartIPMIPollers
    # Number of pre-forked instances of IPMI pollers.
    # The IPMI manager process is automatically started when at least one IPMI poller is started.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartIPMIPollers=0

    ### Option: StartPreprocessors
    # Number of pre-forked instances of preprocessing workers.
    # The preprocessing manager process is automatically started when preprocessor worker is started.
    #
    # Mandatory: no
    # Range: 1-1000
    # Default:
    StartPreprocessors=1

    ### Option: StartPollersUnreachable
    # Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).
    # At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers
    # are started.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    StartPollersUnreachable=2

    ### Option: StartTrappers
    # Number of pre-forked instances of trappers.
    # Trappers accept incoming connections from Zabbix sender, active agents and active proxies.
    # At least one trapper process must be running to display server availability and view queue
    # in the frontend.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartTrappers=5

    ### Option: StartPingers
    # Number of pre-forked instances of ICMP pingers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartPingers=1

    ### Option: StartDiscoverers
    # Number of pre-forked instances of discoverers.
    #
    # Mandatory: no
    # Range: 0-250
    # Default:
    StartDiscoverers=10

    ### Option: StartHTTPPollers
    # Number of pre-forked instances of HTTP pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartHTTPPollers=1

    ### Option: StartTimers
    # Number of pre-forked instances of timers.
    # Timers process time-based trigger functions and maintenance periods.
    # Only the first timer process handles the maintenance periods.
    #
    # Mandatory: no
    # Range: 1-1000
    # Default:
    # StartTimers=1

    ### Option: StartEscalators
    # Number of pre-forked instances of escalators.
    #
    # Mandatory: no
    # Range: 0-100
    # Default:
    # StartEscalators=1

    ### Option: StartAlerters
    # Number of pre-forked instances of alerters.
    # Alerters send the notifications created by action operations.
    #
    # Mandatory: no
    # Range: 0-100
    # Default:
    # StartAlerters=3

    ### Option: JavaGateway
    # IP address (or hostname) of Zabbix Java gateway.
    # Only required if Java pollers are started.
    #
    # Mandatory: no
    # Default:
    # JavaGateway=

    ### Option: JavaGatewayPort
    # Port that Zabbix Java gateway listens on.
    #
    # Mandatory: no
    # Range: 1024-32767
    # Default:
    # JavaGatewayPort=10052

    ### Option: StartJavaPollers
    # Number of pre-forked instances of Java pollers.
    #
    # Mandatory: no
    # Range: 0-1000
    # Default:
    # StartJavaPollers=0

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

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

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

    ### 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=2G

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

    ### Option: SNMPTrapperFile
    # Temporary file used for passing data from SNMP trap daemon to the server.
    # Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.
    #
    # Mandatory: no
    # Default:
    # SNMPTrapperFile=/tmp/zabbix_traps.tmp

    SNMPTrapperFile=/var/log/snmptrap/snmptrap.log

    ### Option: StartSNMPTrapper
    # If 1, SNMP trapper process is started.
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # StartSNMPTrapper=0

    ### Option: ListenIP
    # List of comma delimited IP addresses that the trapper should listen on.
    # Trapper will listen on all network interfaces if this parameter is missing.
    #
    # Mandatory: no
    # Default:
    # ListenIP=0.0.0.0

    # ListenIP=127.0.0.1

    ### Option: HousekeepingFrequency
    # How often Zabbix will perform housekeeping procedure (in hours).
    # Housekeeping is removing outdated information from the database.
    # To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
    # hours of outdated information are deleted in one housekeeping cycle, for each item.
    # To lower load on server startup housekeeping is postponed for 30 minutes after server start.
    # With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
    # In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
    # period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
    #
    # Mandatory: no
    # Range: 0-24
    # Default:
    # HousekeepingFrequency=1

    ### Option: MaxHousekeeperDelete
    # The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
    # [housekeeperid], [tablename], [field], [value].
    # No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
    # will be deleted per one task in one housekeeping cycle.
    # SQLite3 does not use this parameter, deletes all corresponding rows without a limit.
    # If set to 0 then no limit is used at all. In this case you must know what you are doing!
    #
    # Mandatory: no
    # Range: 0-1000000
    # Default:
    # MaxHousekeeperDelete=5000

    ### Option: CacheSize
    # Size of configuration cache, in bytes.
    # Shared memory size for storing host, item and trigger data.
    #
    # Mandatory: no
    # Range: 128K-8G
    # Default:
    CacheSize=4G

    ### Option: CacheUpdateFrequency
    # How often Zabbix will perform update of configuration cache, in seconds.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # CacheUpdateFrequency=60

    ### Option: StartDBSyncers
    # Number of pre-forked instances of DB Syncers.
    #
    # Mandatory: no
    # Range: 1-100
    # Default:
    # StartDBSyncers=3

    ### Option: HistoryCacheSize
    # Size of history cache, in bytes.
    # Shared memory size for storing history data.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    HistoryCacheSize=500M

    ### Option: HistoryIndexCacheSize
    # Size of history index cache, in bytes.
    # Shared memory size for indexing history cache.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    HistoryIndexCacheSize=100M

    ### Option: TrendCacheSize
    # Size of trend cache, in bytes.
    # Shared memory size for storing trends data.
    #
    # Mandatory: no
    # Range: 128K-2G
    # Default:
    TrendCacheSize=500M

    ### Option: ValueCacheSize
    # Size of history value cache, in bytes.
    # Shared memory size for caching item history data requests.
    # Setting to 0 disables value cache.
    #
    # Mandatory: no
    # Range: 0,128K-64G
    # Default:
    ValueCacheSize=500M

    ### Option: Timeout
    # Specifies how long we wait for agent, SNMP device or external check (in seconds).
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
    # Timeout=3
    Timeout=30

    ### Option: TrapperTimeout
    # Specifies how many seconds trapper may spend processing new data.
    #
    # Mandatory: no
    # Range: 1-300
    # Default:
    # TrapperTimeout=300

    ### Option: UnreachablePeriod
    # After how many seconds of unreachability treat a host as unavailable.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    UnreachablePeriod=3600

    ### Option: UnavailableDelay
    # How often host is checked for availability during the unavailability period, in seconds.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    UnavailableDelay=3600

    ### Option: UnreachableDelay
    # How often host is checked for availability during the unreachability period, in seconds.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    UnreachableDelay=3600

    ### Option: AlertScriptsPath
    # Full path to location of custom alert scripts.
    # Default depends on compilation options.
    #
    # Mandatory: no
    # Default:
    # AlertScriptsPath=${datadir}/zabbix/alertscripts

    AlertScriptsPath=/usr/lib/zabbix/alertscripts

    ### Option: ExternalScripts
    # Full path to location of external scripts.
    # Default depends on compilation options.
    #
    # Mandatory: no
    # Default:
    # ExternalScripts=${datadir}/zabbix/externalscripts

    ExternalScripts=/usr/lib/zabbix/externalscripts

    ### Option: FpingLocation
    # Location of fping.
    # Make sure that fping binary has root ownership and SUID flag set.
    #
    # Mandatory: no
    # Default:
    # FpingLocation=/usr/sbin/fping

    ### Option: Fping6Location
    # Location of fping6.
    # Make sure that fping6 binary has root ownership and SUID flag set.
    # Make empty if your fping utility is capable to process IPv6 addresses.
    #
    # Mandatory: no
    # Default:
    # Fping6Location=/usr/sbin/fping6

    ### Option: SSHKeyLocation
    # Location of public and private keys for SSH checks and actions.
    #
    # Mandatory: no
    # Default:
    # SSHKeyLocation=

    ### Option: LogSlowQueries
    # How long a database query may take before being logged (in milliseconds).
    # Only works if DebugLevel set to 3, 4 or 5.
    # 0 - don't log slow queries.
    #
    # Mandatory: no
    # Range: 1-3600000
    # Default:
    # LogSlowQueries=0

    LogSlowQueries=3000

    ### Option: TmpDir
    # Temporary directory.
    #
    # Mandatory: no
    # Default:
    # TmpDir=/tmp

    ### Option: StartProxyPollers
    # Number of pre-forked instances of pollers for passive proxies.
    #
    # Mandatory: no
    # Range: 0-250
    # Default:
    # StartProxyPollers=1

    ### Option: ProxyConfigFrequency
    # How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.
    # This parameter is used only for proxies in the passive mode.
    #
    # Mandatory: no
    # Range: 1-3600*24*7
    # Default:
    # ProxyConfigFrequency=3600

    ### Option: ProxyDataFrequency
    # How often Zabbix Server requests history data from a Zabbix Proxy in seconds.
    # This parameter is used only for proxies in the passive mode.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # ProxyDataFrequency=1

    ### Option: AllowRoot
    # Allow the server to run as 'root'. If disabled and the server is started by 'root', the server
    # will try to switch to the user specified by the User configuration option instead.
    # Has no effect if started under a regular user.
    # 0 - do not allow
    # 1 - allow
    #
    # Mandatory: no
    # Default:
    # AllowRoot=0

    ### Option: User
    # Drop privileges to a specific, existing user on the system.
    # Only has effect if run as 'root' and AllowRoot is disabled.
    #
    # Mandatory: no
    # Default:
    # User=zabbix

    ### Option: Include
    # You may include individual files or all files in a directory in the configuration file.
    # Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
    #
    # Mandatory: no
    # Default:
    # Include=

    # Include=/usr/local/etc/zabbix_server.general.conf
    # Include=/usr/local/etc/zabbix_server.conf.d/
    # Include=/usr/local/etc/zabbix_server.conf.d/*.conf

    ### Option: SSLCertLocation
    # Location of SSL client certificates.
    # This parameter is used only in web monitoring.
    #
    # Mandatory: no
    # Default:
    # SSLCertLocation=${datadir}/zabbix/ssl/certs

    ### Option: SSLKeyLocation
    # Location of private keys for SSL client certificates.
    # This parameter is used only in web monitoring.
    #
    # Mandatory: no
    # Default:
    # SSLKeyLocation=${datadir}/zabbix/ssl/keys

    ### Option: SSLCALocation
    # Override the location of certificate authority (CA) files for SSL server certificate verification.
    # If not set, system-wide directory will be used.
    # This parameter is used only in web monitoring and SMTP authentication.
    #
    # Mandatory: no
    # Default:
    # SSLCALocation=

    ####### LOADABLE MODULES #######

    ### Option: LoadModulePath
    # Full path to location of server modules.
    # Default depends on compilation options.
    #
    # Mandatory: no
    # Default:
    # LoadModulePath=${libdir}/modules

    ### Option: LoadModule
    # Module to load at server startup. Modules are used to extend functionality of the server.
    # Format: LoadModule=<module.so>
    # The modules must be located in directory specified by LoadModulePath.
    # It is allowed to include multiple LoadModule parameters.
    #
    # Mandatory: no
    # Default:
    # LoadModule=

    ####### TLS-RELATED PARAMETERS #######

    ### Option: TLSCAFile
    # Full pathname of a file containing the top-level CA(s) certificates for
    # peer certificate verification.
    #
    # Mandatory: no
    # Default:
    # TLSCAFile=

    ### Option: TLSCRLFile
    # Full pathname of a file containing revoked certificates.
    #
    # Mandatory: no
    # Default:
    # TLSCRLFile=

    ### Option: TLSCertFile
    # Full pathname of a file containing the server certificate or certificate chain.
    #
    # Mandatory: no
    # Default:
    # TLSCertFile=

    ### Option: TLSKeyFile
    # Full pathname of a file containing the server private key.
    #
    # Mandatory: no
    # Default:
    # TLSKeyFile=


    After I increase these parameters, the issue is still occured. Anyone has solution for this problem? Please help me fix this issue.
    Tags: None
    • tcilmo
      Senior Member
      • Nov 2016
      • 122
      #2
      Originally posted by trungson122
      Hi all,

      My zabbix server has a problem recently. Zabbix Server sometimes stop and start immediately. I have checked Zabbix Server log file and it shows as below:

      2257:20180220:140324.749 __mem_malloc: skipped 0 asked 24 skip_min 4294967295 skip_max 0
      2257:20180220:140324.770 [file:vmware.c,line:86] zbx_mem_malloc(): out of memory (requested 24 bytes)
      2257:20180220:140324.771 [file:vmware.c,line:86] zbx_mem_malloc(): please increase VMwareCacheSize configuration parameter
      1772:20180220:140325.122 One child process died (PID:2257,exitcode/signal:1). Exiting ...
      2296:20180220:140325.122 Got signal [signal:11(SIGSEGV),reason:128,refaddrnil)]. Crashing ...
      2296:20180220:140325.126 ====== Fatal information: ======
      1772:20180220:140405.908 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).
      22616:20180220:140416.463 Starting Zabbix Server. Zabbix 3.4.6 (revision 76823).

      I have googled this problem, most of solutions are increasing VMwareCacheSize. I have increased this parameter and configured shared memory on my linux Server as following:

      [root@static zabbix]# ipcs -lm

      ------ Shared Memory Limits --------
      max number of segments = 4096
      max seg size (kbytes) = 10485760
      max total shared memory (kbytes) = 42949672960
      min seg size (bytes) = 1

      [root@static zabbix]# cat /etc/sysctl.conf
      # sysctl settings are defined through files in
      # /usr/lib/sysctl.d/, /run/sysctl.d/, and /etc/sysctl.d/.
      #
      # Vendors settings live in /usr/lib/sysctl.d/.
      # To override a whole file, create a new file with the same in
      # /etc/sysctl.d/ and put new settings there. To override
      # only specific settings, add a file with a lexically later
      # name in /etc/sysctl.d/ and put new settings there.
      #
      # For more information, see sysctl.conf(5) and sysctl.d(5).
      #
      kernel.shmmax=10737418240
      kernel.shmall=10737418240

      My Zabbix Server Config File as below:

      ############ ADVANCED PARAMETERS ################

      ### Option: StartPollers
      # Number of pre-forked instances of pollers.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      StartPollers=30

      ### Option: StartIPMIPollers
      # Number of pre-forked instances of IPMI pollers.
      # The IPMI manager process is automatically started when at least one IPMI poller is started.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      # StartIPMIPollers=0

      ### Option: StartPreprocessors
      # Number of pre-forked instances of preprocessing workers.
      # The preprocessing manager process is automatically started when preprocessor worker is started.
      #
      # Mandatory: no
      # Range: 1-1000
      # Default:
      StartPreprocessors=1

      ### Option: StartPollersUnreachable
      # Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).
      # At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers
      # are started.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      StartPollersUnreachable=2

      ### Option: StartTrappers
      # Number of pre-forked instances of trappers.
      # Trappers accept incoming connections from Zabbix sender, active agents and active proxies.
      # At least one trapper process must be running to display server availability and view queue
      # in the frontend.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      # StartTrappers=5

      ### Option: StartPingers
      # Number of pre-forked instances of ICMP pingers.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      # StartPingers=1

      ### Option: StartDiscoverers
      # Number of pre-forked instances of discoverers.
      #
      # Mandatory: no
      # Range: 0-250
      # Default:
      StartDiscoverers=10

      ### Option: StartHTTPPollers
      # Number of pre-forked instances of HTTP pollers.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      # StartHTTPPollers=1

      ### Option: StartTimers
      # Number of pre-forked instances of timers.
      # Timers process time-based trigger functions and maintenance periods.
      # Only the first timer process handles the maintenance periods.
      #
      # Mandatory: no
      # Range: 1-1000
      # Default:
      # StartTimers=1

      ### Option: StartEscalators
      # Number of pre-forked instances of escalators.
      #
      # Mandatory: no
      # Range: 0-100
      # Default:
      # StartEscalators=1

      ### Option: StartAlerters
      # Number of pre-forked instances of alerters.
      # Alerters send the notifications created by action operations.
      #
      # Mandatory: no
      # Range: 0-100
      # Default:
      # StartAlerters=3

      ### Option: JavaGateway
      # IP address (or hostname) of Zabbix Java gateway.
      # Only required if Java pollers are started.
      #
      # Mandatory: no
      # Default:
      # JavaGateway=

      ### Option: JavaGatewayPort
      # Port that Zabbix Java gateway listens on.
      #
      # Mandatory: no
      # Range: 1024-32767
      # Default:
      # JavaGatewayPort=10052

      ### Option: StartJavaPollers
      # Number of pre-forked instances of Java pollers.
      #
      # Mandatory: no
      # Range: 0-1000
      # Default:
      # StartJavaPollers=0

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

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

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

      ### 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=2G

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

      ### Option: SNMPTrapperFile
      # Temporary file used for passing data from SNMP trap daemon to the server.
      # Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.
      #
      # Mandatory: no
      # Default:
      # SNMPTrapperFile=/tmp/zabbix_traps.tmp

      SNMPTrapperFile=/var/log/snmptrap/snmptrap.log

      ### Option: StartSNMPTrapper
      # If 1, SNMP trapper process is started.
      #
      # Mandatory: no
      # Range: 0-1
      # Default:
      # StartSNMPTrapper=0

      ### Option: ListenIP
      # List of comma delimited IP addresses that the trapper should listen on.
      # Trapper will listen on all network interfaces if this parameter is missing.
      #
      # Mandatory: no
      # Default:
      # ListenIP=0.0.0.0

      # ListenIP=127.0.0.1

      ### Option: HousekeepingFrequency
      # How often Zabbix will perform housekeeping procedure (in hours).
      # Housekeeping is removing outdated information from the database.
      # To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
      # hours of outdated information are deleted in one housekeeping cycle, for each item.
      # To lower load on server startup housekeeping is postponed for 30 minutes after server start.
      # With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
      # In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
      # period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
      #
      # Mandatory: no
      # Range: 0-24
      # Default:
      # HousekeepingFrequency=1

      ### Option: MaxHousekeeperDelete
      # The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
      # [housekeeperid], [tablename], [field], [value].
      # No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
      # will be deleted per one task in one housekeeping cycle.
      # SQLite3 does not use this parameter, deletes all corresponding rows without a limit.
      # If set to 0 then no limit is used at all. In this case you must know what you are doing!
      #
      # Mandatory: no
      # Range: 0-1000000
      # Default:
      # MaxHousekeeperDelete=5000

      ### Option: CacheSize
      # Size of configuration cache, in bytes.
      # Shared memory size for storing host, item and trigger data.
      #
      # Mandatory: no
      # Range: 128K-8G
      # Default:
      CacheSize=4G

      ### Option: CacheUpdateFrequency
      # How often Zabbix will perform update of configuration cache, in seconds.
      #
      # Mandatory: no
      # Range: 1-3600
      # Default:
      # CacheUpdateFrequency=60

      ### Option: StartDBSyncers
      # Number of pre-forked instances of DB Syncers.
      #
      # Mandatory: no
      # Range: 1-100
      # Default:
      # StartDBSyncers=3

      ### Option: HistoryCacheSize
      # Size of history cache, in bytes.
      # Shared memory size for storing history data.
      #
      # Mandatory: no
      # Range: 128K-2G
      # Default:
      HistoryCacheSize=500M

      ### Option: HistoryIndexCacheSize
      # Size of history index cache, in bytes.
      # Shared memory size for indexing history cache.
      #
      # Mandatory: no
      # Range: 128K-2G
      # Default:
      HistoryIndexCacheSize=100M

      ### Option: TrendCacheSize
      # Size of trend cache, in bytes.
      # Shared memory size for storing trends data.
      #
      # Mandatory: no
      # Range: 128K-2G
      # Default:
      TrendCacheSize=500M

      ### Option: ValueCacheSize
      # Size of history value cache, in bytes.
      # Shared memory size for caching item history data requests.
      # Setting to 0 disables value cache.
      #
      # Mandatory: no
      # Range: 0,128K-64G
      # Default:
      ValueCacheSize=500M

      ### Option: Timeout
      # Specifies how long we wait for agent, SNMP device or external check (in seconds).
      #
      # Mandatory: no
      # Range: 1-30
      # Default:
      # Timeout=3
      Timeout=30

      ### Option: TrapperTimeout
      # Specifies how many seconds trapper may spend processing new data.
      #
      # Mandatory: no
      # Range: 1-300
      # Default:
      # TrapperTimeout=300

      ### Option: UnreachablePeriod
      # After how many seconds of unreachability treat a host as unavailable.
      #
      # Mandatory: no
      # Range: 1-3600
      # Default:
      UnreachablePeriod=3600

      ### Option: UnavailableDelay
      # How often host is checked for availability during the unavailability period, in seconds.
      #
      # Mandatory: no
      # Range: 1-3600
      # Default:
      UnavailableDelay=3600

      ### Option: UnreachableDelay
      # How often host is checked for availability during the unreachability period, in seconds.
      #
      # Mandatory: no
      # Range: 1-3600
      # Default:
      UnreachableDelay=3600

      ### Option: AlertScriptsPath
      # Full path to location of custom alert scripts.
      # Default depends on compilation options.
      #
      # Mandatory: no
      # Default:
      # AlertScriptsPath=${datadir}/zabbix/alertscripts

      AlertScriptsPath=/usr/lib/zabbix/alertscripts

      ### Option: ExternalScripts
      # Full path to location of external scripts.
      # Default depends on compilation options.
      #
      # Mandatory: no
      # Default:
      # ExternalScripts=${datadir}/zabbix/externalscripts

      ExternalScripts=/usr/lib/zabbix/externalscripts

      ### Option: FpingLocation
      # Location of fping.
      # Make sure that fping binary has root ownership and SUID flag set.
      #
      # Mandatory: no
      # Default:
      # FpingLocation=/usr/sbin/fping

      ### Option: Fping6Location
      # Location of fping6.
      # Make sure that fping6 binary has root ownership and SUID flag set.
      # Make empty if your fping utility is capable to process IPv6 addresses.
      #
      # Mandatory: no
      # Default:
      # Fping6Location=/usr/sbin/fping6

      ### Option: SSHKeyLocation
      # Location of public and private keys for SSH checks and actions.
      #
      # Mandatory: no
      # Default:
      # SSHKeyLocation=

      ### Option: LogSlowQueries
      # How long a database query may take before being logged (in milliseconds).
      # Only works if DebugLevel set to 3, 4 or 5.
      # 0 - don't log slow queries.
      #
      # Mandatory: no
      # Range: 1-3600000
      # Default:
      # LogSlowQueries=0

      LogSlowQueries=3000

      ### Option: TmpDir
      # Temporary directory.
      #
      # Mandatory: no
      # Default:
      # TmpDir=/tmp

      ### Option: StartProxyPollers
      # Number of pre-forked instances of pollers for passive proxies.
      #
      # Mandatory: no
      # Range: 0-250
      # Default:
      # StartProxyPollers=1

      ### Option: ProxyConfigFrequency
      # How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.
      # This parameter is used only for proxies in the passive mode.
      #
      # Mandatory: no
      # Range: 1-3600*24*7
      # Default:
      # ProxyConfigFrequency=3600

      ### Option: ProxyDataFrequency
      # How often Zabbix Server requests history data from a Zabbix Proxy in seconds.
      # This parameter is used only for proxies in the passive mode.
      #
      # Mandatory: no
      # Range: 1-3600
      # Default:
      # ProxyDataFrequency=1

      ### Option: AllowRoot
      # Allow the server to run as 'root'. If disabled and the server is started by 'root', the server
      # will try to switch to the user specified by the User configuration option instead.
      # Has no effect if started under a regular user.
      # 0 - do not allow
      # 1 - allow
      #
      # Mandatory: no
      # Default:
      # AllowRoot=0

      ### Option: User
      # Drop privileges to a specific, existing user on the system.
      # Only has effect if run as 'root' and AllowRoot is disabled.
      #
      # Mandatory: no
      # Default:
      # User=zabbix

      ### Option: Include
      # You may include individual files or all files in a directory in the configuration file.
      # Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
      #
      # Mandatory: no
      # Default:
      # Include=

      # Include=/usr/local/etc/zabbix_server.general.conf
      # Include=/usr/local/etc/zabbix_server.conf.d/
      # Include=/usr/local/etc/zabbix_server.conf.d/*.conf

      ### Option: SSLCertLocation
      # Location of SSL client certificates.
      # This parameter is used only in web monitoring.
      #
      # Mandatory: no
      # Default:
      # SSLCertLocation=${datadir}/zabbix/ssl/certs

      ### Option: SSLKeyLocation
      # Location of private keys for SSL client certificates.
      # This parameter is used only in web monitoring.
      #
      # Mandatory: no
      # Default:
      # SSLKeyLocation=${datadir}/zabbix/ssl/keys

      ### Option: SSLCALocation
      # Override the location of certificate authority (CA) files for SSL server certificate verification.
      # If not set, system-wide directory will be used.
      # This parameter is used only in web monitoring and SMTP authentication.
      #
      # Mandatory: no
      # Default:
      # SSLCALocation=

      ####### LOADABLE MODULES #######

      ### Option: LoadModulePath
      # Full path to location of server modules.
      # Default depends on compilation options.
      #
      # Mandatory: no
      # Default:
      # LoadModulePath=${libdir}/modules

      ### Option: LoadModule
      # Module to load at server startup. Modules are used to extend functionality of the server.
      # Format: LoadModule=<module.so>
      # The modules must be located in directory specified by LoadModulePath.
      # It is allowed to include multiple LoadModule parameters.
      #
      # Mandatory: no
      # Default:
      # LoadModule=

      ####### TLS-RELATED PARAMETERS #######

      ### Option: TLSCAFile
      # Full pathname of a file containing the top-level CA(s) certificates for
      # peer certificate verification.
      #
      # Mandatory: no
      # Default:
      # TLSCAFile=

      ### Option: TLSCRLFile
      # Full pathname of a file containing revoked certificates.
      #
      # Mandatory: no
      # Default:
      # TLSCRLFile=

      ### Option: TLSCertFile
      # Full pathname of a file containing the server certificate or certificate chain.
      #
      # Mandatory: no
      # Default:
      # TLSCertFile=

      ### Option: TLSKeyFile
      # Full pathname of a file containing the server private key.
      #
      # Mandatory: no
      # Default:
      # TLSKeyFile=


      After I increase these parameters, the issue is still occured. Anyone has solution for this problem? Please help me fix this issue.
      What version of Z are you on? If not on 3.4.7, it might be worth giving it a shot. There a bug fix that might be affecting you.

      3.4.7 release notes: https://www.zabbix.com/rn/rn3.4.7

      See this bug: ZBX-13441
      • fixed crashes in case of failures (e.g. timeouts) during VMware hypervisor discovery

        Comment

        • trungson122
          Junior Member
          • Dec 2015
          • 2
          #3
          @tcilmo, thank for your supporting. I have updated Zabbix to 3.4.7 version.
          [root@static ~]# rpm -qa | grep zabbix
          zabbix-server-mysql-3.4.7-1.el7.x86_64
          zabbix-agent-3.4.7-1.el7.x86_64
          zabbix-web-3.4.7-1.el7.noarch
          zabbix-release-3.4-2.el7.noarch
          zabbix-web-mysql-3.4.7-1.el7.noarch

          It seems to be fine after upgrading. I still monitor Zabbix Server status since yesterday. Recently, My Zabbix Server is monitoring 98 ESXi Hosts and 627 Vms on them. Anyone has anyidea about Zabbix Server Config File for this scenario??

          Thank & Brgs!

            Comment

            Previous template Next
            Working...