第1章 Zabbix简介及组成

1.1 zabbix简介

zabbix是一个基于web界面，提供分布式系统监视以及网络监视功能的企业级的开源解决方案。它可以监视各种网络参数，保证服务器自动的安全运营，并提供灵活的通知机制以让系统管理员快速定位/解决存在的各种问题

1.1 zabbix组成

zabbix server和zabbix agent，可选组件zabbix proxy

可以通过SNMP、zabbix agent、fping、端口监视等方法对远程服务器或网络状态完成监视/数据收集等功能。支持linux及类unix、windows平台只能安装客户端(被监控)

第2章 Zabbix 3.0.13服务端安装

zabbix server3.0无法centos6上进行yum安装，故我们要在centos7上进行yum安装。如果一定要在centos6上进行安装，则强烈建议通过源码方式进行编译安装，同时还需要注意PHP的版本

注意：尽管zabbix server3.0在centos6上不能进行yum安装，但zabbix agent3.0在centos6上是可进行yum安装的

第3章 Web页面报错总结

3.1 问题一Zabbix alerter processes more than 75% busy

问题原因：

zabbix服务器邮件进程繁忙导致的，一般是因为设置动作的间隔太短。特殊情况下会产生大量告警，如服务器发几万封邮件过程中，邮件进程发挂了

解决方案：

01.删除数据库解决(风险较大，不建议)

02.修改邮件脚本，将邮件的动作改为打印时间，等待邮件完全释放再改回来，如下

[root@m01 ~]# cat /usr/lib/zabbix/alertscripts/sms #!/bin/bash echo `date` >>/tmp/sms.txt

3.2 问题二Zabbix discoverer processes more than 75% busy

问题原因：

01.配置了discovery自动发现任务，配置的每个discovery任务在一定时间内占用1个进程，而zabbix_server.conf中默认配置只有1个discovery(被注释，默认生效)

02.为了快速验证自动发现效果，将discovery任务的"Delay"由默认3600s设置成60s

解决方案：

01.修改配置文件中的StartDiscoverers进程数量，取消其之前的#号并将数值修改为5，最后重启服务

(注：根据系统硬件配置，可以设置成更高的数值，但其范围为0~250)

 [root@m01 ~]# grep 'StartDiscoverers' /etc/zabbix/zabbix_server.conf

 ### Option: StartDiscoverers

 StartDiscoverers=

 [root@m01 ~]# systemctl restart zabbix-server.service

02.编写定时任务脚本重启zabbix_server来降低负载

 [root@m01 ~]# crontab -e

 @daily service zabbix-server restart > /dev/null >&

 #计划会每天自动重启Zabbix服务以结束僵尸进程并清理内存等

3.3 问题三Zabbix poller processes more than 75% busy

问题原因：

01.通过Zabbix agent采集数据的设备死机或其他原因导致zabbix agent死掉server获取不到数据

02. server向agent获取数据时时间过长，超过了server设置的timeout时间

解决方案：

01.增加Zabbix Server启动时初始化的进程数量

### Option: StartPollers StartPollers= #改成多少取决于服务器的性能和监控的数量，如果内存足够的话可以设置更高

02.修改模板自动发现规则中的保留失去的资源期间为0

3.4 问题四Zabbix housekeeper processes more than 75% busy

问题原因：

为了防止数据库持续增大，zabbix有自动删除历史数据的机制即housekeeper，而mysql删除数据时性能会降低，就会报错

解决方案：

调整HousekeepingFrequency参数

HousekeepingFrequency= #间隔时间 MaxHousekeeperDelete= #最大删除量

3.5 问题五Zabbix server内存溢出，无法启动

问题原因：

zabbix使用一段时间后，再次加入一批交换机监控，zabbix-server将无法启动，查看日志显示如下(提示内存溢出，需调整zabbix服务器配置zabbix_server.conf)

 ::174352.675 [file:dbconfig.c,line:] zbx_mem_realloc(): out of memory (requested  bytes)

 ::174352.675 [file:dbconfig.c,line:] zbx_mem_realloc(): please increase CacheSize configuration parameter

解决方案：

vim zabbix_server.conf CacheSize=1024M #默认为8M

3.6 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 11 bytes)

问题原因：

zabbix某些页面无法打开，查看php日志发现，当访问这个页面时报错内存不足

解决方案：

不清楚是否内存泄露，最简单的方法是调大php进程的可用内存

[root@zabbix-master ~]# grep 'memory_limit' /etc/httpd/conf.d/zabbix.conf php_value memory_limit 512M #默认128M

3.7总结

此处笔者提供一份配置文件，其中的参数数值可供大家修改

 # This is a configuration file for Zabbix server daemon

 # To get more information about Zabbix, visit http://www.zabbix.com

 ############ GENERAL PARAMETERS #################

 ### Option: ListenPort

 #    Listen port for trapper.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:服务端监听端口用于接收二级代理或直连AGENT的采集数据

 # ListenPort=

 ### Option: SourceIP

 #    Source IP address for outgoing connections.

 #

 # Mandatory: no

 # Default:

 #说明：服务端监听IP，建议指定

 # SourceIP=

 ### Option: LogType

 #    Specifies where log messages are written to:

 #        system  - syslog

 #        file    - file specified with LogFile parameter

 #        console - standard output

 #

 # Mandatory: no

 # Default:

 # LogType=file

 ### Option: LogFile

 #    Log file name for LogType 'file' parameter.

 #

 # Mandatory: no

 # Default:

 # LogFile=

 #说明：zabbix服务端日志路径，视具体情况指定

 LogFile=/tmp/zabbix_server.log

 ### Option: LogFileSize

 #    Maximum size of log file in MB.

 #     - disable automatic log rotation.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：日志达到多少M里就轮转；若此参数值为0时，则不轮转，日志将不断变大，建议设置成轮转

 LogFileSize=

 ### Option: DebugLevel

 #   Specifies debug level:

 #    - basic information about starting and stopping of Zabbix processes

 #    - critical information  灾难日志，日志量较少

 #    - error information  错误级别，日志量大于CRITICAL级别

 #    - warnings    告警级别，日志量大于ERROR级别

 #    - for debugging (produces lots of information)调试级别，日志量大于WARNING

 #    - extended debugging (produces even more information)

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：日志级别0~，单位时间内生成日志的量不断增大

 DebugLevel=

 ### Option: PidFile

 #    Name of PID file.

 #

 # Mandatory: no

 # Default:

 #说明：zabbix服务端程序PID路径

 PidFile=/tmp/zabbix_server.pid

 ### Option: DBHost

 #    Database host name.

 #    If set to localhost, socket is used for MySQL.

 #    If set to empty string, socket is used for PostgreSQL.

 #

 # Mandatory: no

 # Default:

 #说明：指定数据库信息，对于mysql，若设置为localhost则mysql用SOCKET来连接(需配合参数 DBSocket 使用)，否则用IP连接；若DHHOST值为空，则默认连接PostgreSQL

 # DBHost=localhost

 DBHost=

 ### Option: DBName

 #    Database name.

 #    For SQLite3 path to database file must be provided. DBUser and DBPassword are ignored.

 #

 # Mandatory: yes

 # Default:

 # DBName=

 #说明：服务端连接数据库的库名

 DBName=

 ### Option: DBSchema

 #    Schema name. Used for IBM DB2 and PostgreSQL.

 #

 # Mandatory: no

 # Default:

 #说明：专门用于 IBM DB2数据库的连接信息

 # DBSchema=

 ### Option: DBUser

 #    Database user. Ignored for SQLite.

 #

 # Mandatory: no

 # Default:

 #说明：连接数据库的用户

 # DBUser=

 DBUser=

 ### Option: DBPassword

 #    Database password. Ignored for SQLite.

 #    Comment this line if no password is used.

 #

 # Mandatory: no

 # Default:

 #说明：连接数据库的密码

 DBPassword=

 ### Option: DBSocket

 #    Path to MySQL socket.

 #

 # Mandatory: no

 # Default:

 #说明：指定MYSQL的SOCK连接路径

 DBSocket=/tmp/mysql.sock

 ### Option: DBPort

 #    Database port when not using local socket. Ignored for SQLite.

 #

 # Mandatory: no

 # Range: -

 # Default (for MySQL):

 #说明：指定连接数据库的端口，默认3306

 DBPort=

 ############ ADVANCED PARAMETERS ################

 #高级参数

 ### Option: StartPollers

 #    Number of pre-forked instances of pollers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明;初始化时，启动子进程数量，数量越多，则服务端吞吐能力越强，对系统资源消耗越大

 StartPollers=

 ### Option: StartIPMIPollers

 #    Number of pre-forked instances of IPMI pollers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #

 #说明:主要用于IPmi技术用于获取硬件状态场景。若无相关监控项，建议设置为0

 # StartIPMIPollers=

 ### Option: StartPollersUnreachable

 #    Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).

 #    At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers

 #    are started.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：默认情况下，ZABBIX会启用指定进程用于探测某些不可达主机的（含IPMI场景）；若使用场景中含有代理端，建议保持默认；若直接agent较多，可视具体情况调整

 StartPollersUnreachable=

 ### Option: StartTrappers

 #    Number of pre-forked instances of trappers.

 #    Trappers accept incoming connections from Zabbix sender, active agents and active proxies.

 #    At least one trapper process must be running to display server availability and view queue

 #    in the frontend.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：用于设置诸如SNMP STRAPPER场景提交来的数据的接收进程数，若客户机SNMP TRAPPER技术较多，建议加大此参数值

 StartTrappers=

 ### Option: StartPingers

 #    Number of pre-forked instances of ICMP pingers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：用于设置启用icmp协议PING主机方式启动线程数量，若单台代理所管理机器超过500台，建议加大此数值

 # StartPingers=

 ### Option: StartDiscoverers

 #    Number of pre-forked instances of discoverers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：用于设置自动发现主机的线程数量，若单台代理所管理机器超过500台，可以考虑加大此数值（仅适用于直接AGENT场景）

 StartDiscoverers=

 ### Option: StartHTTPPollers

 #    Number of pre-forked instances of HTTP pollers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：用于设置WEB拨测监控线程数，可视具体情况增加或减少此数值。

 # StartHTTPPollers=

 ### Option: StartTimers

 #    Number of pre-forked instances of timers.

 #    Timers process time-based trigger functions and maintenance periods.

 #    Only the first timer process handles the maintenance periods.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：各实例计时器数量，主要用于触发器，标有维护标识的主机，但只第一个计时器用于计算维护标识主机。

 # StartTimers=

 ### Option: StartEscalators

 #    Number of pre-forked instances of escalators.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：用于处理动作中的步骤的进程，zabbix动作较多时建议调大。

 StartEscalators=

 ### Option: JavaGateway

 #    IP address (or hostname) of Zabbix Java gateway.

 #    Only required if Java pollers are started.

 #

 # Mandatory: no

 # Default:

 #说明：JAVAGATEWAY 场景下使用

 JavaGateway=10.238.0.180

 ### Option: JavaGatewayPort

 #    Port that Zabbix Java gateway listens on.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：JAVAGATEWAY 场景下使用

 JavaGatewayPort=

 ### Option: StartJavaPollers

 #    Number of pre-forked instances of Java pollers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：JAVAGATEWAY 场景下使用

 StartJavaPollers=

 ### Option: StartVMwareCollectors

 #    Number of pre-forked vmware collector instances.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：用于设置监控VMWARE Esxi主机实例时使用，若为0则不启用，若要监控ESXI主机，此值最少为1 ；视监控ESXI数量设置对应数值

 # StartVMwareCollectors=

 ### Option: VMwareFrequency

 #    How often Zabbix will connect to VMware service to obtain a new data.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：代理端访问 VMWARE service的频率，单位:秒

 # VMwareFrequency=

 ### Option: VMwarePerfFrequency

 #    How often Zabbix will connect to VMware service to obtain performance data.

 #

 # Mandatory: no

 # Range: -

 # Default:

 # VMwarePerfFrequency=

 ### Option: VMwareCacheSize

 #    Size of VMware cache, in bytes.

 #    Shared memory size for storing VMware data.

 #    Only used if VMware collectors are started.

 #

 # Mandatory: no

 # Range: 256K-2G

 # Default:

 #说明：划出多少共享内存用于存储VMWARE数据

 VMwareCacheSize=256M

 ### Option: VMwareTimeout

 #    Specifies how many seconds vmware collector waits for response from VMware service.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：等待VMWare返回数据的最长时间

 VMwareTimeout=

 ### Option: SNMPTrapperFile

 #    Temporary file used for passing data from SNMP trap daemon to the server.

 #    Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.

 #

 # Mandatory: no

 # Default:

 #说明：指定SNMP TRAPPER 时的临时文件，用于代理端启用SNMP TRAPPER功能时使用

 # SNMPTrapperFile=/tmp/zabbix_traps.tmp

 ### Option: StartSNMPTrapper

 #    If , SNMP trapper process is started.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：是否启用 snmptrapper功能 ，默认不启用=，启用=（配合参数SNMPTrapperFile使用）

 # StartSNMPTrapper=

 ### Option: ListenIP

 #    List of comma delimited IP addresses that the trapper should listen on.

 #    Trapper will listen on all network interfaces if this parameter is missing.

 #

 # Mandatory: no

 # Default:

 #说明：启用SNMPTRAPPER里 ，接收端监听的IP，此参数与StartSNMPTrapper，SNMPTrapperFile 联合使用

 # ListenIP=0.0.0.0

 ListenIP=10.238.0.180

 ### Option: HousekeepingFrequency

 #    How often Zabbix will perform housekeeping procedure (in hours).

 #    Housekeeping is removing outdated information from the database.

 #    To prevent Housekeeper from being overloaded, no more than  times HousekeepingFrequency

 #    hours of outdated information are deleted in one housekeeping cycle, for each item.

 #    To lower load on server startup housekeeping is postponed for  minutes after server start.

 #    With HousekeepingFrequency= the housekeeper can be only executed using the runtime control option.

 #    In this case the period of outdated information deleted in one housekeeping cycle is  times the

 #    period since the last housekeeping cycle, but not less than  hours and not greater than  days.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：多少小时清理一次代理端数据库的 history, alert, and alarms，以保持代理端数据库轻便，建议保持默认

 HousekeepingFrequency=

 ### Option: MaxHousekeeperDelete

 #    The table "housekeeper" contains "tasks" for housekeeping procedure in the format:

 #    [housekeeperid], [tablename], [field], [value].

 #    No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])

 #    will be deleted per one task in one housekeeping cycle.

 #    SQLite3 does not use this parameter, deletes all corresponding rows without a limit.

 #    If set to  then no limit is used at all. In this case you must know what you are doing!

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:每个HouseKeeper任务删除的最大记录数，1.8.2开始支持

 MaxHousekeeperDelete=

 ### Option: SenderFrequency

 #    How often Zabbix will try to send unsent alerts (in seconds).

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:多少秒后重试发送失败的报警信息

 SenderFrequency=

 ### Option: CacheSize

 #    Size of configuration cache, in bytes.

 #    Shared memory size for storing host, item and trigger data.

 #

 # Mandatory: no

 # Range: 128K-8G

 # Default:

 #说明;zabbix初始化时占用多少系统共享内存用于存储配置信息，HOST,ITEM,TRIGGER数据，视监控主机数量和监控项调整，建议调整到32M或者更大

 CacheSize=8G

 ### Option: CacheUpdateFrequency

 #    How often Zabbix will perform update of configuration cache, in seconds.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：zabbix更新操作系统CACHE频率，若管理页面操作不频繁，可以考虑加大参数值

 CacheUpdateFrequency=

 ### Option: StartDBSyncers

 #    Number of pre-forked instances of DB Syncers.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:将采集数据从CACHE同步到数据库线程数量，视数据库服务器I/O繁忙情况，和数据库写能力调整。数值越大，写能力越强。对数据库服务器I/O压力越大。

 StartDBSyncers=

 ### Option: HistoryCacheSize

 #    Size of history cache, in bytes.

 #    Shared memory size for storing history data.

 #

 # Mandatory: no

 # Range: 128K-2G

 # Default:

 #说明：用于设置划分多少系统共享内存用于存储采集的历史数据，此数值越大，数据库读压力越小

 HistoryCacheSize=2048M

 ### Option: HistoryIndexCacheSize

 #    Size of history index cache, in bytes.

 #    Shared memory size for indexing history cache.

 #

 # Mandatory: no

 # Range: 128K-2G

 # Default:

 #说明：3.0.0开始支持，历史索引大小，一个监控项需要100bytes来存储

 HistoryIndexCacheSize=2048M

 ### Option: TrendCacheSize

 #    Size of trend cache, in bytes.

 #    Shared memory size for storing trends data.

 #

 # Mandatory: no

 # Range: 128K-2G

 # Default:

 #说明：用于设置划分多少系统共享内存用于存储计算出来的趋势数据，此参数值从一定程度上可影响数据库读压力

 TrendCacheSize=512M

 ### Option: ValueCacheSize

 #    Size of history value cache, in bytes.

 #    Shared memory size for caching item history data requests.

 #    Setting to  disables value cache.

 #

 # Mandatory: no

 # Range: ,128K-64G

 # Default:

 #说明：划出系统多少共享内存用于已请求的存储监控项信息，若监控项较多，建议加大此数值

 ValueCacheSize=16G

 ### Option: Timeout

 #    Specifies how long we wait for agent, SNMP device or external check (in seconds).

 #

 # Mandatory: no

 # Range: -

 # Default:

 # Timeout=

 #说明：与AGNET\SNMP设备和其它外部设备通信超时设置，单位为秒；若采集数据不完整或网络繁忙，或从管理页面发现客户端状态变化频繁，可以考虑加大此数值。注意若此数值加大，应该考虑参数 StartPollers 是否有相应加大的必要。

 Timeout=

 ### Option: TrapperTimeout

 #    Specifies how many seconds trapper may spend processing new data.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：启用 trapper功能，用于进程等待超时设置。根据需要调整

 TrapperTimeout=

 ### Option: UnreachablePeriod

 #    After how many seconds of unreachability treat a host as unavailable.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：当AGNET端处于不可用状态下，间隔多少秒后，尝试重新连接。建议根据具体情况设置。注意，若此数值过小，右agent端业务系统繁忙时，有可能造成报警信息误报

 # UnreachablePeriod=

 ### Option: UnavailableDelay

 #    How often host is checked for availability during the unavailability period, in seconds.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:当AGENT端处于可用状态下，间隔多少秒后，进行状态检查。若出现可正常采集数据，但管理页面AGENT状态不正常；若在网络，端口等均通畅情况下，AGENT状态仍不正常，可以考虑加大此数值

 # UnavailableDelay=

 ### Option: UnreachableDelay

 #    How often host is checked for availability during the unreachability period, in seconds.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：当agent端处于不可达状态下，延迟多少秒后，进行重新尝试，建议保持默认，在AGENT接入调试阶段，可考虑减少此数值

 # UnreachableDelay=

 ### Option: AlertScriptsPath

 #    Full path to location of custom alert scripts.

 #    Default depends on compilation options.

 #

 # Mandatory: no

 # Default:

 #说明：监控报警脚本路径，非研发人员不建议修改此参数值

 # AlertScriptsPath=${datadir}/zabbix/alertscripts

 AlertScriptsPath=/home/zabbix/bin

 ### Option: ExternalScripts

 #    Full path to location of external scripts.

 #    Default depends on compilation options.

 #

 # Mandatory: no

 # Default:

 #说明：自定义脚本存储路径，非研发人员不建议修改此参数值

 # ExternalScripts=${datadir}/zabbix/externalscripts

 ### Option: FpingLocation

 #    Location of fping.

 #    Make sure that fping binary has root ownership and SUID flag set.

 #

 # Mandatory: no

 # Default:

 #说明：IPv4 FPING命令路径，仅ROOT可用。注意使用此命令时，应该确认此命令是否存在

 FpingLocation=/usr/sbin/fping

 ### Option: Fping6Location

 #    Location of fping6.

 #    Make sure that fping6 binary has root ownership and SUID flag set.

 #    Make empty if your fping utility is capable to process IPv6 addresses.

 #

 # Mandatory: no

 # Default:

 #说明：IPv6 FPING命令路径，仅ROOT可用。注意使用此命令时，应该确认此命令是否存在

 # Fping6Location=/usr/sbin/fping6

 ### Option: SSHKeyLocation

 #    Location of public and private keys for SSH checks and actions.

 #

 # Mandatory: no

 # Default:

 #说明：在服务端需要SSH到AGENT端且采用用KEY验证方式时使用。非研发人员，不建议修改或设置

 # SSHKeyLocation=

 ### Option: LogSlowQueries

 #    How long a database query may take before being logged (in milliseconds).

 #    Only works if DebugLevel set to ,  or .

 #     - don't log slow queries.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:用于服务端数据库慢查询功能，单位是毫秒；1毫秒=.001秒，若有服务端数据库监控慢查询的需求，可以视具体情况调整此数。

 # LogSlowQueries=

 LogSlowQueries=

 ### Option: TmpDir

 #    Temporary directory.

 #

 # Mandatory: no

 # Default:

 #说明：zabbix服务端工作的临时目录

 # TmpDir=/tmp

 ### Option: StartProxyPollers

 #    Number of pre-forked instances of pollers for passive proxies.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明:启用多少子进程与代理端通信，若代理端较多可考虑加大此数值

 # StartProxyPollers=

 ### Option: ProxyConfigFrequency

 #    How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.

 #    This parameter is used only for proxies in the passive mode.

 #

 # Mandatory: no

 # Range: -**

 # Default:

 #说明：zabbix服务端将配置文件数据同步到代理端的频率，仅适用于代理端为被动模式情况下

 # ProxyConfigFrequency=

 ### Option: ProxyDataFrequency

 #    How often Zabbix Server requests history data from a Zabbix Proxy in seconds.

 #    This parameter is used only for proxies in the passive mode.

 #

 # Mandatory: no

 # Range: -

 # Default:

 #说明：zabbix服务端请求代理端采集的数据的频率，仅适用代理端为被动模式情况下

 # ProxyDataFrequency=

 ### Option: AllowRoot

 #    Allow the server to run as 'root'. If disabled and the server is started by 'root', the server

 #    will try to switch to the user specified by the User configuration option instead.

 #    Has no effect if started under a regular user.

 #    - do not allow 不允许

 #    - allow 允许

 #

 # Mandatory: no

 # Default:

 #说明：是否允许以root身份运行服务端

 AllowRoot=

 ### Option: User

 #    Drop privileges to a specific, existing user on the system.

 #    Only has effect if run as 'root' and AllowRoot is disabled.

 #

 # Mandatory: no

 # Default:

 #说明：非root运行的账号

 # User=zabbix

 ### Option: Include

 #    You may include individual files or all files in a directory in the configuration file.

 #    Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.

 #

 # Mandatory: no

 # Default:

 #说明：在一些情况下，软件的参数配置文件很长，为了方便管理，将配置文件切割成N个配置文件，但为了主配置参数文件的简洁，便会启用INCLUDE参数，以方便程序读取指定目录下的所有配置文件

 # Include=

 # Include=/usr/local/etc/zabbix_server.general.conf

 # Include=/usr/local/etc/zabbix_server.conf.d/

 # Include=/usr/local/etc/zabbix_server.conf.d/*.conf

 ### Option: SSLCertLocation

 #    Location of SSL client certificates.

 #    This parameter is used only in web monitoring.

 #

 # Mandatory: no

 # Default:

 #说明：SSL客户端认证文件，2.4开始支持

 # SSLCertLocation=${datadir}/zabbix/ssl/certs

 ### Option: SSLKeyLocation

 #    Location of private keys for SSL client certificates.

 #    This parameter is used only in web monitoring.

 #

 # Mandatory: no

 # Default:

 #说明：SSL私钥文件目录，2.4开始支持

 # SSLKeyLocation=${datadir}/zabbix/ssl/keys

 ### Option: SSLCALocation

 #    Override the location of certificate authority (CA) files for SSL server certificate verification.

 #    If not set, system-wide directory will be used.

 #    This parameter is used only in web monitoring and SMTP authentication.

 #

 # Mandatory: no

 # Default:

 #说明：SSL CA钥文件目录，2.4开始支持

 # SSLCALocation=

 ####### LOADABLE MODULES #######

 #可加载的模块

 ### Option: LoadModulePath

 #    Full path to location of server modules.

 #    Default depends on compilation options.

 #

 # Mandatory: no

 # Default:

 #指定本地模块路径，非研发人员不建议修改

 # LoadModulePath=${libdir}/modules

 ### Option: LoadModule

 #    Module to load at server startup. Modules are used to extend functionality of the server.

 #    Format: LoadModule=<module.so>

 #    The modules must be located in directory specified by LoadModulePath.

 #    It is allowed to include multiple LoadModule parameters.

 #

 # Mandatory: no

 # Default:

 #指定本地模块路径，非研发人员不建议修改

 # LoadModule=

 ####### TLS-RELATED PARAMETERS #######

 #TLS 相关参数

 ### Option: TLSCAFile

 #    Full pathname of a file containing the top-level CA(s) certificates for

 #    peer certificate verification.

 #

 # Mandatory: no

 # Default:

 #说明：TLS证书文件

 # TLSCAFile=

 ### Option: TLSCRLFile

 #    Full pathname of a file containing revoked certificates.

 #

 # Mandatory: no

 # Default:

 #说明：TLS证书文件

 # TLSCRLFile=

 ### Option: TLSCertFile

 #    Full pathname of a file containing the server certificate or certificate chain.

 #

 # Mandatory: no

 # Default:

 #说明：TLS证书文件

 # TLSCertFile=

 ### Option: TLSKeyFile

 #    Full pathname of a file containing the server private key.

 #

 # Mandatory: no

 # Default:

 #说明：TLS证书文件

 # TLSKeyFile= 

 #参考配置文件见https://www.boheyan.cn/zabbix.htm

此笔记是本人学习摘记整理而成，此为初稿(尚有诸多不完善之处)，原创作品允许转载，转载时请务必以超链接形式标明文章原始出处，作者信息和本声明，否则将追究法律责任。http://www.cnblogs.com/bananaaa/

Zabbix服务网页报错汇总的更多相关文章

  1. Ubuntu操作系统编译安装zabbix报错汇总

    Ubuntu操作系统编译安装zabbix报错汇总 作者:尹正杰 版权声明:原创作品,谢绝转载!否则将追究法律责任. 一.报错提示:"configure: error: MySQL libra ...

  2. selenium报错汇总

    selenium报错汇总 报错:[error] Could not connect to Selenium Server. Have you started the Selenium Server y ...

  3. Ambari集成Kerberos报错汇总

    Ambari集成Kerberos报错汇总 作者:尹正杰 版权声明:原创作品,谢绝转载!否则将追究法律责任. 一.查看报错的配置信息步骤 1>.点击Test Kerberos Client,查看相 ...

  4. Python_环境部署及报错汇总（0）

    一.安装Anaconda Anaconda是一个开源的包.环境管理器,可以用于在同一个机器上安装不同版本的软件包及其依赖,并能够在不同的环境之间切换. Anaconda包括Conda.Python以及 ...

  5. android手机访问app网页报错：net::ERR_PROXY_CONNECTION_FAILED

    手机访问网页报错:net::ERR_PROXY_CONNECTION_FAILED 手机访问app中嵌入的html网页报错: net::ERR_PROXY_CONNECTION_FAILED 原来是手 ...

  6. zabbix客户端日志报错no active checks on server [192.168.3.108:10051]: host [192.168.3.108] not found

    zabbix客户端日志报错: 45647:20160808:220507.717 no active checks on server [192.168.3.108:10051]: host [192 ...

  7. zabbix共享内存报错cannot create semaphore set

    zabbix共享内存报错 cannot open log: cannot create semaphore set: [28] No space left on device 报错原因: kernel ...

  8. gitblit在windows10上的安装及服务启动报错处理

    折腾一下午算是装好了,心情不错决定分享一下.安装步骤大同小异网上都有,主要是Failed creating java 这个报错,百度出来的没有一个能给我解决的,摸索半天找出一个自己的方式.为报错而来的 ...

  9. ElementUI——报错汇总

    前言 elementUI的报错汇总 错误 please transfer a valid prop path to form item! vue.esm.js?c5de:628 [Vue warn]: ...

随机推荐

  1. 在SQL中用正则表达式替换html标签（2）

    由于数据库的一个表字段中多包含html标签,现在需要修改数据库的字段把html标签都替换掉.当然我可以通过写一个程序去修改,那毕竟有点麻烦.直接在查询分析器中执行,但是MS SQL Server并没有 ...

  2. asp.net中kindeditor配置

    <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>KindEditor< ...

  3. checkValidity-表达验证方法。

    调用该方法,可以显示对表单元素进行有效验证,返回值是boolean. 代码如下: <!DOCTYPE html> <html> <head> <meta ch ...

  4. MyBatis开发中解决返回字段不全的问题

    场景重现: mybatis 在查询的时候,可以返回Map,但是一旦这个字段为空(null)的时候,map里就没有了.我用的是mysql数据库,除了在查询语句上做ifnull判断给它默认值外,有没的别的 ...

  5. db2备份还原

    还原步骤:创建好数据库后进入该数据库 .restore db TSMESDB from D:\ICSS\dbData on D:\ICSS\dbData  into TSMESDB redirect. ...

  6. 继承“HibernateDaoSupport”后，报“The hierarchy of the type AccoutDaoImpl is inconsistent”的解决方案

    解决办法: 今天写了一段很简单的代码,Eclipse竟然报错 import org.springframework.jdbc.core.support.JdbcDaoSupport; import c ...

  7. 快速排序算法分析--C++版

    快速排序由于排序效率在同为O(N*logN)的几种排序方法中效率较高,因此经常被采用,再加上快速排序思想----分治法也确实实用,因此很多软件公司的笔试面试喜欢考这个. 快速排序是C.R.A.Hoar ...

  8. 如何快速部署 Prometheus？- 每天5分钟玩转 Docker 容器技术（85）

    上一节介绍了 Prometheus 的核心,多维数据模型.本节演示如何快速搭建 Prometheus 监控系统. 环境说明 我们将通过 Prometheus 监控两台 Docker Host:192. ...

  9. Debian GNU/Linux 8.4 (jessie)编译安装php.md

    编译遇到的问题很多.网上的文章往往是记录遇到的报错,贴上对应的解决. 而实际的环境,如操作系统,安装的软件必然有差异,所以,更重要的是,如何找到解决方法(不担保按步骤做可以编译成功),并将过程自动化. ...

  10. tomcat启动报错Several ports (8080, 8009) required by Tomcat v6.0

    tomcat启动报错 如下图: 问题:8080.8009端口已经被占用. 解决办法: 1.在命令提示符下,输入netstat -aon | findstr 8080 2.继续输入taskkill -F ...