Zabbix Documentation 3.0

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

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 [2014/10/23 14:58]
Igors H [Runtime control] added housekeeper runtime control option and example (igors)
manual:concepts:server [2018/10/15 08:15] (current)
martins-v more precise wording
Line 14: Line 14:
  
 === Server process === === Server process ===
 +
 +== 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+
  
-You can use the following command line parameters with Zabbix server ​:+This will work on most of GNU/Linux systems. On other systems you may need to run:
  
-<​code>​-c --config <​file> ​             absolute path to the configuration file (default is /etc/zabbix/​zabbix_server.conf)+  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: 
 + 
 +<​code>​ 
 +-c --config <​file> ​             absolute 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
Line 42: Line 60:
 ^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.| |
-|housekeeper_execute|Execute ​the housekeeper. Ignored if housekeeper ​is being currently ​executed.| |+|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 (e.g., poller) \\ **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.|**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)|
 |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.+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:
  
   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 trigger execution of housekeeper:​ Example of using runtime control to trigger execution of housekeeper:​
  
Line 105: Line 122:
 <​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.