[ZBX-16690] Could not lock PID file [/tmp/zabbix_agentd.pid]: [13] Permission denied Created: 2019 Sep 26  Updated: 2019 Sep 28  Resolved: 2019 Sep 27

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

Type: Incident report Priority: Minor
Reporter: Bernard Fay Assignee: Zabbix Support Team
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AIX 7.2
$ oslevel -s
7200-03-03-1914


 Description   

I installed the Zabbix agent on a AIX machine. Though it works well, I have the following error repeated countless time. 

zabbix_agentd [8388944] Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [13] Permission denied

The Zabbix agent version is: 

$ /opt/zabbix/sbin/zabbix_agentd -V
zabbix_agentd (daemon) (Zabbix) 4.0.7
Revision 92831 18 April 2019, compilation time: May 10 2019 08:40:52

Copyright (C) 2019 Zabbix SIA
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it according to
the license. There is NO WARRANTY, to the extent permitted by law.

Supported technology levels: 6100 and above

The PidFile configuration variable is set to the default value:

  1. PidFile=/tmp/zabbix_agentd.pid)

 

 A search on internet let me see other people with the same problem but without any solution.  

Does a solution exist for this problem?

 

 

 Comments   
Comment by Elina Kuzyutkina (Inactive) [ 2019 Sep 27 ]

Hello Bernard,

This issue tracker is for bug reports only. Please check https://www.zabbix.org/wiki/Getting_help for community or commercial support options.

Whichever method you choose, indicate there the method how you installed zabbix-agent, how you launch it and the contents ls -la /tmp | grep zabbix output

No indication of a bug.
Regards, Elina

Comment by Glebs Ivanovskis [ 2019 Sep 28 ]

Is Resolution correct?

Generated at Wed Apr 01 19:11:56 EEST 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.