• 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

pleskbackup stopped working

  • Thread starter Martin Maciaszek
  • Start date
M

Martin Maciaszek

Guest
I'm using Plesk 9.5.2 on my OpenSUSE 11 server and some time ago my backups suddenly stopped working.
The problem boils down to this:
Code:
/[B]usr/local/psa/bin/pleskbackup domains-name maciaszek.net --output-file=/srv/backup_tmp/test.tgz -v --skip-logs[/B]
[lots of lines]
...
Domains [0/1]
-------------- Start print backup log hire --------------
<?xml version="1.0" encoding="UTF-8"?>
  <execution-result status="error">
    <object name="backup" type="backupowner">
      <message severity="error" code="msgtext">The dump have been invalidated by check-dump operation</message>
    </object>
    <object name="backup" type="backupowner">
      <message severity="error" code="msgtext">Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /usr/local/psa/admin/bin/plesk_agent_manager line 658.
</message>
    </object>
  </execution-result>
-------------- End print backup log hire --------------

You can view additional information in the log file located in /usr/local/psa/PMM/sessions/2010-08-09-200305.782 directory. This directory will be removed automatically after 30 days

Runtime error: The backup failed with errors!

When I check the log files I find this in migration.log:
Code:
[20:04:38|INFO:27254:p.log] pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --get-dump-info --dump-file-specification=clients/fastjack/domains/maciaszek.net/backup_maciaszek.net_info_1008092003.xml --session-path=/usr/local/psa/PMM/sessions/2010-08-09-200305.782 --verbose
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps' initialising...
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Initialized
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Get backup info from clients/fastjack/domains/maciaszek.net/backup_maciaszek.net_info_1008092003.xml
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Get initial backup info from dir clients/fastjack/domains/maciaszek.net/.discovered/backup_maciaszek.net_info_1008092003
[20:04:38|INFO:27254:p.log] Get backup params from listing of clients/fastjack/domains/maciaszek.net/.discovered/backup_maciaszek.net_info_1008092003
[20:04:38|INFO:27254:p.log] Read properties from xml clients/fastjack/domains/maciaszek.net/backup_maciaszek.net_info_1008092003.xml
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Validate backup clients/fastjack/domains/maciaszek.net/backup_maciaszek.net_info_1008092003.xml
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Validate backup (common phase) clients/fastjack/domains/maciaszek.net/backup_maciaszek.net_info_1008092003.xml
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Get items 'status' for discovered 'backup_maciaszek.net_info_1008092003' at path clients/fastjack/domains/maciaszek.net
[20:04:38|INFO:27254:p.log] Executing utility: /usr/local/psa/admin/sbin/backup_sign verify /var/lib/psa/dumps/clients/fastjack/domains/maciaszek.net/backup_maciaszek.net_info_1008092003.xml
[20:04:38|INFO:27254:p.log] The utility executed with the return code 0
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Create item 'status_WRONG-FORMAT' for discovered 'backup_maciaszek.net_info_1008092003' at path clients/fastjack/domains/maciaszek.net
[20:04:38|INFO:27254:p.log] Repository '/var/lib/psa/dumps': Put info to clients/fastjack/domains/maciaszek.net/.discovered/backup_maciaszek.net_info_1008092003/status_WRONG-FORMAT
[20:04:38|INFO:27254:p.log] Validate content files backup_fastjack_maciaszek_word_4_1008092003.tgz at dir clients/fastjack/domains/maciaszek.net/databases/fastjack_maciaszek_word_4
[20:04:38|INFO:27254:p.log] Validate content files backup_fastjack_maciaszek_open_5_1008092003.tgz at dir clients/fastjack/domains/maciaszek.net/databases/fastjack_maciaszek_open_5
[20:04:38|INFO:27254:p.log] Validate content files backup_fastjack_maciaszek_git_1_1008092003.tgz at dir clients/fastjack/domains/maciaszek.net/databases/fastjack_maciaszek_git_1
[20:04:38|INFO:27254:p.log] Validate content files backup_fastjack_maciaszek_mint_1_1008092003.tgz at dir clients/fastjack/domains/maciaszek.net/databases/fastjack_maciaszek_mint_1
[20:04:38|INFO:27254:p.log] pmm-ras finished. Exit code: 0

And this in psadump.log:
Code:
18:03:06 INFO  ------------------------------------------------------------
18:03:06 INFO  Migration status reporting initialized.
18:03:06 INFO  Status file: /usr/local/psa/PMM/sessions/2010-08-09-200305.782/dump-status.xml
18:03:06 INFO  ------------------------------------------------------------
18:04:38 ERROR The dump have been invalidated by check-dump operation
18:04:38 ERROR Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /usr/local/psa/admin/bin/plesk_agent_manager line 658.


== STDERR ====================
Odd number of elements in hash assignment at /usr/local/psa/PMM/agents/PleskX/Packer.pm line 4017.
Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /usr/local/psa/admin/bin/plesk_agent_manager line 658.


==============================

I don't know how to fix it but I'm willing to provide additional debugging output to help track the problem down.
 
Odd number of elements in hash assignment at /usr/local/psa/PMM/agents/PleskX/Packer.pm line 4017.

Usually those errors mean that MySQL server either broken connection by timeout or has gone down (was stopped or crashed). You can try to find something related in mysqld.log.
 
I restarted MySQL with a fresh log file. Started the backup process and got nothing in /var/lib/mysql/mysql.log. Just to make sure I checked all tables of all my MySQL databases. Fixed some tables that myisamchk claimed were not properly closed and tried again. Still no cigarr.

I turned on full logging in MySQL and tried again. Didn't see anything out of the ordinary. Just a bunch of "Connect", "Query", "Quit" and some occasional "Init DB". (I won't post that log file here because it's over 1600 lines long and may contain sensitive information)

MySQL seem to be humming along without any problems. Is there anything else I can try to pinpoint the problem?
 
Only mentioned reason is known for me. Detailed investigation directly on your server is required. So, it would be much more effectively if you contact support team.
 
On OpenSuSE 11.1 Plesk 9.52 backup said similar thing and failed:

ERROR Runtime error: The check dump failed with code '1'. The dump can
contain invalid data! at /usr/local/psa/admin/bin/plesk_agent_manager line 658.


== STDERR ====================
/bin/tar: tmp/.chroot_admingmLBxj/
admin.unix: socket ignored

The reason for this was a number of files like:
"<customer's domain>/tmp/.chroot_admingmLBxj/ admin.unix"

I fixed this by running:
0.1) Make sure that file *admin.unix does not match anything else
0.2) Make sure that directory .chroot_admin* does not match anything else
1) cd to vhosts
2) find . -name "*admin.unix" -exec rm {} \;
3) find . -name ".chroot_admin*" -exec rmdir {} \;

After that my backups seemed to succeed.

Regards,
Jari Turkia
 
Ok, I finally figured it out. And it was my fault. I've been meddling with Plesk's internals. I added AAAA DNS records to the database.

I fixed it by adding AAAA to the allowed type of DNS records in the plesk.xsd file.

Of course this wouldn't have been necessary if Plesk supported IPv6 in the first place.
 
Back
Top