[ZBX-15450] Zabbix server is not running: information displayed may not be current Created: 2019 Jan 14 Updated: 2019 Jan 15 Resolved: 2019 Jan 14 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Prasanna Kumar J | Assignee: | Arturs Lontons |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 7.4 Keral version: |
||
| Description |
|
Error when restarting /starting zabbix
Job for zabbix-server.service failed because a configured resource limit was exceeded. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.
****************out put of "journalctl -xe" ************************** Jan 14 13:42:03 pune-zabbix01 systemd[1]: Unit zabbix-server.service entered failed state. Jan 14 13:42:03 pune-zabbix01 systemd[1]: zabbix-server.service failed. Jan 14 13:42:03 pune-zabbix01 polkitd[751]: Unregistered Authentication Agent for unix-process:16846:24657624 (system bus name :1.39, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Jan 14 13:42:13 pune-zabbix01 systemd[1]: zabbix-server.service holdoff time over, scheduling restart. Jan 14 13:42:13 pune-zabbix01 systemd[1]: Starting Zabbix Server... – Subject: Unit zabbix-server.service has begun start-up – Defined-By: systemd – Support: [http://lists.freedesktop.org/mailman/listinfo/systemd-devel] – – Unit zabbix-server.service has begun starting up. Jan 14 13:42:13 pune-zabbix01 systemd[1]: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start. Jan 14 13:42:13 pune-zabbix01 systemd[1]: zabbix-server.service never wrote its PID file. Failing. Jan 14 13:42:13 pune-zabbix01 systemd[1]: Failed to start Zabbix Server. – Subject: Unit zabbix-server.service has failed – Defined-By: systemd – Support: [http://lists.freedesktop.org/mailman/listinfo/systemd-devel] – – Unit zabbix-server.service has failed. – – The result is failed.
----log file: zabbix_server [22997]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [23007]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [23014]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [23024]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [23032]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30890]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30898]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30908]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30915]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30922]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30931]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30938]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30945]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30954]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30961]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30969]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30983]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30990]: cannot open log: cannot create semaphore set: [28] No space left on device zabbix_server [30997]: cannot open log: cannot create semaphore set: [28] No space left on device
Please let me know what can be done for fixing this? |
| Comments |
| Comment by dimir [ 2019 Jan 14 ] |
|
Can't you see from the error message the reason? zabbix_server [30997]: cannot open log: cannot create semaphore set: [28] No space left on device |
| Comment by dimir [ 2019 Jan 14 ] |
|
And next time, please do not use this bug tracker to report your issues with setting up Zabbix, it is meant for reporting bugs/feature requests in Zabbix. For getting help with using Zabbix see the options listed here: https://zabbix.org/wiki/Getting_help , e. g. the http://www.zabbix.com/forum/
|
| Comment by Glebs Ivanovskis [ 2019 Jan 15 ] |
|
From man semget: ENOSPC A semaphore set has to be created but the system limit for the
maximum number of semaphore sets (SEMMNI), or the system wide
maximum number of semaphores (SEMMNS), would be exceeded.
Consider raising the limits or removing unneeded old semaphore sets. |