Can't open PID file /run/zabbix/zabbix_server.pid

[yatta]

Hi,
I'm trying to install Zabbix on Suse and follow the instructions below;

https://www.zabbix.com/download
https://www.zabbix.com/documentation/5.4/en/manual/installation/install#installing_frontend

After that I'm trying to start "zabbix-server" service, but it gives the error below;

wsapzabbix1:/usr/lib/systemd/system # service zabbix-server status
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2022-02-10 16:34:45 EET; 4s ago
Process: 8712 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 8714 (zabbix_server)
Tasks: 1
CGroup: /system.slice/zabbix-server.service
└─8714 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

Feb 10 16:34:45 wsapzabbix1 systemd[1]: Starting Zabbix Server...
Feb 10 16:34:45 wsapzabbix1 systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: Operation not permitted
Feb 10 16:34:45 wsapzabbix1 systemd[1]: Started Zabbix Server.

Any idea why? I Googled it but nothing helped.
Regards.

[tim.mooney]

Does the /run/zabbix directory exist? The various Zabbix packages include a file that should be getting installed into /usr/lib/tmpfiles.d/ . Are there zabbix-*.conf files in that directory? The /run directory is a pseudo-filesystem managed by systemd and recreated whenever systemd is started. To have subdirectories in that pseudo-filesystem, the typical method is to list the directory with permissions that should get created in a conf file in /usr/lib/tmpfiles.d/

Are you installing packages, or did you build the software from source code?

Are you using AppArmor, SELinux, or anything these that can restrict access to certain paths?

[yatta]

-Does the /run/zabbix directory exist?

Yes it's exist;

server:/run/zabbix # ll
total 4
-rw-rw-r-- 1 root root 4 Feb 10 15:57 zabbix_agentd.pid
wsapzabbix1:/run/zabbix #

-Are you installing packages, or did you build the software from source code?

Not sure what is that mean but I just followed instructions from the pages below;

https://www.zabbix.com/download
https://www.zabbix.com/documentation/5.4/en/manual/installation/install#installing_frontend

-Are you using AppArmor, SELinux, or anything these that can restrict access to certain paths?
Stil not sure. OS is SUSE SLE 15. How can I check that?

[cyber]

Most difficult way... Not knowing much about platform and trying to install from sources..
Scratch it and install from packages...

[irwan13th]

issue resolved?

[Atsushi]

As far as I can see the result of executing the command of the first contributor, Zabbix server seems to be able to start.

Active: active (running)

If Zabbix server is not working now, check the log file to see what the problem is. The PID file open error may be that systemd was unable to write the PID file when it first started zabbix_server immediately after installation. However, after that, systemd can successfully create the PID file and it seems that Zabbix server can be started normally, so there is no problem with the PID file.
Zabbix server may not be able to start due to a completely different cause, in which case it is necessary to investigate the cause by checking the contents of the log file.

[yatta]

I deleted everything and made a fresh installation, so far I haven't seen same error.