How to upgrade MariaDB with ISPCONFIG

Hi,

i am using latest ispconfig with debian 11 and mariadb 10.5.15-MariaDB-0+deb11u1-log Debian 11

In lists i can see that latest stable version for mariadb is 10.9.3.

Is here any way how to do upgrade safety? Will be working everything fine ather upgrade incl. ispconfig?

 

Hello, I did update mariadb to LTS 10.11.4, and I find that the backups IPSCOnfig3 (fully up-to-date and patched) is making since that upgrade (from 10.6 to 10.11) are empty!

Can you confirm that ISPConfig 3 latest will not work properly with MariaDB 10.11 ?

Thanks

 

Maybe the MariaDB version that you've installed did not create a symlink to mysqldump?
Reason behind this is that since MariaDB 10.5 mysqldump is only a symlink to mariadb-dump.

You should check if the command/symlink exists on your system at all!

Beginning with MariaDB 11.0.1 even the symlink is not created by the installer anymore.
Something that we should keep in mind to add/workaround in future ISPConfig releases.

More information:
https://mariadb.com/kb/en/mysqldump/

 

Hello again, also, I reinstalled mariadb 10.6 hoping it would work and I'm trying to setup the master slave nameservers and when I do the expert install on the slave, at the last step when it tries to connect to the master dbispconfig db I get a fatal error:
MySQL master server database name [dbispconfig]:

ERROR: Unable to load SQL-Dump into database table.
root@ns3:/tmp/ispconfig3_install/install#

all my root mysql passwords are correct. Could this be a character set problem, or more likey mariadb 10.6 doing a dump differently than before?

I am able to connect to the master mysql from the future slave via mysql -h master host ip ...

When I run the install it says OK after checking the version of mariadb at 10.6

Thanks for your input. Is it ok to use utf8mb4 as character set , or should I stick to utf8 ? - it fails with the same error both ways. I know that utf-8 is no longer supported by mariadb as of 10.6 and I believe there were changes in support of mariadb dump vs mysqldump.

 

Thanks Michaelabgelo - that's the problem. symlink command isn't there on either the master or the slave and mariadb-dump needs it. Is udev the package to get symlink? I have a version which devs are saying is broken - 247.3-7+deb11u2

Do you know anything about this? Is there anothe way to get the command symlink (anyways I used to use ln -s - isn't that used any longer?) on bullseye?

Does the exact command "symlink" need to be working (to produce output) on the terminal in order for the install of ispconfig3 to work?

Michaelangelo or Till, would you happen to know the exact command to create the needed symlink?

For example ln -s /mariadb-dump /mysqldump ? do I just fing the paths and add them, or do I cd to the target directory and create the symlink form there?

Thansk for advice, I've got to get the nameservers working again!!!

 

I am also setting symlinks on in the my.cnf or 50-server.cnf:
symbolic-links=0 --> 1

the default may be off I believe

 

Well I installed symlinks program, and the symlink exists:
in /usr/bin/:
relative: /usr/bin/mysqldump -> mariadb-dump
is the target perhaps missing the /usr/bin/ in front of it? (it doesn't appear to need the dir info if it is in the same directory as the source - it appears - I'm new at symlinks)

so, my problem has nothing to do with a lack of symlinks, right?

 

There is no command symlink. Symlink is symbolic link. They are created with command ln -s, like you have done previously.
Michelangelo asked you to check the command mysqldump exists and there is the needed symbolic link.

 

Thanks Taleman for that clarification - yes, the command mysqldump exists and I listed the symlink, above. I don't know how else to check if the symlink exists properly. It does exist.

I found out the problem: I had root and mysql @ localhost passwords that were corrupted because I tried to run that line in the server setup to use mysql-native-password - and that failed, and I didn't check if they were corrupted or not. Very sorrry for wasting everyone's time. The "perfect server" installs fine on bullseye - except for that one line.

 

In case anyone else has this problem - the mysql-native-password type stops being supported from mariadb 10.5 on.
Strange, becasue mysql -u root -p still works supplying the root password. To fix the error, login as root to mysql, and run the following commands (you don't even need to restart mariadb in safe_mode, it seems!!!):
SELECT User, Host, Password FROM mysql.user;

If you see 'invalid" for the root and the mysql user, as I did (because mysql-native-password isn't supported anymore), do this:

ALTER USER 'root'@'localhost' IDENTIFIED BY 'VALID_USER_PASSWORD';
ALTER USER 'mysql'@'localhost' IDENTIFIED BY 'VALID_USER_PASSWORD';
FLUSH PRIVILEGES;

quit; and restart mariadb and then run mysql_upgrade --force

Should do the trick!

 

As already stated various times in various posts and threads, ISPConfig only supports default MariaDB version shipped with the OS, thus wise, I would repeat the advise to avoid upgrading it via other than the supported OS repos as that may cause a lot of problems, errors and/or failures to your ISPConfig server.

Should anyone insist in pursuing the same despite repeated advices, I think it will only be polite not to trouble this community with any of the said problems as such an upgrade is clearly not supported; or, if anyone really think it does work, I think it is best to open a tip thread and provide your intels and supports in there.

 

If you are trying to update MariaDB to the latest much improved LTS version 11.4 - you need to add the bookworm package "mariadb-client-compat" to your server in order to do an ispconfig 3.2 upgrade/update.