• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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