Issue Deprecated Program Name Warning After Upgrading to MariaDB 11.4

[Daerik]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

18.0.64

After upgrading to Plesk Obsidian 18.0.64 and MariaDB 11.4 (from 10.11), I am encountering a persistent deprecation warning when running plesk db commands:

[root@plesk ~]# plesk db "SELECT 'test';"
mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead

I’ve confirmed that /usr/bin/mysql is correctly symlinked to mariadb:

[root@plesk ~]# ll /usr/bin/mysql
lrwxrwxrwx 1 root root 7 Sep 23 20:31 /usr/bin/mysql -> mariadb

To further troubleshoot, I also added an alias in .bashrc to alias mysql to mariadb, which stops the deprecation warning when executing mysql directly. However, the warning persists when using Plesk's db command, and this is also causing false positives in my cron jobs.

My question is whether Plesk plans to update the db command to better handle MariaDB 11.4, or if there's a workaround I can use to prevent this warning from triggering in Plesk CLI and cron jobs.

Any insights or suggestions would be greatly appreciated!

--

P.S. How do I mark these issue posts as resolved? I've found forum posts about it, but it appears my membership level is too low to do it myself.

 

[andreios]

I needed to add aliases for mysql, mysqldump. Plesk relies on these in some functions. Plesk Backups will fail (maybe silently if you don't have email notification enabled). Just adding theme to bash is not enough.

cd /usr/bin/
ln -s mariadb-dump mysqldump
ln -s mariadb mysql

I use Ubuntu 24

mysqldump

Old name for mariadb-dump.

mariadb.com

Don't know if there are other symlinks who got removed.

mysql symlink is needed for plesk installer and plesk repair and maybe other functions.

 

[Sebahat.hadzhi]

Our team is aware of the issue and they are currently working on rewriting all Plesk utilities that use /usr/bin/mysql* and make them fully compatible with MariaDB 11.4. Unfortunately, I cannot provide an ETA at the moment.

 

[learning_curve]

@Daerik FWIW This "change" (today's massive understatement!) has been coming for a long time now.
An early clue, was perhaps when /etc/mysql/my.cnf was changed to /etc/mysql/mariadb.cnf which was back with the Mariadb 10.5 -> 10.6, from memory

Some people are simply waiting for a MariaDB "announcement" aka ...from release **.** onward, depreciated will be changed to not allowed... Example
Others have gone pro-active (within their own associated systems packages etc) Example
Then there's some "definite maybes" too: Example

As you've already seen, all of the mysql labels, links and/or symlinks (when using Plesk) all still function, often, with the deprecation warning, as per your post & here's many existing, mysql symlinks e.g. a simple search & find in /usr/bin/ that's focused on mysql symlinks & ignoring all of the non-symlinked mariadb data:

# ls -la /usr/bin/ | grep "mysql.*\->"
lrwxrwxrwx  1 root root           7 Aug  5 08:54 mysql -> mariadb
lrwxrwxrwx  1 root root          14 Aug  5 08:54 mysqlaccess -> mariadb-access
lrwxrwxrwx  1 root root          13 Aug  5 08:54 mysqladmin -> mariadb-admin
lrwxrwxrwx  1 root root          13 Aug  5 08:54 mysqlanalyze -> mariadb-check
lrwxrwxrwx  1 root root          14 Aug  5 08:54 mysqlbinlog -> mariadb-binlog
lrwxrwxrwx  1 root root          13 Aug  5 08:54 mysqlcheck -> mariadb-check
lrwxrwxrwx  1 root root          28 Aug  5 08:54 mysql_convert_table_format -> mariadb-convert-table-format
lrwxrwxrwx  1 root root          14 Aug  5 08:54 mysqld_multi -> mariadbd-multi
lrwxrwxrwx  1 root root          13 Aug  5 08:54 mysqld_safe -> mariadbd-safe
lrwxrwxrwx  1 root root          20 Aug  5 08:54 mysqld_safe_helper -> mariadbd-safe-helper
lrwxrwxrwx  1 root root          12 Aug  5 08:54 mysqldump -> mariadb-dump
lrwxrwxrwx  1 root root          16 Aug  5 08:54 mysqldumpslow -> mariadb-dumpslow
lrwxrwxrwx  1 root root          17 Aug  5 08:54 mysql_find_rows -> mariadb-find-rows
lrwxrwxrwx  1 root root          22 Aug  5 08:54 mysql_fix_extensions -> mariadb-fix-extensions
lrwxrwxrwx  1 root root          15 Aug  5 08:54 mysqlhotcopy -> mariadb-hotcopy
lrwxrwxrwx  1 root root          14 Aug  5 08:54 mysqlimport -> mariadb-import
lrwxrwxrwx  1 root root          18 Aug  5 08:54 mysql_install_db -> mariadb-install-db
lrwxrwxrwx  1 root root          13 Aug  5 08:54 mysqloptimize -> mariadb-check
lrwxrwxrwx  1 root root          14 Aug  5 08:54 mysql_plugin -> mariadb-plugin
lrwxrwxrwx  1 root root          13 Aug  5 08:54 mysqlrepair -> mariadb-check
lrwxrwxrwx  1 root root          14 Aug  5 08:54 mysqlreport -> mariadb-report
lrwxrwxrwx  1 root root          27 Aug  5 08:54 mysql_secure_installation -> mariadb-secure-installation
lrwxrwxrwx  1 root root          21 Aug  5 08:54 mysql_setpermission -> mariadb-setpermission
lrwxrwxrwx  1 root root          12 Aug  5 08:54 mysqlshow -> mariadb-show
lrwxrwxrwx  1 root root          12 Aug  5 08:54 mysqlslap -> mariadb-slap
lrwxrwxrwx  1 root root          21 Aug  5 08:54 mysql_tzinfo_to_sql -> mariadb-tzinfo-to-sql
lrwxrwxrwx  1 root root          15 Aug  5 08:54 mysql_upgrade -> mariadb-upgrade
lrwxrwxrwx  1 root root          15 Aug  5 08:54 mysql_waitpid -> mariadb-waitpid
#

So, a current conclusion, might be: Plesk already have this 'change" in hand (see post #3), but it's a big project, so completion won't be anytime soon, unless the aforementioned MariaDB announcement is made, but meantime, there's no consequential, operational setbacks when using Plesk / MariaDB 11.4.*