• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Database backup error and doesn't work

zepelin57

Basic Pleskian
Server operating system version
AlmaLinux 8.8
Plesk version and microupdate number
18.0.56
Hi all,
Backups no longer work correctly since the MariaDB 10.6 upgrade:
Code:
WARNING:(Database object 'xxxxxx_') Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: mysqldump: Couldn& execute SHOW FUNCTION STATUS WHERE Db = xxxxx;: Cannot load from mysql.proc. The table is probably corrupted (1728)
WARNING:(Database object 'xxxxxx_') Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: mysqldump: Couldn& execute SHOW FUNCTION STATUS WHERE Db = xxxxxx_;: Cannot load from mysql.proc. The table is probably corrupted (1728)

Do you have a solution to resolve the problem?
Thanks for your help.
 
"repair" is not a shell command, but an SQL command. You first need to open a database shell (e.g. plesk db) then you can run
> repair table mysql.proc;
 
Ok Peter, So I did what you asked in SQL, but I still got the error in the daily report last night.
 
mysql.proc repair status OK for all db.
If I do Check and Repair under Plesk everything is OK for all domains, strange!
 
The problem was resolved :
Code:
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

Thank you so much!
 
Back
Top