Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-14730

Zabbix server is running No localhost:10051

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • None
    • None
    • None

      Status of Zabbix

      Parameter Value Details
      Zabbix server is running No localhost:10051

      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.
      
      -------------------------------------------------------------------------------------------------------
      [root@localhost admin]# 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: exit-code) since Wed 2018-08-15 00:19:46 EDT; 4s ago
       Process: 20099 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=1/FAILURE)
      
      Aug 15 00:19:46 localhost.localdomain systemd[1]: Failed to start Zabbix Server.
      Aug 15 00:19:46 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
      Aug 15 00:19:46 localhost.localdomain systemd[1]: zabbix-server.service failed.
      [root@localhost admin]#
      --------------------------------------------------------------
      
      [root@localhost admin]# cat /etc/selinux/config
      
      # This file controls the state of SELinux on the system.
      # SELINUX= can take one of these three values:
      # enforcing - SELinux security policy is enforced.
      # permissive - SELinux prints warnings instead of enforcing.
      # disabled - No SELinux policy is loaded.
      SELINUX=disabled
      # SELINUXTYPE= can take one of three two values:
      # targeted - Targeted processes are protected,
      # minimum - Modification of targeted policy. Only selected processes are protected.
      # mls - Multi Level Security protection.
      SELINUXTYPE=targeted
      

       

            Unassigned Unassigned
            mo30 mo30
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: