• 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.

Migration 9.5 to 10.3.1 fails

C

christoph_peter

Guest
I try to migrate a reseller account from 9.5 to 10.3.1 - I do not have root access to the source server. I created a backup via the web interace. uploaded it the new server via the backup manager or directly via ssh. I used this

http://kb.parallels.com/en/9578 to convert the backup.

usr/local/psa/admin/bin/pmm-ras --import-file-as-dump --dump-file-specification=./backup_c.peter_info_1112121210.xml.tgz --dump-storage=/var/lib/psa/dumps/ --guid=00000000-0000-0000-0000-000000000000 --type=server --session-path=/usr/local/psa/PMM/logs
resellers/c.peter/backup_c.peter_info_1112121210.xml

when restoring the backup it fails with the following error:

ERROR: () Failed validation of the document with its internal DTD. The errors are: Element 'preferences': This element is not expected. Expected is ( limits-and-permissions )

any ideas on how to fix this?
 
There is database inconsistency which can be fixed manually in database. There is similar problem described in KB article http://kb.parallels.com/9343 You can try to locate and fix this problem in Plesk database. Contact Parallels Support Team if you can't do it by yourself.
 
Thanks for the info, the article addresses two other specific issues, but without knowing the exact query to run against the database I can't really do anything. Also as I said before, I don't have root access to the Server / Plesk installation. Is there a way I can get more detailed info on the fix so I can pass it on to my provider?
 
Back
Top