• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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