这篇文章给大家介绍zabbix-server服务启动失败处理过程是怎么样的，内容非常详细，感兴趣的小伙伴们可以参考借鉴，希望对大家能有所帮助。
成都创新互联公司是一家集网站建设,玉林企业网站建设,玉林品牌网站建设,网站定制,玉林网站建设报价,网络营销,网络优化,玉林网站推广为一体的创新建站企业，帮助传统企业提升企业形象加强企业竞争力。可充分满足这一群体相比中小企业更为丰富、高端、多元的互联网需求。同时我们时刻保持专业、时尚、前沿，时刻以成就客户成长自我，坚持不断学习、思考、沉淀、净化自己，让我们为更多的企业打造出实用型网站。
在CentOS7x64 7.3.1611上测试部署Zabbix 3.0.9，到启动zabbix-server服务时报错：
6月 19 15:52:13 CentOS7x64 systemd[1]: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start.
6月 19 15:52:13 CentOS7x64 systemd[1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE
6月 19 15:52:24 CentOS7x64 systemd[1]: zabbix-server.service: control process exited, code=exited status=1
6月 19 15:52:24 CentOS7x64 systemd[1]: Unit zabbix-server.service entered failed state.
6月 19 15:52:24 CentOS7x64 systemd[1]: zabbix-server.service failed.
[root@CentOS7x64 ~]# getenforce
Disabled
[root@CentOS7x64 ~]#
这次执行启动命令没有报错提示，执行systemctl status zabbix-server.service和journalctl -xe也没有明显的错误原因提示。
[root@CentOS7x64 ~]# cd /var/log
[root@CentOS7x64 log]# ls
anaconda cups httpd pluto speech-dispatcher VBoxGuestAdditions-uninstall.log Xorg.9.log
audit dmesg lastlog pm-powersave.log spooler vmware-vmusr.log Xorg.9.log.old
boot.log dmesg.old libvirt ppp spooler-20170417 wpa_supplicant.log yum.log
btmp firewalld maillog qemu-ga tallylog wtmp yum.log-20170417
btmp-20170417 gdm maillog-20170417 sa tuned Xorg.0.log zabbix
chrony glusterfs messages samba vboxadd-install.log Xorg.0.log.old
cron grubby messages-20170417 secure vboxadd-install-x11.log Xorg.1.log
cron-20170417 grubby_prune_debug MySQLd.log secure-20170417 VBoxGuestAdditions.log Xorg.1.log.old
[root@CentOS7x64 log]# cd zabbix
[root@CentOS7x64 zabbix]# ls
zabbix_server.log
[root@CentOS7x64 zabbix]# ll
总用量 384
-rw-rw-r--. 1 zabbix zabbix 368295 6月 19 16:04 zabbix_server.log
[root@CentOS7x64 zabbix]# less zabbix_server.log
[root@CentOS7x64 zabbix]# tail -50 zabbix_server.log
4520:20170619:160624.303 ****** Enabled features ******
4520:20170619:160624.303 SNMP monitoring: YES
4520:20170619:160624.303 IPMI monitoring: YES
4520:20170619:160624.303 Web monitoring: YES
4520:20170619:160624.303 VMware monitoring: YES
4520:20170619:160624.303 SMTP authentication: YES
4520:20170619:160624.303 Jabber notifications: YES
4520:20170619:160624.303 Ez Texting notifications: YES
4520:20170619:160624.303 ODBC: YES
4520:20170619:160624.303 SSH2 support: YES
4520:20170619:160624.303 IPv6 support: YES
4520:20170619:160624.303 TLS support: YES
4520:20170619:160624.303 ******************************
4520:20170619:160624.303 using configuration file: /etc/zabbix/zabbix_server.conf
4520:20170619:160624.306 [Z3005] query failed: [1146] Table 'zabbix.users' doesn't exist [select userid from users limit 1]
4520:20170619:160624.306 cannot use database "zabbix": database is not a Zabbix database
4531:20170619:160634.563 Starting Zabbix Server. Zabbix 3.0.9 (revision 67444).
4531:20170619:160634.563 ****** Enabled features ******
4531:20170619:160634.563 SNMP monitoring: YES
4531:20170619:160634.563 IPMI monitoring: YES
4531:20170619:160634.563 Web monitoring: YES
4531:20170619:160634.563 VMware monitoring: YES
4531:20170619:160634.563 SMTP authentication: YES
4531:20170619:160634.563 Jabber notifications: YES
4531:20170619:160634.563 Ez Texting notifications: YES
4531:20170619:160634.563 ODBC: YES
4531:20170619:160634.563 SSH2 support: YES
4531:20170619:160634.563 IPv6 support: YES
4531:20170619:160634.563 TLS support: YES
4531:20170619:160634.563 ******************************
4531:20170619:160634.563 using configuration file: /etc/zabbix/zabbix_server.conf
4531:20170619:160634.567 [Z3005] query failed: [1146] Table 'zabbix.users' doesn't exist [select userid from users limit 1]
4531:20170619:160634.567 cannot use database "zabbix": database is not a Zabbix database
4536:20170619:160644.820 Starting Zabbix Server. Zabbix 3.0.9 (revision 67444).
4536:20170619:160644.820 ****** Enabled features ******
4536:20170619:160644.820 SNMP monitoring: YES
4536:20170619:160644.820 IPMI monitoring: YES
4536:20170619:160644.820 Web monitoring: YES
4536:20170619:160644.820 VMware monitoring: YES
4536:20170619:160644.820 SMTP authentication: YES
4536:20170619:160644.820 Jabber notifications: YES
4536:20170619:160644.820 Ez Texting notifications: YES
4536:20170619:160644.820 ODBC: YES
4536:20170619:160644.820 SSH2 support: YES
4536:20170619:160644.820 IPv6 support: YES
4536:20170619:160644.820 TLS support: YES
4536:20170619:160644.820 ******************************
4536:20170619:160644.820 using configuration file: /etc/zabbix/zabbix_server.conf
4536:20170619:160644.826 [Z3005] query failed: [1146] Table 'zabbix.users' doesn't exist [select userid from users limit 1]
4536:20170619:160644.826 cannot use database "zabbix": database is not a Zabbix database
[root@CentOS7x64 zabbix]#
看日志应该是Zabbix数据库配置不完整，zabbix.users表没有创建，即Zabbix数据库配置时建库建表等动作没有按照要求正常完成。
补充了相关操作后再试，zabbix-server服务启动正常了：
Zabbix管理页面能正常登陆并打开：
关于zabbix-server服务启动失败处理过程是怎么样的就分享到这里了，希望以上内容可以对大家有一定的帮助，可以学到更多知识。如果觉得文章不错，可以把它分享出去让更多的人看到。
