Facebook
Twitter
Daerik
New Pleskian
- 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:
I’ve confirmed that /usr/bin/mysql is correctly symlinked to 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.
I’ve confirmed that /usr/bin/mysql is correctly symlinked to 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.
