Ad Widget

Collapse

Zabbix will not start on Centos...

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Alfista
    Senior Member
    • Mar 2017
    • 136

    #1

    Zabbix will not start on Centos...

    Hi,

    I have now done a clean install of Zabbix 4 on CenOS and after start it crash and will not work.
    Please can you help me where can be the problem?

    I have this in log:
    Code:
      3254:20181005:115217.180 Starting Zabbix Server. Zabbix 4.0.0 (revision 85308).
      3254:20181005:115217.180 ****** Enabled features ******
      3254:20181005:115217.180 SNMP monitoring:           YES
      3254:20181005:115217.181 IPMI monitoring:           YES
      3254:20181005:115217.181 Web monitoring:            YES
      3254:20181005:115217.181 VMware monitoring:         YES
      3254:20181005:115217.181 SMTP authentication:       YES
      3254:20181005:115217.181 Jabber notifications:      YES
      3254:20181005:115217.181 Ez Texting notifications:  YES
      3254:20181005:115217.181 ODBC:                      YES
      3254:20181005:115217.181 SSH2 support:              YES
      3254:20181005:115217.181 IPv6 support:              YES
      3254:20181005:115217.181 TLS support:               YES
      3254:20181005:115217.181 ******************************
      3254:20181005:115217.181 using configuration file: /etc/zabbix/zabbix_server.conf
      3254:20181005:115217.189 current database version (mandatory/optional): 04000000/04000000
      3254:20181005:115217.189 required mandatory version: 04000000
      3254:20181005:115217.204 server #0 started [main process]
      3255:20181005:115217.205 server #1 started [configuration syncer #1]
      3256:20181005:115217.206 server #2 started [ipmi manager #1]
      3256:20181005:115217.206 cannot start IPMI service: Cannot bind socket to "/var/run/zabbix/zabbix_server_ipmi.sock": [13] Permission denied.
      3260:20181005:115217.210 server #6 started [housekeeper #1]
      3254:20181005:115217.210 One child process died (PID:3256,exitcode/signal:1). Exiting ...
      3264:20181005:115217.222 server #10 started [http poller #3]
      3254:20181005:115217.224 syncing history data...
      3254:20181005:115217.224 syncing history data done
      3254:20181005:115217.224 syncing trend data...
      3254:20181005:115217.224 syncing trend data done
      3254:20181005:115217.224 Zabbix Server stopped. Zabbix 4.0.0 (revision 85308).
      3264:20181005:115217.236 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reason:0]. Exiting ...
    Thanks.
  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #2
    Have you enabled SELinux?
    If you enable SELinux and make it run, please set policy.

    Comment

    • pesbarcavn
      Junior Member
      • Oct 2018
      • 3

      #3
      I think you check SELinux and set it disable

      Comment

      • Alfista
        Senior Member
        • Mar 2017
        • 136

        #4
        And how to enable SELinux?

        Comment


        • Alfista
          Alfista commented
          Editing a comment
          Thanks, found it, and now it works.
      • ITOMDave
        Member
        • Nov 2018
        • 53

        #5
        Hi all, I know this is an old thread but for those who come across it, the following link may help you progress with running "semanage"

        Dave
        semanage command not found in CentOS 7 and RHEL 7

        Comment

        Working...