[closed] Update to ISPConfig version 3.2.11p2 on multiserver causes error

Hello,
among other things, we operate a multiserver setup with ispconfig and the following servers:
1 panel, 4 web, 2 storage (also set up as a web server), 2x mail, 2x ns
All servers are Debian12 systems.
However, the web01 causes problems when updating to ISPConfig 3.2.11p2. The installation aborts when attempting to connect to the database on panel. The following error message appears:

Code:

Checking ISPConfig database .. mysqlcheck: Got error: 1130: Host '127.0.0.1' is not allowed to connect to this MariaDB server when trying to connect
OK
ERROR 1130 (HY000): Host '127.0.0.1' is not allowed to connect to this MariaDB server
Unable to call mysql command line with credentials from mysql_clientdb.conf

All other servers ran fine and the update worked without any problems.
The firewall is set correctly and allows access to port 3306 via the internal IP address (10.0.0.0/24, 10.0.1.0/24), the external IP address of web01 and via the host name. However, it is possible to access the databases on panel and web01 manually using mysql -h panel.XXXX.XX -u root -p and mysql -h localhost -u root -p. The passwords in /usr/local/ispconfig/server/lib/mysql_clientdb.conf are also correct.
The test script shows no abnormalities.

What has been tried so far:

• Control of mariaDB settings and adoption of configuration files from other systems.
• Resetting the rights for the database users on panel.
• Delete and create new database users on panel.

What else can we do?

 

My understanding is the host db accounts are not visible in ISPConfig Panel, and they can not be manipulated with panel.
The host db accounts are the ones you created during installation with database commands. I check them using PHPMyAdmin, they are shown in the User Accounts -tab.
During update, it is the host that is updated that connects to the master server, so check from command line this works.

 

Hello Taleman,
thanks for yout answer. I think there is a little misunderstanding here. Of course, the accounts are not created in the panel (webpanel). We have our own server named panel on which only the webpanel runs. This is then the master server.

As described, the system user accounts on the master were recreated directly in the database. The commands used were as follows:

Code:

CREATE USER 'root'@'10.0.x.x' IDENTIFIED BY 'XXXXXXXXXXXX' ;
GRANT ALL PRIVILEGES ON * . * TO 'root'@'10.0.x.x' IDENTIFIED BY 'XXXXXXXXXXXX' WITH GRANT OPTION MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;
CREATE USER 'root'@'web01.XXXXX.XX' IDENTIFIED BY 'XXXXXXXXXXXX' ;
GRANT ALL PRIVILEGES ON * . * TO 'root'@'web01.XXXXX.XX' IDENTIFIED BY 'XXXXXXXXXXXX' WITH GRANT OPTION MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;

And yes, manual connections on the command line are possible both from the web01 to panel direction and from the panel to web01 direction.

 

This command gives:

Code:

mysqlcheck: Got error: 1130: Host '127.0.0.1' is not allowed to connect to this MariaDB server when trying to connect

 

I also ran into this problem when I upgraded from Debian 11 to 12 today. MariaDB went from 10.5 to 10.11

After a short googling, I found out that "skip-name-resolve" enabled in MariaDB config, so the root@localhost (which exists as per ISPconfig default installation) user not working as [email protected] (which is non existent).

The solution is disable skip-name-resolve option in MariaDB config, or add both [email protected] and root@::1 users (with same password as root@localhost).

Interesting that when I previously upgraded this same server from Debian 10 to 11 (also with skip-name-resolve enabled), this not happened at MariaDB 10.3 to 10.5 upgrade.