-
Type:
Documentation task
-
Resolution: Unresolved
-
Priority:
Major
-
None
-
Affects Version/s: 7.0.26rc1, 7.4.10rc1, 8.0.0beta1 (master)
-
Component/s: Server (S)
-
None
-
Environment:8.0/7.4/7.0
-
Support backlog
Hello,
This is an output of "zabbix_server --help" ran on 7.0 LTS:
zabbix_server -help
Usage:
zabbix_server [-c config-file]
zabbix_server [-c config-file] -R runtime-option
zabbix_server [-c config-file] -T
zabbix_server -h
zabbix_server -V
The core daemon of Zabbix software.
Options:
-c --config config-file Path to the configuration file
(default: "/etc/zabbix/zabbix_server.conf")
-f --foreground Run Zabbix server in foreground
-R --runtime-control runtime-option Perform administrative functions
Runtime control options:
config_cache_reload Reload configuration cache
housekeeper_execute Execute the housekeeper
trigger_housekeeper_execute Execute the trigger housekeeper
log_level_increase=target Increase 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
snmp_cache_reload Reload SNMP cache
secrets_reload Reload secrets from Vault
diaginfo=section Log internal diagnostic information of the
section (historycache, preprocessing, alerting,
lld, valuecache, locks, connector) or everything if section is
not specified
prof_enable=target Enable profiling, affects all processes if
target is not specified
prof_disable=target Disable profiling, affects all processes if
target is not specified
service_cache_reload Reload service manager cache
ha_status Display HA cluster status
ha_remove_node=target Remove the HA node specified by its name or ID
ha_set_failover_delay=delay Set HA failover delay
proxy_config_cache_reload[=name] Reload configuration cache on proxy by its name,
comma-separated list can be used to pass multiple names.
All proxies will be reloaded if no names were specified.
Log level control targets:
process-type All processes of specified type
(alerter, alert manager, alert syncer, availability manager,
browser poller, configuration syncer, configuration syncer worker,
connector manager, connector worker, discovery manager, discovery worker,
escalator, ha manager, history poller, history syncer, housekeeper,
http poller, http agent poller, icmp pinger, internal poller,
ipmi manager, ipmi poller, java poller, lld manager, lld worker,
odbc poller, poller, agent poller, preprocessing manager,
preprocessing worker, proxy poller, proxy group manager, report manager,
report writer, self-monitoring, service manager, snmp poller, snmp trapper,
task manager, timer, trapper, trigger housekeeper, unreachable poller,
vmware collector)
process-type,N Process type and number (e.g., poller,3)
pid Process identifier
Profiling control targets:
process-type All processes of specified type
(alerter, alert manager, alert syncer, availability manager,
browser poller, configuration syncer, configuration syncer worker,
connector manager, connector worker, discovery manager, discovery worker,
escalator, ha manager, history poller, history syncer, housekeeper,
http poller, http agent poller, icmp pinger, internal poller,
ipmi manager, ipmi poller, java poller, lld manager, lld worker,
odbc poller, poller, agent poller, preprocessing manager,
preprocessing worker, proxy poller, proxy group manager, report manager,
report writer, self-monitoring, service manager, snmp poller, snmp trapper,
task manager, timer, trapper, trigger housekeeper, unreachable poller,
vmware collector)
process-type,N Process type and number (e.g., history syncer,1)
pid Process identifier
scope Profiling scope
(rwlock, mutex, processing) can be used with process-type
(e.g., history syncer,1,processing)
-T --test-config Validate configuration file and exit
-h --help Display this help message
-V --version Display version number
Some configuration parameter default locations:
AlertScriptsPath "/usr/lib/zabbix/alertscripts"
ExternalScripts "/usr/lib/zabbix/externalscripts"
SSLCertLocation "/usr/share/zabbix/ssl/certs"
SSLKeyLocation "/usr/share/zabbix/ssl/keys"
LoadModulePath "/usr/lib64/zabbix/modules"
Report bugs to: <https://support.zabbix.com>
Zabbix home page: <https://www.zabbix.com>
Documentation: <https://www.zabbix.com/documentation>
important part to take a look into is "Log level control targets" - target "discovery worker" is still included, but when user will try to increase logging level, this would be returned:
zabbix_server -R log_level_increase='discovery worker' Cannot redirect signal: "discovery worker" process does not exist
could be worth to change this, to not include processes like "discovery worker"