background info:
ubuntu 20.04 LTS virtual machine
running inside Hyper-V on windows 11 pro
zabbix 5.4.1
PostgresSQL
Apache2
I have a machine on the local network of a site I manage. I enabled hyper-v and installed ubuntu 20.04 using the quick setup wizard from Microsoft.
I installed zabbix client and zabbix server first.
I got client working pushing data up to my gcp zabbix instance (it has both 127.0.0.1 and my cloud instance set as servers it pushes to
I have zabbix server working as well no problem
now I am trying to get zabbix-proxy to work so I can collect statistics on other local devices up to my cloud instance
so I go touch that files
but it still doesn't work
any ideas? I use linux a lot and I have never had to deal with a pid file issue before. not sure where to go with this
ubuntu 20.04 LTS virtual machine
running inside Hyper-V on windows 11 pro
zabbix 5.4.1
PostgresSQL
Apache2
I have a machine on the local network of a site I manage. I enabled hyper-v and installed ubuntu 20.04 using the quick setup wizard from Microsoft.
I installed zabbix client and zabbix server first.
I got client working pushing data up to my gcp zabbix instance (it has both 127.0.0.1 and my cloud instance set as servers it pushes to
I have zabbix server working as well no problem
now I am trying to get zabbix-proxy to work so I can collect statistics on other local devices up to my cloud instance
Code:
root@LOLIANET-ADMIN-LINUX:/etc/zabbix# service zabbix-proxy start root@LOLIANET-ADMIN-LINUX:/etc/zabbix# service zabbix-proxy status ● zabbix-proxy.service - Zabbix Proxy Loaded: loaded (/lib/systemd/system/zabbix-proxy.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2022-02-14 18:15:08 PST; 5s ago Process: 278629 ExecStart=/usr/sbin/zabbix_proxy -c $CONFFILE (code=exited, status=0/SUCCESS) Main PID: 278631 (code=exited, status=1/FAILURE) Feb 14 18:15:08 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Main process exited, code=exited, status=1/FAILU>Feb 14 18:15:08 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'. root@LOLIANET-ADMIN-LINUX:/etc/zabbix# root@LOLIANET-ADMIN-LINUX:/etc/zabbix# tail /var/log/syslog Feb 14 18:15:19 LOLIANET-ADMIN-LINUX systemd[1]: Started Zabbix Proxy. Feb 14 18:15:19 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Main process exited, code=exited, status=1/FAILURE Feb 14 18:15:19 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'. Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Scheduled restart job, restart counter is at 24718. Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: Stopped Zabbix Proxy. Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: Starting Zabbix Proxy... Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: Operation not permitted Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: Started Zabbix Proxy. Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Main process exited, code=exited, status=1/FAILURE Feb 14 18:15:29 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'. root@LOLIANET-ADMIN-LINUX:/etc/zabbix#
Code:
root@LOLIANET-ADMIN-LINUX:/etc/zabbix# touch /run/zabbix/zabbix_proxy.pid root@LOLIANET-ADMIN-LINUX:/etc/zabbix# chown zabbix:zabbix /run/zabbix/zabbix_proxy.pid
Code:
root@LOLIANET-ADMIN-LINUX:/etc/zabbix# service zabbix-proxy restart root@LOLIANET-ADMIN-LINUX:/etc/zabbix# service zabbix-proxy status ● zabbix-proxy.service - Zabbix Proxy Loaded: loaded (/lib/systemd/system/zabbix-proxy.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2022-02-14 18:18:36 PST; 5s ago Process: 278833 ExecStart=/usr/sbin/zabbix_proxy -c $CONFFILE (code=exited, status=0/SUCCESS) Main PID: 278835 (code=exited, status=1/FAILURE) Feb 14 18:18:36 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Main process exited, code=exited, status=1/FAILURE Feb 14 18:18:36 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'. root@LOLIANET-ADMIN-LINUX:/etc/zabbix# tail /var/log/syslog Feb 14 18:18:36 LOLIANET-ADMIN-LINUX systemd[1]: Started Zabbix Proxy. Feb 14 18:18:36 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Main process exited, code=exited, status=1/FAILURE Feb 14 18:18:36 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'. Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Scheduled restart job, restart counter is at 1. Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: Stopped Zabbix Proxy. Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: Starting Zabbix Proxy... Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: Operation not permitted Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: Started Zabbix Proxy. Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Main process exited, code=exited, status=1/FAILURE Feb 14 18:18:46 LOLIANET-ADMIN-LINUX systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'. root@LOLIANET-ADMIN-LINUX:/etc/zabbix#
Comment