• 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

Migration Manager and Backup Problems

S

stephhh

Guest
Hi!

I've just updated to Plesk 8 on my Debian 3.1 Sarge System.
At first nothing realy worked (elemts and services were shown as not installed, though the Updater said latest version installed), but after an "apt-get remove drweb-base" and a reistallation of it via Plesk Updater almost everything worked fine.

Now, when i try to migrate Resellers from my old Confixx 3.1 to Plesk with the migration manager, i always get errors concerning mailboxes. No matter with wich reseller i try, it's always the same and the Migration Manager stops.

The errormessage looks like this:
The XML file /opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml was not parsed successfully with the following errors:
/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:72:parsererror :Specification mandate value for attribute cid <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:72:parsererror :attributes construct error <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:72:parsererror :Couldn't find end of Start Tag mailbox line 72 <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:77:parsererror :Specification mandate value for attribute cid <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:77:parsererror :attributes construct error <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:77:parsererror :Couldn't find end of Start Tag mailbox line 77 <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:145:parsererror :Specification mandate value for attribute cid <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:145:parsererror :attributes construct error <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:145:parsererror :Couldn't find end of Start Tag mailbox line 145 <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:208:parsererror :Specification mandate value for attribute cid <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:208:parsererror :attributes construct error <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:208:parsererror :Couldn't find end of Start Tag mailbox line 208 <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:271:parsererror :Specification mandate value for attribute cid <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:271:parsererror :attributes construct error <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:271:parsererror :Couldn't find end of Start Tag mailbox line 271 <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:321:parsererror :Specification mandate value for attribute cid <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:321:parsererror :attributes construct error <mailbox cid type="mbox"/> ^/opt/psa/PMM/var/2006-04-01-13.15.27.419866/dump.xml:321:parsererror :Couldn't find end of Start Tag mailbox line 321 <mailbox cid type="mbox"/> ^

Furthermore i always get an error, when trying to Use the Backup Manager.

The errormessage looks like this:
MySQL query failed: Table 'psa.BackupsRunning' doesn't exist

0: /opt/psa/admin/plib/common_func.php3:229
db_query(string 'SELECT sessionId FROM BackupsRunning WHERE param = 'BackupManagerFactory_client' AND val='1' limit 1')
1: /opt/psa/admin/plib/backup/BackupManagerFactory.php:229
BackupManagerFactoryTable::findByClient(integer '1')
2: /opt/psa/admin/plib/backup/BackupManagerFactory.php:172
BackupManagerFactory::getClientSessionId()
3: /opt/psa/admin/plib/backup/BackupManagerFactory.php:77
BackupManagerFactory->fetchByBackupLevel()
4: /opt/psa/admin/htdocs/backup/main_client.php:16

When installing the Migration Manager via Updater it requires the Backup Tools to be installed at the same time.
And somehow, both of them produce errors, but these errors do not seem to have a relation, as far as i can see.

So, my hope is that anyone here may be able to help me fixing the problems.
Any here, who has any hints for me? *hope*

Regards from Hamburg in Germany

Steph
 
Hi Again!

Ok, after long i've fixed the Backup-Problem manualy.

I was just opening the file /opt/psa/etc/plesk_backup_manager_db.sql and copied the code into PHPmyAdmin.

CREATE TABLE IF NOT EXISTS BackupsRunning (
sessionId varchar(150)
CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL
, param varchar(150)
CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL
, val varchar(255)
CHARACTER SET binary
, PRIMARY KEY (sessionId, param)
) TYPE=InnoDB;

CREATE TABLE IF NOT EXISTS BackupsScheduled (
id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY
, obj_id INT UNSIGNED NOT NULL
, obj_type ENUM('server', 'client', 'domain') NOT NULL
, last DATETIME NOT NULL
, period INT UNSIGNED NOT NULL
, active ENUM('true', 'false') NOT NULL
, processed ENUM('true', 'false') NOT NULL
, files INT NOT NULL
, prefix varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci
, email varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci
, objects INT UNSIGNED
-- REFERENCES BackupObjects(id)
) TYPE=InnoDB;

CREATE TABLE BackupsObjects (
id INT UNSIGNED NOT NULL AUTO_INCREMENT
, obj_id INT UNSIGNED NOT NULL
, obj_type ENUM('client', 'domain') NOT NULL
, PRIMARY KEY (id, obj_id, obj_type)
) TYPE=InnoDB;

... and ERROR!

My MySQL didn't like the "COLLATE utf8_general_ci".
So i removed it and tried it again and....

ERROR! -Once again.

This time MySQL didn't like "CHARACTER SET binary" so i changed "binary" to utf8 and...

SUCCESS!

This time it worked! After that i changed val manually and gave it the attribute "binary" and saved.

After that i tried some Backups and everything seems to work pretty good!

Only the Migration Manager Problem remains...

Greetz from Germany

Steph
 
Seen half-a-dozen such a problems. Please contact support, it always was a bug in migration manager if such symptoms are observed.
 
I have solve this problem, by running this script:
/usr/local/psa/etc/pmm/pmm_db.sql

Code:
-- Main PMM table
CREATE TABLE IF NOT EXISTS PMM (
        sessionId varchar(250) CHARACTER SET binary NOT NULL,
        param     varchar(250) CHARACTER SET ascii COLLATE ascii_general_ci NOT NULL,
        val       varchar(255) CHARACTER SET binary,
        PRIMARY KEY (sessionId, param)
) TYPE=InnoDB;

-- Saved PMM params from last migration session (defaults)
CREATE TABLE IF NOT EXISTS PMMDefault (
        param varchar(255) CHARACTER SET ascii COLLATE ascii_general_ci NOT NULL,
        val   varchar(255) CHARACTER SET binary,
        PRIMARY KEY (param)
) TYPE=InnoDB;
 
Back
Top