manual:concepts:server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:concepts:server [2014/09/25 15:14]
sasha Links adapted because of a move operation
manual:concepts:server [2020/03/02 12:08]
marinagen New runtime control option: snmp_cache_reload
Line 1: Line 1:
-==== - #2 Server ====+==== Server ====
  
 === Overview === === Overview ===
Line 13: Line 13:
 All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section. All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section.
  
-=== Server process ​===+=== Running server ​=== 
 + 
 +== If installed as package ​==
  
 Zabbix server runs as a daemon process. The server can be started by executing: Zabbix server runs as a daemon process. The server can be started by executing:
  
-  shell> ​cd sbin +  shell> ​service zabbix-server start 
-  shell> ./​zabbix_server+ 
 +This will work on most of GNU/Linux systems. On other systems you may need to run: 
 + 
 +  shell> ​/etc/init.d/zabbix-server start 
 + 
 +Similarly, for stopping/​restarting/​viewing status, use the following commands: 
 + 
 +  shell> service zabbix-server stop 
 +  shell> service zabbix-server restart 
 +  shell> service zabbix-server status 
 + 
 +== Start up manually == 
 + 
 +If the above does not work you have to start it manually. Find the path to the zabbix_server binary and execute: 
 + 
 +  shell> ​zabbix_server
  
-You can use the following command line parameters with Zabbix server :+You can use the following command line parameters with Zabbix server:
  
-<​code>​-c --config <​file> ​             ​absolute ​path to the configuration file (default is /etc/zabbix/​zabbix_server.conf)+<​code>​ 
 +-c --config <​file> ​             path to the configuration file (default is /usr/local/etc/​zabbix_server.conf)
 -R --runtime-control <​option> ​  ​perform administrative functions -R --runtime-control <​option> ​  ​perform administrative functions
 -h --help ​                      give this help -h --help ​                      give this help
Line 29: Line 47:
 <​note>​Runtime control is not supported on OpenBSD and NetBSD.</​note>​ <​note>​Runtime control is not supported on OpenBSD and NetBSD.</​note>​
  
-Examples of command line parameters:+Examples of running Zabbix server with command line parameters:
  
   shell> zabbix_server -c /​usr/​local/​etc/​zabbix_server.conf   shell> zabbix_server -c /​usr/​local/​etc/​zabbix_server.conf
   shell> zabbix_server --help   shell> zabbix_server --help
   shell> zabbix_server -V   shell> zabbix_server -V
- 
  
 == Runtime control == == Runtime control ==
Line 42: Line 59:
 ^Option^Description^Target^ ^Option^Description^Target^
 |config_cache_reload|Reload configuration cache. Ignored if cache is being currently loaded.| | |config_cache_reload|Reload configuration cache. Ignored if cache is being currently loaded.| |
-|log_level_increase[=<​**target**>​]|Increase log level, affects all processes if target is not specified.|**pid** - Process identifier (1 to 65535) \\ **process type** - All processes of specified type (e.g., poller) \\ **process type,N** - Process type and number (e.g., poller,3)|+|snmp_cache_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id) for all hosts.| | 
 +|housekeeper_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | 
 +|log_level_increase[=<​**target**>​]|Increase log level, affects all processes if target is not specified.|**process type** - All processes of specified type (e.g., poller)\\ See all [[#​server_process_types|server process types]].\\ **process type,N** - Process type and number (e.g., poller,3)\\ **pid** - Process identifier (1 to 65535). For larger values specify target as '​process type,​N'​.  ​|
 |log_level_decrease[=<​**target**>​]|Decrease log level, affects all processes if target is not specified.|:::​| |log_level_decrease[=<​**target**>​]|Decrease log level, affects all processes if target is not specified.|:::​|
- 
-Allowed range of PIDs for changing the log level of a single Zabbx process is from 1 to 65535. On systems with large PIDs <process type,N> target option can be used for changing the log level of a single process. 
  
 Example of using runtime control to reload the server configuration cache: Example of using runtime control to reload the server configuration cache:
  
   shell> zabbix_server -c /​usr/​local/​etc/​zabbix_server.conf -R config_cache_reload   shell> zabbix_server -c /​usr/​local/​etc/​zabbix_server.conf -R config_cache_reload
 +  ​
 +Example of using runtime control to reload the SNMP cache:
 +
 +  shell> zabbix_server -R snmp_cache_reload  ​
 +  ​
 +Example of using runtime control to trigger execution of housekeeper:​
 +
 +  shell> zabbix_server -c /​usr/​local/​etc/​zabbix_server.conf -R housekeeper_execute
  
 Examples of using runtime control to change log level: Examples of using runtime control to change log level:
Line 79: Line 104:
  
 The scripts are used to automatically start/stop Zabbix processes during system'​s start-up/​shutdown. The scripts are located under directory misc/​init.d. The scripts are used to automatically start/stop Zabbix processes during system'​s start-up/​shutdown. The scripts are located under directory misc/​init.d.
 +
 +=== Server process types ===
 +
 +  * ''​alert manager''​ - manager of alerter tasks
 +  * ''​alerter''​ - process for sending notifications
 +  * ''​configuration syncer''​ - process for managing in-memory cache of configuration data
 +  * ''​discoverer''​ - process for discovery of devices
 +  * ''​escalator''​ - process for escalation of actions
 +  * ''​history syncer''​ - history DB writer
 +  * ''​housekeeper''​ - process for removal of old historical data
 +  * ''​http poller''​ - web monitoring poller
 +  * ''​icmp pinger''​ - poller for icmpping checks
 +  * ''​ipmi manager''​ - IPMI poller manager
 +  * ''​ipmi poller''​ - poller for IPMI checks
 +  * ''​java poller''​ - poller for Java checks
 +  * ''​lld manager''​ - manager process of low-level discovery tasks
 +  * ''​lld worker''​ - worker process of low-level discovery tasks
 +  * ''​poller''​ - normal poller for passive checks
 +  * ''​preprocessing manager''​ - manager of preprocessing tasks
 +  * ''​preprocessing worker''​ - process for data preprocessing
 +  * ''​proxy poller''​ - poller for passive proxies
 +  * ''​self-monitoring''​ - process for collecting internal server statistics
 +  * ''​snmp trapper''​ - trapper for SNMP traps
 +  * ''​task manager''​ - process for remote execution of tasks requested by other components (e.g. close problem, acknowledge problem, check item value now, remote command functionality)
 +  * ''​timer''​ - timer for processing maintenances
 +  * ''​trapper''​ - trapper for active checks, traps, proxy communication
 +  * ''​unreachable poller''​ - poller for unreachable devices
 +  * ''​vmware collector''​ - VMware data collector responsible for data gathering from VMware services
 +
 +The server log file can be used to observe these process types.
 +
 +Various types of Zabbix server processes can be monitored using the **zabbix[process,<​type>,<​mode>,<​state>​]** internal [[:​manual/​config/​items/​itemtypes/​internal|item]].
  
 === Supported platforms === === Supported platforms ===
Line 99: Line 156:
 <​note>​Zabbix may work on other Unix-like operating systems as well.</​note>​ <​note>​Zabbix may work on other Unix-like operating systems as well.</​note>​
  
-(linking to other sections, like zabbix maintenance etc)+=== Locale ===
  
 +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.