Ad Widget

Collapse

Zabbix Frontend MySQL setup failed - CentOS7, new 3.4 installation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • TheNetworkGuy
    Junior Member
    • Jul 2018
    • 6

    #1

    Zabbix Frontend MySQL setup failed - CentOS7, new 3.4 installation

    Hi Zabbix forum members,

    I'm trying to setup a new zabbix lab with dedicated database, server and front end VM's. Details are listed below:
    - All machines can reach each other using ICMP ping
    - Firewalld has been disabled on all machines
    - All machines are on the same VLAN, no firewall or routing involved
    - Software has been installed using the latest Zabbix YUM repo

    192.168.5.111 Database
    192.168.5.114 Server
    192.168.5.116 Frontend

    When running the setup.php on the new Frontend database i get the following error:

    Error connecting to database: Can't connect to MySQL server on '192.168.5.111' (13 "Permission denied")

    I added the SQL user using following commands:

    mysql> create database zabbix character set utf8 collate utf8_bin;
    mysql> grant all privileges on zabbix.* to [email protected]/255.255.255.0 identified by 'supersecretpassword';

    The annoying thing is that i can connect from the Frontend server to the database using the mariadb-client package:

    [root@frt01 zabbix]# mysql -h 192.168.5.111 -u zabbix -p zabbix
    Enter password:
    Welcome to the MariaDB monitor. Commands end with ; or \g.
    Your MariaDB connection id is 22
    Server version: 5.5.56-MariaDB MariaDB Server

    Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

    MariaDB [(none)]>

    I'm copy pasting the password which works with the mysql-client command. I only installed the zabbix-web-mysql package on the Frontend server, no other Zabbix related packages / tools.

    Does anyone have an idea where i can look next? Maybe some hidden log files etc?

    Thanks in advance!
  • TheNetworkGuy
    Junior Member
    • Jul 2018
    • 6

    #2
    Problem solved.. SELinux got in the way on the frontend server.

    Comment

    Working...