Zabbix Documentation 5.0

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


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
manual:concepts:server [2018/11/08 07:20]
martins-v updating content with process listing
manual:concepts:server [2020/03/06 13:25] (current)
marinagen snmp_chache_reload description slightly edited
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 == == If installed as package ==
Line 52: Line 52:
   shell> zabbix_server --help   shell> zabbix_server --help
   shell> zabbix_server -V   shell> zabbix_server -V
- 
  
 == Runtime control == == Runtime control ==
Line 60: 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.| |
 +|snmp_cache_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.| |
 |housekeeper_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | |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.|**pid** - Process identifier (1 to 65535) \\ **process type** - All processes of specified type (alerter, alert manager, configuration syncer, discoverer, escalator, history syncer, housekeeperhttp poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, preprocessing manager, preprocessing worker, proxy poller, self-monitoring,​ snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector) \\ **process type,N** - Process type and number (e.g., poller,3)|+|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 Zabbix process is from 1 to 65535. On systems with PIDs>​65535,​ a <process type,N> target can be used as a workaround for changing the log level of a single process (e.g.%%"​%%history syncer,​6%%"​%%). 
  
 Example of using runtime control to reload the server configuration cache: Example of using runtime control to reload the server configuration cache:
Line 70: Line 68:
   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:​ Example of using runtime control to trigger execution of housekeeper:​
Line 103: 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 ===