• 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 problem from 8.1 to 8.1 server to server

L

latis

Guest
I recevice the fallowing error while trying to migrate, what should I do?

The XML file /2007-03-19-15.18.40.751864/dump.xml was not parsed successfully with the following errors:
/2007-03-19-15.18.40.751864/dump.xml:68:parsererror :AttValue: ' expected <fpuser name=" ^/2007-03-19-15.18.40.751864/dump.xml:68:parsererror :attributes construct error <fpuser name=" ^/2007-03-19-15.18.40.751864/dump.xml:68:parsererror :Couldn't find end of Start Tag fpuser line 68 <fpuser name=" ^/2007-03-19-15.18.40.751864/dump.xml:68:parsererror :premature end of data in tag phosting line 58 <fpuser name=" ^/2007-03-19-15.18.40.751864/dump.xml:68:parsererror :premature end of data in tag domain line 3 <fpuser name=" ^/2007-03-19-15.18.40.751864/dump.xml:68:parsererror :premature end of data in tag migration-dump line 2 <fpuser name=" ^
 
I have the same error
What is your mysql versions on both servers?
I have v5 on remote and v4.0 on local (where migration fails)

My error:
(...)
/usr/local/psa/PMM/var/2007-05-17-12.18.00.986718/dump.xml:11:parsererror :premature end of data in tag limit line 11 <limit name="disk_space">419430400 ^/usr/local/psa/PMM/var/2007-05-17-12.18.00.986718/dump.xml:11:parsererror :premature end of data in tag domain line 3 <limit name="disk_space">419430400
(...)

I've looked on dump.xml. It has strange (binary?) strings just before "^"

Maybe the problem is on mysql tables structure.

(10 min. later)

You must know, my system was crashed and reinstalled. I took old (from 8.0 and mysql4.1) psa tables to new (8.1 with mysql5) plesk.
I see, there are diffrences bitween binary field type (mysql4 vs mysql5).

I've changed binary field type to varchar(255) - in 2 tables: Limits and Permissions and then I've removed strange binary rests from "value" fields in both tables.
Just like that:
PHP:
<?php
mysql_pconnect("localhost","user","pass");
mysql_select_db("psa");

$z = mysql_query("SELECT `id`,`limit_name`,`value`
                FROM `Limits`");

$tmp = array();
while ($tmp = mysql_fetch_assoc($z)) {
    preg_match('/^\\S*\\d+/',$tmp['value'], $value); // for Limits table
//   preg_match('/^\\w+/',$tmp['value'], $value); // for Permissions table

    echo $tmp['id']." - ".$tmp['limit_name']." : ". $value[0] . " - ";

    mysql_query("UPDATE `Limits` set value='".$value[0]."'
                WHERE `id`='".$tmp['id']."' and `limit_name`='".$tmp['limit_name']."'"); // for Limits table

/*  mysql_query("UPDATE `Permissions` set value='".$value[0]."'
                WHERE `id`='".$tmp['id']."' and `permission`='".$tmp['permission']."'"); */ //for Permissions table

    echo " OK\n";
}
?>

Now migration works fine with 1 exception - mysql tables was not imported, because of diffrences mysql4 vvs mysql5 as plesk wrote me.

Maybe someone knows, why there was binary type of value field?

Regards and Hello - This is my first post ;)
 
Back
Top