Where is zabbix server.conf

StartHistoryPollers no 5 Number of pre-forked instances of history pollers. StartJavaPollers no 0 Number of pre-forked instances of Java pollers 1. At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started. StartPollers no 5 Number of pre-forked instances of pollers 1. StartPreprocessors no 3 Number of pre-forked instances of preprocessing workers 1.

The preprocessing manager process is automatically started when a preprocessor worker is started. StartProxyPollers no 1 Number of pre-forked instances of pollers for passive proxies 1. StartReportWriters no 0 Number of pre-forked instances of report writers. If set to 0, scheduled report generation is disabled. The report manager process is automatically started when a report writer is started. StartTimers no 1 Number of pre-forked instances of timers.

Timers process maintenance periods. StartTrappers no 5 Number of pre-forked instances of trappers 1. Trappers accept incoming connections from Zabbix sender, active agents and active proxies.

Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted. If IPv6 support is enabled then ' TLSCAFile no Full pathname of a file containing the top-level CA s certificates for peer certificate verification, used for encrypted communications between Zabbix components. TLSCertFile no Full pathname of a file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.

Override the default ciphersuite selection criteria for certificate- and PSK-based encryption. Override the default ciphersuite selection criteria for certificate-based encryption. Override the default ciphersuite selection criteria for PSK-based encryption. This parameter is used for encrypted communications between Zabbix components. TLSKeyFile no Full pathname of a file containing the server private key, used for encrypted communications between Zabbix components.

TrapperTimeout no Specifies how many seconds trapper may spend processing new data. Shared memory size for storing trends data. Shared memory size for caching calculated trend function data. UnavailableDelay no 60 How often host is checked for availability during the unavailability period, in seconds. UnreachableDelay no 15 How often host is checked for availability during the unreachability period, in seconds.

UnreachablePeriod no 45 After how many seconds of unreachability treat a host as unavailable. User no zabbix Drop privileges to a specific, existing user on the system. Only has effect if run as 'root' and AllowRoot is disabled. Shared memory size for caching item history data requests. Setting to 0 disables value cache not recommended. When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes. VaultDBPath no Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.

VaultToken no Vault authentication token that should have been generated exclusively for Zabbix server with read-only permission to the paths specified in Vault macros and read-only permission to the path specified in the optional VaultDBPath configuration parameter.

A VMware internal check zabbix[vmware,buffer,…] can be used to monitor the VMware cache usage see Internal checks. Note that shared memory is not allocated if there are no vmware collector instances configured to start. This delay should be set to the least update interval of any VMware monitoring item. VMwarePerfFrequency no 60 Delay in seconds between performance counter statistics retrieval from a single VMware service.

This delay should be set to the least update interval of any VMware monitoring item that uses VMware performance counters. This will cause Zabbix server to stop usually shortly after the start, but sometimes it can take more time. The configuration file should be revised or the limit should be raised to avoid this situation.

All rights reserved. Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4. Location of custom alert scripts depends on compile-time installation variable datadir. Allow the server to run as 'root'. Size of configuration cache, in bytes. How often Zabbix will perform update of configuration cache, in seconds.

Database host name. Database name. Database port when not using local socket. Full pathname of a file containing the top-level CA s certificates for database certificate verification. Full pathname of file containing Zabbix server certificate for authenticating to database. Full pathname of file containing the private key for authenticating to database. The list of encryption ciphersuites that Zabbix server permits for TLSv1.

Specifies debug level: 0 - basic information about starting and stopping of Zabbix processes 1 - critical information 2 - error information 3 - warnings 4 - for debugging produces lots of information 5 - extended debugging produces even more information See also runtime control options. Directory for real-time export of events, history and trends in newline-delimited JSON format.

Maximum size per export file in bytes. List of comma-delimited entity types events, history, trends for real-time export all types by default. Location of external scripts depends on compile-time installation variable datadir. Location of fping6. Location of fping. Size of history index cache, in bytes.

Enable preprocessing of history values in history storage to store values in different indices based on date: 0 - disable 1 - enable. Comma separated list of value types to be sent to the history storage. How often Zabbix will perform housekeeping procedure in hours. You may include individual files or all files in a directory in the configuration file. If you see the error ERROR : Access denied for user 'zabbix' 'localhost' using password: YES then make sure you used the password for the zabbix user and not the root user.

In order for the Zabbix server to use this database, you need to set the database password in the Zabbix server configuration file. Open the configuration file in your editor:. These comments in the file explain how to connect to the database. We need to set the DBPassword value in the file to the password for our database user. Add this line below those comments to configure the database:. That takes care of the Zabbix server configuration, but we have to make some modifications to our PHP setup in order for the Zabbix web interface to work properly.

The Zabbix installation process created an Apache configuration file that contains these settings. We need to make a small change to this file, so open it up. The file contains PHP settings that meet the necessary requirements for the Zabbix web interface.

The only change you need to make is to set the appropriate timezone, which is commented out by default. Uncomment the timezone line, highlighted above, and change it to your time zone. You can use this list of supported time zones to find the right one for you. Then save and close the file.

The web interface lets us see reports and add hosts that we want to monitor, but it needs some initial setup before we can use it. On the first screen, you will see a welcome message. Click Next step to continue. All of the values in this table must be OK , so verify that they are. Be sure to scroll down and look at all of the prerequisites.

We told the Zabbix server about our database, but the Zabbix web interface also needs access to the database to manage hosts and read data. The Name is optional; it is used in the web interface to distinguish one server from another in case you have several monitoring servers.

Click Next step to proceed. The web interface setup is complete! Click Finish to proceed to the login screen. The default user is Admin and the password is zabbix. Then, just like on the Zabbix server, run the following commands to install the repository configuration package:. While Zabbix supports certificate-based encryption, setting up a certificate authority is beyond the scope of this tutorial, but we can use pre-shared keys PSK to secure the connection between the server and agent.

Now edit the Zabbix agent settings to set up its secure connection to the Zabbix server. Open the agent configuration file in your text editor:. Each setting within this file is documented via informative comments throughout the file, but you only need to edit some of them.

Next, find the section that configures the secure connection to the Zabbix server and enable pre-shared key support. Find the TSLConnect section, which looks like this:.

Zabbix server is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run server as any non-root user without any issues.

If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run server as 'root' if you modify the 'AllowRoot' parameter in the server configuration file accordingly.

If Zabbix server and agent are run on the same machine it is recommended to use a different user for running the server than for running the agent. Otherwise, if both are run as the same user, the agent can access the server configuration file and any Admin level user in Zabbix can quite easily retrieve, for example, the database password.

Due to the security requirements and mission-critical nature of server operation, UNIX is the only operating system that can consistently deliver the necessary performance, fault tolerance and resilience.

Zabbix operates on market leading versions. Note that the server requires a UTF-8 locale so that some textual items can be interpreted correctly.

Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically. Recent Changes.