Zabbix Documentation 2.0

2.23.04.0 (current)In development:4.2 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


Sidebar

manual:appendix:config:zabbix_server

1 Zabbix server

The parameters supported in a Zabbix server configuration file:

ParameterMandatoryRangeDefaultDescription
AlertScriptsPath no /usr/local/share/zabbix/alertscripts Location of custom alert scripts (depends on compile-time installation variable datadir).
CacheSize no 128K-2G 8M Size of configuration cache, in bytes.
Shared memory size for storing host, item and trigger data.
The upper limit used to be 1G before version 2.0.5.
CacheUpdateFrequency no 1-3600 60 How often Zabbix will perform update of configuration cache, in seconds.
DBHost no localhost Database host name.
In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL
only empty string results in attempt to use socket.
DBName yes Database name.
For SQLite3 path to database file must be provided. DBUser and DBPassword are ignored.
DBPassword no Database password. Ignored for SQLite.
Comment this line if no password is used.
DBPort no 1024-65535 3306 Database port when not using local socket. Ignored for SQLite.
DBSchema no Schema name. Used for IBM DB2.
DBSocket no /tmp/mysql.sock Path to MySQL socket.
DBUser no Database user. Ignored for SQLite.
DebugLevel no 0-4 3 Specifies debug level:
0 - no debug
1 - critical information
2 - error information
3 - warnings
4 - for debugging (produces lots of information)
DisableHousekeeping no 0-1 0 If set to 1, housekeeping is disabled.
ExternalScripts no /usr/local/share/zabbix/externalscripts Location of external scripts (depends on compile-time installation variable datadir).
Fping6Location no /usr/sbin/fping6 Location of fping6.
Make sure that fping6 binary has root ownership and SUID flag set.
Make empty (“Fping6Location=”) if your fping utility is capable to process IPv6 addresses.
FpingLocation no /usr/sbin/fping Location of fping.
Make sure that fping binary has root ownership and SUID flag set!
HistoryCacheSize no 128K-2G 8M Size of history cache, in bytes.
Shared memory size for storing history data.
The upper limit used to be 1G before version 2.0.5.
HistoryTextCacheSize no 128K-2G 16M Size of text history cache, in bytes.
Shared memory size for storing character, text or log history data.
The upper limit used to be 1G before version 2.0.5.
HousekeepingFrequency no 1-24 1 How often Zabbix will perform housekeeping procedure (in hours).
Housekeeping is removing outdated information from the database.
Note: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.
Include no You may include individual files or all files in a directory in the configuration file. See special notes about limitations.
JavaGateway no IP address (or hostname) of Zabbix Java gateway.
Only required if Java pollers are started.
This option is supported in version 2.0.0 and higher.
JavaGatewayPort no 1024-32767 10052 Port that Zabbix Java gateway listens on.
This option is supported in version 2.0.0 and higher.
ListenIP no 0.0.0.0 List of comma delimited IP addresses that the trapper should listen on.
Trapper will listen on all network interfaces if this parameter is missing.
Multiple IP addresses are supported in version 1.8.3 and higher.
ListenPort no 1024-32767 10051 Listen port for trapper.
LogFileSize no 0-1024 1 Maximum size of log file in MB.
0 - disable automatic log rotation.
LogFile no Name of log file.
LogSlowQueries no 0-3600000 0 How long a database query may take before being logged (in milliseconds).
0 - don't log slow queries.
This option becomes enabled starting with DebugLevel=3.
Supported since Zabbix 1.8.2 version.
MaxHousekeeperDelete no 0-1000000 500 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!
This parameter is supported since Zabbix 1.8.2 and applies only to deleting history and trends of already deleted items.
NodeID no 0-999 0 Unique NodeID in distributed setup.
0 - standalone server
NodeNoEvents no 0-1 0 If set to '1' local events won't be sent to master node.
This won't impact ability of this node to propagate events from its child nodes.
NodeNoHistory no 0-1 0 If set to '1' local history won't be sent to master node.
This won't impact ability of this node to propagate history from its child nodes.
PidFile no /tmp/zabbix_server.pid Name of PID file.
ProxyConfigFrequency no 1-604800 3600 How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.
This option is supported in version 1.8.3 and higher.
ProxyDataFrequency no 1-3600 1 How often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode.
This option is supported in version 1.8.3 and higher.
SenderFrequency no 5-3600 30 How often Zabbix will try to send unsent alerts (in seconds).
SNMPTrapperFile no /tmp/zabbix_traps.tmp 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.
This option is supported in version 2.0.0 and higher.
SourceIP no Source IP address for outgoing connections.
SSHKeyLocation no Location of public and private keys for SSH checks and actions
StartDBSyncers no 1-100 4 Number of pre-forked instances of DB Syncers.
The upper limit used to be 64 before version 1.8.5.
This option is supported in version 1.8.3 and higher.
StartDiscoverers no 0-250 1 Number of pre-forked instances of discoverers.
The upper limit used to be 255 before version 1.8.5.
StartHTTPPollers no 0-1000 1 Number of pre-forked instances of HTTP pollers.
The upper limit used to be 255 before version 1.8.5.
StartIPMIPollers no 0-1000 0 Number of pre-forked instances of IPMI pollers.
The upper limit used to be 255 before version 1.8.5.
StartJavaPollers no 0-1000 0 Number of pre-forked instances of Java pollers.
This option is supported in version 2.0.0 and higher.
StartPingers no 0-1000 1 Number of pre-forked instances of ICMP pingers.
The upper limit used to be 255 before version 1.8.5.
StartPollersUnreachable no 0-1000 1 Number of pre-forked instances of pollers for unreachable hosts (including IPMI).
The upper limit used to be 255 before version 1.8.5.
This option is missing in version 1.8.3.
StartPollers no 0-1000 5 Number of pre-forked instances of pollers.
The upper limit used to be 255 before version 1.8.5.
StartProxyPollers no 0-250 1 Number of pre-forked instances of pollers for passive proxies.
The upper limit used to be 255 before version 1.8.5.
This option is supported in version 1.8.3 and higher.
StartSNMPTrapper no 0-1 0 If set to 1, SNMP trapper process will be started.
This option is supported in version 2.0.0 and higher.
StartTrappers no 0-1000 5 Number of pre-forked instances of trappers.
Trappers accept incoming connections from Zabbix sender, active agents, active proxies and child nodes.
At least one trapper process must be running to display server availability in the frontend.
The upper limit used to be 255 before version 1.8.5.
Timeout no 1-30 3 Specifies how long we wait for agent, SNMP device or external check (in seconds).
TmpDir no /tmp Temporary directory.
TrapperTimeout no 1-300 300 Specifies how many seconds trapper may spend processing new data.
TrendCacheSize no 128K-2G 4M Size of trend cache, in bytes.
Shared memory size for storing trends data.
The upper limit used to be 1G before version 2.0.5.
UnavailableDelay no 1-3600 60 How often host is checked for availability during the unavailability period, in seconds.
UnreachableDelay no 1-3600 15 How often host is checked for availability during the unreachability period, in seconds.
UnreachablePeriod no 1-3600 45 After how many seconds of unreachability treat a host as unavailable.

Zabbix supports configuration files only in UTF-8 encoding without BOM.