Details
-
Problem report
-
Status: Closed
-
Trivial
-
Resolution: Done
-
6.0.1
-
None
-
None
-
RHEL 8.5, running latest software (kernel 4.18.0-348.12.2.el8_5.x86_64)
Description
Steps to reproduce:
- Base install of RHEL8 on EC2
- yum update to latest software versions available.
- sudo rpm -Uvh https://repo.zabbix.com/zabbix/6.0/rhel/8/x86_64/zabbix-release-6.0-1.el8.noarch.rpm
- yum install zabbix-proxy-sqlite3
- Configure /etc/zabbix/zabbix_proxy.conf
- I have only updated Server, Hostname, and DBName
- Zabbix proxy fails to start and enters a fail loop
Result:
Per /var/log/zabbix/zabbix_proxy.log
2057:20220303:225659.557 Starting Zabbix Proxy (active) [itsm-test-zabbix6-proxy-rhel8]. Zabbix 6.0.1 (revision a80cb13868).
2057:20220303:225659.557 **** Enabled features ****
2057:20220303:225659.557 SNMP monitoring: YES
2057:20220303:225659.557 IPMI monitoring: YES
2057:20220303:225659.557 Web monitoring: YES
2057:20220303:225659.557 VMware monitoring: YES
2057:20220303:225659.557 ODBC: YES
2057:20220303:225659.557 SSH support: YES
2057:20220303:225659.557 IPv6 support: YES
2057:20220303:225659.557 TLS support: YES
2057:20220303:225659.557 **************************
2057:20220303:225659.557 using configuration file: /etc/zabbix/zabbix_proxy.conf
2057:20220303:225659.571 current database version (mandatory/optional): 06000000/06000000
2057:20220303:225659.571 required mandatory version: 06000000
2057:20220303:225659.574 proxy #0 started [main process]
2058:20220303:225659.575 proxy #1 started configuration syncer #1
2058:20220303:225704.086 cannot connect to RTC service: Cannot connect to service "rtc": [13] Permission denied.
2057:20220303:225704.087 One child process died (PID:2058,exitcode/signal:1). Exiting ...
2057:20220303:225704.583 Zabbix Proxy stopped. Zabbix 6.0.1 (revision a80cb13868).
Per sudo journalctl -xefu zabbix-proxy
Mar 03 22:57:30 itsm-test-zabbix6-proxy-rhel8 systemd[1]: zabbix-proxy.service: Service RestartSec=10s expired, scheduling restart.
Mar 03 22:57:30 itsm-test-zabbix6-proxy-rhel8 systemd[1]: zabbix-proxy.service: Scheduled restart job, restart counter is at 25.
– Subject: Automatic restarting of a unit has been scheduled
– Defined-By: systemd
– Support: https://access.redhat.com/support
–
– Automatic restarting of the unit zabbix-proxy.service has been scheduled, as the result for
– the configured Restart= setting for the unit.
Mar 03 22:57:30 itsm-test-zabbix6-proxy-rhel8 systemd[1]: Stopped Zabbix Proxy.
– Subject: Unit zabbix-proxy.service has finished shutting down
– Defined-By: systemd
– Support: https://access.redhat.com/support
–
– Unit zabbix-proxy.service has finished shutting down.
Mar 03 22:57:30 itsm-test-zabbix6-proxy-rhel8 systemd[1]: Starting Zabbix Proxy...
– Subject: Unit zabbix-proxy.service has begun start-up
– Defined-By: systemd
– Support: https://access.redhat.com/support
–
– Unit zabbix-proxy.service has begun starting up.
Mar 03 22:57:30 itsm-test-zabbix6-proxy-rhel8 systemd[1]: zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: No such file or directory
Mar 03 22:57:30 itsm-test-zabbix6-proxy-rhel8 systemd[1]: Started Zabbix Proxy.
– Subject: Unit zabbix-proxy.service has finished start-up
– Defined-By: systemd
– Support: https://access.redhat.com/support
–
– Unit zabbix-proxy.service has finished starting up.
–
– The start-up result is done.
Expected:
Zabbix proxy to start successfully