[ZBX-14767]  amount of semaphor for zabbix Created: 2018 Aug 25  Updated: 2018 Aug 30  Resolved: 2018 Aug 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Major
Reporter: mo30 Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

hi

How much should be the amount of semaphores for zabbix ?

we need to Increase amount . 

service zabbix cannt start 

 

 

cat /var/log/zabbix/zabbix_server.log
.
.
.
zabbix_server [19361]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19374]: cannot open log: cannot create semaphore set: [28] No space left on device

-------------------------------------

[root@localhost admin]# ipcs -ls

------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 250
max semaphores system wide = 32000
max ops per semop call = 32
semaphore max value = 32767
-----------------------------------------
[root@localhost admin]# systemctl restart zabbix-server.service
Job for zabbix-server.service failed because the control process exited with err or code. See "systemctl status zabbix-server.service" and "journalctl -xe" for d etails.

 



 Comments   
Comment by Vladislavs Sokurenko [ 2018 Aug 25 ]

Please check selinux log

Comment by mo30 [ 2018 Aug 27 ]

 

[root@localhost ~]# grep "SELinux is preventing" /var/log/messages
[root@localhost ~]# grep "denied" /var/log/audit/audit.log
[root@localhost ~]# sestatus
SELinux status: disabled
[root@localhost ~]#

Comment by Glebs Ivanovskis [ 2018 Aug 27 ]

Check what ipcs -us and ipcs -s show you. Perhaps, you just need to delete old semaphores manually (actually, make sure you let Zabbix terminate gracefully by not sending SIGKIL to it, use SIGTERM instead - this could be the reason for the buildup of old semaphores). Each Zabbix daemon needs just one semaphore set with less than 15 semaphores in it, so this shouldn't cause any issues with system limits.

Comment by mo30 [ 2018 Aug 27 ]

hi 

before delete ipcrm but when retart zabbix-service  not start 

 

---------------------------------------------

root@localhost ~]# ipcs -us

------ Semaphore Status --------
used arrays = 6
allocated semaphores = 19

[root@localhost ~]# ipcs -s

------ Semaphore Arrays --------
key semid owner perms nsems
0x00000000 98304 zabbix 600 14
0x00000000 524289 apache 600 1
0x00000000 557058 apache 600 1
0x00000000 589827 apache 600 1
0x00000000 622596 apache 600 1
0x00000000 655365 apache 600 1

[root@localhost ~]#

Comment by Glebs Ivanovskis [ 2018 Aug 27 ]

Is the error message still the same in the log file?

Comment by mo30 [ 2018 Aug 27 ]

yes . zabbix service not start

 

-------------------

cat /var/log/zabbix/zabbix_server.log
.
.
.
zabbix_server [19361]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19374]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19379]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19384]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19389]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19398]: cannot open log: cannot create semaphore set: [28] No space left on device
----------------------------------------------------------------------------------------------------

[root@localhost admin]# systemctl restart zabbix_server
Failed to restart zabbix_server.service: Unit zabbix_server.service failed to load: No such file or directory.
------------------------------------------------------------------------------------------------------
[root@localhost admin]# systemctl restart zabbix-server
Job for zabbix-server.service failed because the control process exited with error code. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

Comment by Glebs Ivanovskis [ 2018 Aug 27 ]

Are you sure these aren't old messages? Please do

tail -n 10 /var/log/zabbix/zabbix_server.log; systemctl restart zabbix_server; tail -n 10 /var/log/zabbix/zabbix_server.log

Maybe now Zabbix does not start for a different reason ("No such file or directory").

Comment by mo30 [ 2018 Aug 28 ]

tnks all new 

new comment : 

there is not the file /var/log/zabbix/zabbix_server.log 

the file zabbix_server.log  with date 

 

 

[root@localhost ~]# tail -n 10 /var/log/zabbix/zabbix_server.log
[root@localhost ~]#

=================================================================

[root@localhost ~]# dir /var/log/zabbix/
zabbix_agentd.log zabbix_agentd.log-20180716.gz

zabbix_agentd.log-20180826

zabbix_server.log-20180702.gz

zabbix_server.log-20180813.gz
zabbix_agentd.log-20180610.gz

zabbix_agentd.log-20180722.gz zabbix_

server.log zabbix_server.log-20180708.gz

zabbix_server.log-20180819
zabbix_agentd.log-20180618.gz

zabbix_agentd.log-20180730.gz

zabbix_server.log-20180604.gz

zabbix_server.log-20180716.gz
zabbix_agentd.log-20180624.gz

zabbix_agentd.log-20180805.gz

zabbix_server.log-20180610.gz

zabbix_server.log-20180722.gz
zabbix_agentd.log-20180702.gz

zabbix_agentd.log-20180813.gz

zabbix_server.log-20180618.gz

zabbix_server.log-20180730.gz
zabbix_agentd.log-20180708.gz

zabbix_agentd.log-20180819.gz

zabbix_server.log-20180624.gz

zabbix_server.log-20180805.gz

===================================================================
[root@localhost ~]# tail -n 10 /var/log/zabbix/zabbix_server.log-20180819
zabbix_server [19330]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19336]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19341]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19349]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19361]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19374]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19379]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19384]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19389]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19398]: cannot open log: cannot create semaphore set: [28] No space left on device
====================================================================================================

[root@localhost ~]# systemctl restart zabbix_server
Failed to restart zabbix_server.service: Unit zabbix_server.service failed to load: No such file or directory.

===============================================================================================================

[root@localhost ~]# tail -n 10 /var/log/zabbix/zabbix_server.log-20180819
zabbix_server [19330]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19336]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19341]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19349]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19361]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19374]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19379]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19384]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19389]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19398]: cannot open log: cannot create semaphore set: [28] No space left on device

 

Comment by Glebs Ivanovskis [ 2018 Aug 28 ]

Erm, I guess the service is named zabbix-server, not zabbix_server (with a dash instead of underscore).

Comment by mo30 [ 2018 Aug 28 ]

oh yes

[root@localhost admin]# systemctl restart zabbix-server
Job for zabbix-server.service failed because the control process exited with error code. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

=================

[root@localhost admin]# systemctl status zabbix-server
zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2018-08-28 07:00:25 EDT; 8s ago
Process: 5451 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=1/FAILURE)

Aug 28 07:00:25 localhost.localdomain systemd[1]: Failed to start Zabbix Server.
Aug 28 07:00:25 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
Aug 28 07:00:25 localhost.localdomain systemd[1]: zabbix-server.service failed.

======================================

[root@localhost admin]# tail -n 10 /var/log/zabbix/zabbix_server.log-20180819
zabbix_server [19330]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19336]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19341]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19349]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19361]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19374]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19379]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19384]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19389]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19398]: cannot open log: cannot create semaphore set: [28] No space left on device
[root@localhost admin]#

Comment by Glebs Ivanovskis [ 2018 Aug 28 ]

Now you are checking the wrong log file. At least there are no new messages about semaphores.

Comment by mo30 [ 2018 Aug 28 ]

tnks

how checking ? 

Comment by Glebs Ivanovskis [ 2018 Aug 29 ]

I think at this point you will progress faster if you address your questions to Zabbix community on IRC or forum. Check possible ways of getting help.

This place is a bug tracker and in your situation there is no indication of a bug in Zabbix.

Generated at Sat Aug 02 10:25:33 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.