• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Cannot restore, unknown error code from backup_sign utility

S

stoilis

Guest
Hi,

I am using Plesk 8.2.1 on Debian etch, using the latest updates on anything.

While trying to create a map file on a new server for restoration, I get the following error:

# pleskrestore --create-map backupfile -map map
Can't check backup file: unknown error code from backup_sign utility: 255
#

The error appears only after a while, about an hour of processing the backup file.

What is probably useful to mention, is that my backup is split at 2GB chunks. So, backupfile is just the first one, the whole list being:
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:04 backupfile
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:09 backupfile.001
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:14 backupfile.002
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:19 backupfile.003
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:24 backupfile.004
-rw-r--r-- 1 root root 1173101133 2007-10-23 14:26 backupfile.005

Any hint on how to proceed to restoration?

Thank you in advance.
 
You should consider this as per SWSoft Knowledgebase article:

http://kb.swsoft.com/en/2279

RESOLUTION
Such error can be caused by missing certificate for backup signing. Try to generate the certificate with the command:

# $PRODUCT_ROOT_D/admin/sbin/backup_sign generate

Our symptoms were different. We got:

backup_sign: Can't find private key in database:
backup_sign: Can't get server's private key
23:17:23 ERROR Failed to create MIME message

Our backups were still completed, and the normal sizes were there, and even looking at the file it seemed intact, but every time we tried to create a map or restore something we got a backup corrupted message. The above Knowledgebase article sorted us out!
 
I solved the problem by generating the map file on the original server. There, it could be generated without a problem.
 
Back
Top