• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Backup failed: pmm utility 'PMMCli' raised an exception. Error code is: -9

DLM

New Pleskian
Hello,

all backups under Plesk Onxy failed. Error: pmm utility 'PMMCli' raised an exception. Error code is: -9

Thanks for you help!

Daniel
 
Hello, Daniel.
Could you please provide more details about the error from '/var/log/plesk/PMM/pmmcli.log'
 
Could you try to run following command:
Code:
/usr/bin/perl /opt/psa/admin/bin/plesk_agent_manager server --get-size --incremental --session-path=/opt/psa/PMM/sessions/2016-11-01-092159.326 < /dev/null
 
DBD::mysql::st execute failed: Table 'performance_schema.session_variables' doesn't exist at /opt/psa/PMM/agents/shared/Db/MysqlDbiBackend.pm line 69.
 
It looks like broken MySQL installation. Could you please run following command and then re-run backup:
Code:
mysql_upgrade --user=admin --password=`cat /etc/psa/.psa.shadow` --force --verbose
 
Hey Sergey,

this helps a little bit! Thanks! The backup was created, but I received the message that there are some problems. For more information see the file attached.
 

Attachments

  • task-390.log
    4.8 KB · Views: 7
Have you tried to restart mysql after mysql_upgrade? It is required in this case.

It seems Plesk db has some broken references. Could you please run following commands (after restart mysql):
Code:
plesk db "UPDATE domains SET displayName = name WHERE displayName IS NULL OR displayName = '';"

plesk bin repair --db
The first fixes inconsistency between name and displayName in psa.domains tablse. The second one checks Plesk DB for a lot of other inconsistencies and tries to fix them in interactive mode.
 
Last edited:
Back
Top