Ad Widget

Collapse

zabbix server cannot start

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • panicos
    Junior Member
    • Sep 2017
    • 3

    #1

    zabbix server cannot start

    Hello,
    I installed last version of Zabbix on a CentOS 7 and when i try to start the Zabbix service, i get errors. Here are the details:
    [root@NGSRV3 ~]# systemctl start zabbix-server
    Job for zabbix-server.service failed because a configured resource limit was exceeded. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.
    [root@NGSRV3 ~]#
    [root@NGSRV3 ~]# systemctl status zabbix-server.service
    ● zabbix-server.service - Zabbix Server
    Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
    Active: activating (auto-restart) (Result: resources) since Thu 2017-09-21 21:07:08 EEST; 3s ago
    Process: 3021 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
    Main PID: 1217 (code=exited, status=1/FAILURE)
    Sep 21 21:07:08 NGSRV3 systemd[1]: zabbix-server.service never wrote its PID file. Failing.
    Sep 21 21:07:08 NGSRV3 systemd[1]: Failed to start Zabbix Server.
    Sep 21 21:07:08 NGSRV3 systemd[1]: Unit zabbix-server.service entered failed state.
    Sep 21 21:07:08 NGSRV3 systemd[1]: zabbix-server.service failed.
    [root@NGSRV3 ~]#

    In /var/log/zabbix/zabbix_server.log i have the following:

    1723:20170921:205159.871 using configuration file: /etc/zabbix/zabbix_server.conf
    1723:20170921:205159.871 cannot set resource limit: [13] Permission denied
    1723:20170921:205159.871 cannot disable core dump, exiting...
    zabbix_server [1726]: cannot open log: cannot create semaphore set: [28] No space left on device
    zabbix_server [1729]: cannot open log: cannot create semaphore set: [28] No space left on device
    zabbix_server [1732]: cannot open log: cannot create semaphore set: [28] No space left on device
    zabbix_server [1735]: cannot open log: cannot create semaphore set: [28] No space left on device
    zabbix_server [1738]: cannot open log: cannot create semaphore set: [28] No space left on device
    zabbix_server [1741]: cannot open log: cannot create semaphore set: [28] No space left on device
    zabbix_server [1746]: cannot open log: cannot create semaphore set: [28] No space left on device
    But there is enough space on the disk:
    [root@NGSRV3 ~]# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/cl_ngsrv3-root 14G 1.6G 13G 12% /
    devtmpfs 484M 0 484M 0% /dev
    tmpfs 495M 0 495M 0% /dev/shm
    tmpfs 495M 6.7M 488M 2% /run
    tmpfs 495M 0 495M 0% /sys/fs/cgroup
    /dev/sda1 1014M 168M 847M 17% /boot
    tmpfs 99M 0 99M 0% /run/user/0
    [root@NGSRV3 ~]#

    I was suggested this is a SELinux problem, but i don't know how to troubleshoot this further. I have seen previous topics with this similar issue, and try the workarounds found, but could not manage to solve the problem.
    Also i admit i am not an experienced linux user.
    Do you have any support suggestions regarding this issue?

    THank you.
  • allexpetrov
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2017
    • 361

    #2
    As you've mentioned - this could be a SELinux problem. You could disable SELinux if you don't know how to operate with it or you can allow using audit2allow

    Comment

    • panicos
      Junior Member
      • Sep 2017
      • 3

      #3
      indeed, i have no ideea how to operate SELinux. Therefore, i maaged to set it to permissive mode and the issue is solved now.
      Can there be any other issue if i set it to permissive mode (which i guess = disabled)? Or is it ok if i leave it like this?

      Thanks.

      Comment

      • allexpetrov
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • May 2017
        • 361

        #4
        Hi,
        disabled is when SELinux disabled. Actually it all depends on your security requirements. If you ok to go without it - you can go without it, you will save your time in future. Ask your Security team

        Regards,
        Alex!

        Comment

        • morten.moesgaard
          Junior Member
          • Jan 2017
          • 2

          #5
          Could this be the answer maybe ??

          Comment

          Working...