zabbix_server表面启动成功，但是没有进程

叁歲伎倆 2022-05-21 10:49 302阅读 0赞

## [zabbix\_server表面启动成功，但是没有进程][zabbix_server] ##

\[root@iZ25m1box8cZ zabbix\]\# /etc/init.d/zabbix\_server start

Starting zabbix\_server (via systemctl):                    \[  **OK**  \]

\[root@iZ25m1box8cZ ~\]\# ps -ef|grep zabbix

root     20125 19728  0 10:22 pts/3    00:00:00 grep --color=auto zabbix

表面上zabbix\_server已经启动了，但是并没有发现zabbix\_server进程

**解决方法：查看服务状态报告**

\[root@iZ25m1box8cZ ~\]\# **/etc/init.d/zabbix\_server status**

● zabbix\_server.service - SYSV: Starts and stops Zabbix Server using chkconfig

Loaded: loaded (/etc/rc.d/init.d/zabbix\_server; bad; vendor preset: disabled)

Active: active (exited) since Mon 2017-02-27 16:27:22 CST; 18h ago

Docs: man:systemd-sysv-gene rator(8)

Feb 27 16:27:22 iZ25m1box8cZ systemd\[1\]: Starting SYSV: Starts and stops Zabbix Server using chkconfig...

Feb 27 16:27:22 iZ25m1box8cZ zabbix\_server\[6313\]: **Starting zabbix\_server:  /usr/local/zabbix//sbin/zabbix\_server: error while loading shared libraries: libmysqlclient.so.20: ca...or directory**

Feb 27 16:27:22 iZ25m1box8cZ zabbix\_server\[6313\]: \[FAILED\]

Feb 27 16:27:22 iZ25m1box8cZ systemd\[1\]: Started SYSV: Starts and stops Zabbix Server using chkconfig.

Hint: Some lines were ellipsized, use -l to show in full.

对应解决：

\[root@iZ25m1box8cZ mysql\]\# ls /usr/local/mysql/lib/

libmysqlclient.a  libmysqlclient.so  libmysqlclient.so.20  libmysqlclient.so.20.3.3  libmysqld.a  libmysqld-debug.a  libmysqlservices.a  mecab  pkgconfig  plugin

\[root@iZ25m1box8cZ mysql\]\# **ln -s /usr/local/mysql/lib/libmysqlclient.so.20 /usr/lib64/**

重启zabbix\_server:

\[root@iZ25m1box8cZ zabbix\]\# **/etc/init.d/zabbix\_server restart**

再次查看服务状态报告：

\[root@iZ25m1box8cZ ~\]\# /etc/init.d/zabbix\_server status

● zabbix\_server.service - SYSV: Starts and stops Zabbix Server using chkconfig

Loaded: loaded (/etc/rc.d/init.d/zabbix\_server; bad; vendor preset: disabled)

Active: active (exited) since Tue 2017-02-28 11:25:07 CST; 5s ago

Docs: man:systemd-sysv-generator(8)

Process: 22235 ExecStop=/etc/rc.d/init.d/zabbix\_server stop (code=exited, status=0/SUCCESS)

Process: 22249 ExecStart=/etc/rc.d/init.d/zabbix\_server start (code=exited, status=0/SUCCESS)

Feb 28 11:25:07 iZ25m1box8cZ systemd\[1\]: Starting SYSV: Starts and stops Zabbix Server using chkconfig...

Feb 28 11:25:07 iZ25m1box8cZ zabbix\_server\[22249\]: **Starting zabbix\_server:  zabbix\_server \[22256\]: unknown parameter \[alertScriptsPath\] in config file \[/usr/local/zabbix/etc/zab...\], line 100**

Feb 28 11:25:07 iZ25m1box8cZ zabbix\_server\[22249\]: \[FAILED\]

Feb 28 11:25:07 iZ25m1box8cZ systemd\[1\]: Started SYSV: Starts and stops Zabbix Server using chkconfig.

Hint: Some lines were ellipsized, use -l to show in full.

即去修改 /usr/local/zabbix/etc/zabbix\_server.conf中的 **AalertScriptsPath**就行了。

最后再次重启zabbix\_server：

\[root@iZ25m1box8cZ zabbix\]\# **/etc/init.d/zabbix\_server restart**

Restarting zabbix\_server (via systemctl):                  \[  OK  \]

\[root@iZ25m1box8cZ ~\]\# **/etc/init.d/zabbix\_server status**

● zabbix\_server.service - SYSV: Starts and stops Zabbix Server using chkconfig

Loaded: loaded (/etc/rc.d/init.d/zabbix\_server; bad; vendor preset: disabled)

Active: active (running) since Tue 2017-02-28 11:25:40 CST; 4s ago

Docs: man:systemd-sysv-generator(8)

Process: 22293 ExecStop=/etc/rc.d/init.d/zabbix\_server stop (code=exited, status=0/SUCCESS)

Process: 22307 ExecStart=/etc/rc.d/init.d/zabbix\_server start (code=exited, status=0/SUCCESS)

CGroup: /system.slice/zabbix\_server.service

├─22316 /usr/local/zabbix/sbin/zabbix\_server

├─22318 /usr/local/zabbix/sbin/zabbix\_server: configuration syncer \[waiting 60 sec for processes\]

├─22319 /usr/local/zabbix/sbin/zabbix\_server: db watchdog \[synced alerts config in 0.001065 sec, idle 60 sec\]

├─22320 /usr/local/zabbix/sbin/zabbix\_server: poller \#1 \[got 0 values in 0.000017 sec, idle 5 sec\]

├─22321 /usr/local/zabbix/sbin/zabbix\_server: poller \#2 \[got 0 values in 0.000020 sec, idle 5 sec\]

├─22322 /usr/local/zabbix/sbin/zabbix\_server: poller \#3 \[got 0 values in 0.000024 sec, idle 5 sec\]

├─22323 /usr/local/zabbix/sbin/zabbix\_server: poller \#4 \[got 0 values in 0.000019 sec, idle 5 sec\]

├─22324 /usr/local/zabbix/sbin/zabbix\_server: poller \#5 \[got 0 values in 0.000025 sec, idle 5 sec\]

├─22325 /usr/local/zabbix/sbin/zabbix\_server: unreachable poller \#1 \[got 0 values in 0.000020 sec, idle 5 sec\]

├─22326 /usr/local/zabbix/sbin/zabbix\_server: trapper \#1 \[processed data in 0.000000 sec, waiting for connection\]

├─22327 /usr/local/zabbix/sbin/zabbix\_server: trapper \#2 \[processed data in 0.000000 sec, waiting for connection\]

├─22328 /usr/local/zabbix/sbin/zabbix\_server: trapper \#3 \[processed data in 0.000000 sec, waiting for connection\]

├─22329 /usr/local/zabbix/sbin/zabbix\_server: trapper \#4 \[processed data in 0.000000 sec, waiting for connection\]

├─22330 /usr/local/zabbix/sbin/zabbix\_server: trapper \#5 \[processed data in 0.000000 sec, waiting for connection\]

├─22331 /usr/local/zabbix/sbin/zabbix\_server: icmp pinger \#1 \[got 0 values in 0.000024 sec, idle 5 sec\]

├─22332 /usr/local/zabbix/sbin/zabbix\_server: alerter \[sent alerts: 0 success, 0 fail in 0.000555 sec, idle 30 sec\]

├─22333 /usr/local/zabbix/sbin/zabbix\_server: housekeeper \[deleted 0 hist/trends, 0 items, 0 events, 0 sessions, 0 alarms, 0 audit items in 0.207611

├─22334 /usr/local/zabbix/sbin/zabbix\_server: timer \#1 \[processed 0 triggers, 0 events in 0.000000 sec, 0 maintenances in 0.000000 sec, idle 20 sec\]

├─22335 /usr/local/zabbix/sbin/zabbix\_server: http poller \#1 \[got 0 values in 0.000369 sec, idle 5 sec\]

├─22336 /usr/local/zabbix/sbin/zabbix\_server: discoverer \#1 \[processed 0 rules in 0.000411 sec, idle 60 sec\]

├─22337 /usr/local/zabbix/sbin/zabbix\_server: history syncer \#1 \[synced 0 items in 0.000011 sec, idle 5 sec\]

├─22338 /usr/local/zabbix/sbin/zabbix\_server: history syncer \#2 \[synced 0 items in 0.000008 sec, idle 5 sec\]

├─22339 /usr/local/zabbix/sbin/zabbix\_server: history syncer \#3 \[synced 0 items in 0.000008 sec, idle 5 sec\]

├─22340 /usr/local/zabbix/sbin/zabbix\_server: history syncer \#4 \[synced 0 items in 0.000010 sec, idle 5 sec\]

├─22341 /usr/local/zabbix/sbin/zabbix\_server: escalator \[processed 0 escalations in 0.000373 sec, idle 3 sec\]

├─22342 /usr/local/zabbix/sbin/zabbix\_server: proxy poller \#1 \[exchanged data with 0 proxies in 0.000017 sec, idle 5 sec\]

└─22343 /usr/local/zabbix/sbin/zabbix\_server: self-monitoring \[processed data in 0.000004 sec, idle 1 sec\]

Feb 28 11:25:40 iZ25m1box8cZ systemd\[1\]: Starting SYSV: Starts and stops Zabbix Server using chkconfig...

Feb 28 11:25:40 iZ25m1box8cZ zabbix\_server\[22307\]: Starting zabbix\_server:  \[  OK  \]

Feb 28 11:25:40 iZ25m1box8cZ systemd\[1\]: Started SYSV: Starts and stops Zabbix Server using chkconfig.

--------------------

zabbix\_agentd也是现象也是同样，没有运行进程。

检测方法:  agentd进程直接后面跟配置文件运行

\[root@iZ25h0fi74kZ ~\]\# **/data/zabbix/sbin/zabbix\_agentd -c /data/zabbix/etc/zabbix\_agentd.conf**

[zabbix_server]: https://www.cnblogs.com/lizhi221/p/6814079.html

zabbix_server表面启动成功，但是没有进程

发表评论取消回复

还没有评论，来说两句吧...

相关阅读

相关 docker 镜像启动成功但是无法访问

相关已解决“docker容器启动MySQL创建成功了但是没有端口号以及没有启动”问题解决

相关 Hbase的Hmaster进程没有启动/Hbase进程启动不全

相关 JPA 执行save()方法成功但是没有插入数据库问题解决

相关 Xcode能编译运行成功，但是模拟器没有自启动（没有任何动静）

相关 tomat启动成功-但是应用没有启动成功

相关 jenkins部署本地项目,成功了但是项目没有启动

相关 zabbix_server表面启动成功，但是没有进程

相关 MySQL没有启动成功，没有报告任何错误

相关 logstach启动成功，但是同步mysql数据出错