Shulou(Shulou.com)06/01 Report--

This article introduces you how the zabbix-server service startup failure handling process is, the content is very detailed, interested friends can refer to, hope to be helpful to you.

When you test and deploy Zabbix 3.0.9 on CentOS7x64 7.3.1611, it is wrong to start the zabbix-server service:

June 19 15:52:13 CentOS7x64 systemd [1]: PID file / run/zabbix/zabbix_server.pid not readable (yet?) After start.

June 19 15:52:13 CentOS7x64 systemd [1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE

June 19 15:52:24 CentOS7x64 systemd [1]: zabbix-server.service: control process exited, code=exited status=1

June 19 15:52:24 CentOS7x64 systemd [1]: Unit zabbix-server.service entered failed state.

June 19 15:52:24 CentOS7x64 systemd [1]: zabbix-server.service failed.

[root@CentOS7x64 ~] # getenforce

Disabled

[root@CentOS7x64 ~] #

There is no error in executing the startup command, and there is no obvious reason for the error in the execution of systemctl status zabbix-server.service and 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

Total dosage 384

-rw-rw-r--. 1 zabbix zabbix 368295 June 19 16:04 zabbix_server.log

[root@CentOS7x64 zabbix] # less zabbix_server.log

[root@CentOS7x64 zabbix] # tail-50 zabbix_server.log

4520Rom 20170619RU 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

4520Rom 20170619RU 160624.303 * *

4520:20170619:160624.303 using configuration file: / etc/zabbix/zabbix_server.conf

4520 Table 20170619 zabbix.users' doesn't exist 160624.306 [Z3005] query failed: [1146] Table 'zabbix.users' doesn't exist [select userid from users limit 1]

4520 database is not a Zabbix database 20170619 database is not a Zabbix database 160624.306 cannot use database "zabbix"

4531:20170619:160634.563 Starting Zabbix Server. Zabbix 3.0.9 (revision 67444).

4531 20170619 Hua 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

4531Rd 20170619UR 160634.563 * *

4531:20170619:160634.563 using configuration file: / etc/zabbix/zabbix_server.conf

4531 Table 20170619 zabbix.users' doesn't exist 160634.567 [Z3005] query failed: [1146] Table 'zabbix.users' doesn't exist [select userid from users limit 1]

4531 database is not a Zabbix database 20170619 cannot use database 160634.567 "zabbix":

4536:20170619:160644.820 Starting Zabbix Server. Zabbix 3.0.9 (revision 67444).

4536RV 20170619RU 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

4536R 20170619R 160644.820 * *

4536:20170619:160644.820 using configuration file: / etc/zabbix/zabbix_server.conf

4536 Table 20170619 zabbix.users' doesn't exist 160644.826 [Z3005] query failed: [1146] Table 'zabbix.users' doesn't exist [select userid from users limit 1]

4536R 20170619 cannot use database 160644.826 "zabbix": database is not a Zabbix database

[root@CentOS7x64 zabbix] #

If you look at the log, it should be that the configuration of the Zabbix database is incomplete and the zabbix.users table is not created, that is, the actions such as building the database and building the table during the Zabbix database configuration have not been completed as required.

After adding the relevant operations, try again, and the zabbix-server service starts normally:

The Zabbix management page can log in and open normally:

About the zabbix-server service startup failure handling process is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.