Hi,
Is there anything that could be killing the agent process? Anything regarding this in var/log/messages?
What about UserParameters? An incorrectly defined UserParameter script could also cause such behavior.

In the zabbix-agent logs - clean.
After the zabbix-agent stops, the semaphores remain in place. On some servers, their number exceeds 5000.

UserParameter is used, but on version 4.0.x there is no such problem.
Now I roll back all agents from 4.2.2 to 4.0.8

Might be different, but a similar issue with sender: ZBX-16218 .

Yes. 100% is a similar problem!

Likely related to ZBX-16218. I'll keep both of these issues open for now, at least until a potential fix for both of them is proposed.

It doesn't appear to happen with zabbix_agentd, at least not in my case:

root@c1:~# ipcs -s -u zabbix
Semaphores:
T           ID          KEY MODE        OWNER    GROUP
s       327688            0 --rw------- zabbix   zabbix

root@c1:~# service zabbix_agentd restart
Stopping zabbix_agentd.
Waiting for PIDS: 40674.
root@c1:~# service zabbix_agentd restart
Stopping zabbix_agentd.
Waiting for PIDS: 40724.
root@c1:~# service zabbix_agentd restart
Stopping zabbix_agentd.
Waiting for PIDS: 40754.
root@c1:~# service zabbix_agentd restart
Stopping zabbix_agentd.
Waiting for PIDS: 40784.
root@c1:~# ipcs -s -u zabbix
Semaphores:
T           ID          KEY MODE        OWNER    GROUP
s       589832            0 --rw------- zabbix   zabbix

This is on FreeBSD 11.2-RELEASE-p10 and Zabbix 4.2.1. Unfortunately 4.2.2 hasn't landed in the ports tree yet so I'm unable to test it.

I see ZBX-16218 has been closed with a "resolved" status. And this issue is apparently linked to ZBX-16128, is that a typo? That issue seems to be unrelated.

I don't mind if one of the two is closed, it's rather pointless to have two tickets reporting on the same issue.

Hello sirdice,

Yes indeed it was a typo, updated to correct one, thanks for noticing!

kmenschikov It seems that issue is fixed in:

• 4.2.4rc1 07391f7a9e7
• 4.4.0alpha1 (master) b561d885e23

Please check when you have the opportunity.

Best Regards,
Aleksandrs

Hello,

Have you had any success with re-checking? At the moment I will be closing the issue as duplicate, but let us know if the issue persists!

Best Regards,
Aleksandrs

Fixed in:

• pre-4.0.28rc1 77b896149e0
• pre-5.0.8rc1 965f5d7310a
• pre-5.2.4rc1 a7b60383f28
• pre-5.4.0alpha1 (master) 6c50ea47a28