[ZBX-11334] zabbix agent service failed, PID not readable Created: 2016 Oct 07  Updated: 2018 May 06  Resolved: 2016 Oct 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 3.0.4
Fix Version/s: None

Type: Incident report Priority: Critical
Reporter: perigee Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS7



 Description   

I'm trying to run zabbix-agent 3.0.4 on CentOS7, systemd failed to start the zabbix agent, from `journalctl -xe`

```
PID file /run/zabbix/zabbix_agentd.pid not readable (yes?) after start.
node=localhost.localdomain type=SERVICE_START msg=audit(1475848200.601:17994): pid=1 uid=0 auid=4294967298 ses=...
zabbix-agent.service never wrote its PID file. Failing.
Failed to start Zabbix Agent.
```

There is no permission error, and I try to re-configure the PID path to /tmp folder in zabbix-agent.service and zabbix_agentd.conf, it doesn't work.

Very weird, anyone has idea? Thank you in advance.



 Comments   
Comment by richlv [ 2016 Oct 07 ]

this issue tracker is for bugreports, and the current issue looks more like a support request at this time - please see http://zabbix.org/wiki/Getting_help for support options.

in this case, try starting agent daemon directly and see whether there are any errors

Comment by Francisco [ 2018 May 06 ]

Greetings,

 

I had the same issue and by looking at logs with this command "tail -1 /var/log/zabbix/zabbix_agentd.log" i have observed:
zabbix_agentd [30615]: cannot open log: cannot create semaphore set: [28] No space left on device

i had gathered info on this from:
https://gerardnico.com/linux/semaphore

and checked the semaphore array max usage:
$>cat /proc/sys/kernel/sem
output: 250 32000 32 128

$>ipcs -s | grep -c "^0x"
output: 128

the last value, 128 is the max limit reached for semaphore arrays, so i needed to increase that, by doing:
$>echo "kernel.sem = 250 32000 32 256" >> /etc/sysctl.conf
$> sysctl -p /etc/sysctl.conf
output: kernel.sem = 250 32000 32 256

After this, i needed to check the new sempahore array:
$> cat /proc/sys/kernel/sem
output: 250 32000 32 256

and restart zabbix:
$> systemctl start zabbix-agent

$> systemctl status zabbix-agent
● zabbix-agent.service - Zabbix Agent
Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2018-05-05 13:20:09 ADT; 26s ago
Process: 30681 ExecStart=/usr/sbin/zabbix_agentd -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 30683 (zabbix_agentd)
CGroup: /system.slice/zabbix-agent.service
├─30683 /usr/sbin/zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf
├─30684 /usr/sbin/zabbix_agentd: collector [idle 1 sec]
├─30685 /usr/sbin/zabbix_agentd: listener #1 [waiting for connection]
├─30686 /usr/sbin/zabbix_agentd: listener #2 [waiting for connection]
├─30687 /usr/sbin/zabbix_agentd: listener #3 [waiting for connection]
└─30688 /usr/sbin/zabbix_agentd: active checks #1 [idle 1 sec]

Thanks to everyone for their help

Generated at Sat Aug 02 09:51:14 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.