-
Incident report
-
Resolution: Fixed
-
Trivial
-
None
-
4.2.0
-
None
-
Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 52 (May 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019), Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020), Sprint 62 (Mar 2020), Sprint 63 (Apr 2020)
Steps to reproduce:
rpm -ivh zabbix-java-gateway-4.2.0-1.el12.x86_64.rpm systemctl start zabbix-java-gateway
Result:
# systemctl status zabbix-java-gateway.service zabbix-java-gateway.service Loaded: not-found (Reason: No such file or directory) Active: failed (Result: exit-code) since Wed 2019-04-17 10:30:07 UTC; 2h 51min ago Main PID: 2069 (code=exited, status=143) systemd[1]: Started Zabbix Server. zabbix-java-gateway[2069]: Running zabbix-java-gateway ... systemd[1]: Stopping Zabbix Server... systemd[1]: zabbix-java-gateway.service: main process exited, code=exited, status=143/n/a systemd[1]: Stopped Zabbix Server. systemd[1]: Unit zabbix-java-gateway.service entered failed state. systemd[1]: Stopped Zabbix Server.
Solution:
copying /usr/lib/systemd/system/zabbix-java-gateway.service file to /lib/systemd/system/zabbix-java-gateway.service
solves the problem.