• 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 failed: Unable to create dump

M

maddes

Guest
Hi,

We are trying to migrate from Plesk 8.6 to Plesk 10.4.4 and we keep getting the following error in psadump.log:
---
10306]: 08:08:56 INFO ------------------------------------------------------------
[10306]: 08:08:56 INFO Migration status reporting initialized.
[10306]: 08:08:56 INFO Status file: /usr/local/psa/PMM/rsessions/20111206090856158/dump-status.xml
[10306]: 08:08:56 INFO ------------------------------------------------------------
[10306]: 08:10:07 ERROR 319718f5-166d-4fc8-8ddc-6294be91e2a2 Unable to create dump:
at /usr/local/psa/PMM/agents/shared/Logging.pm line 84
Logging::error('Unable to create dump', 'fatal') called at /usr/local/psa/admin/bin/plesk_agent_manager line 648
main::__ANON__('Error::Simple=HASH(0x29000d8)', 'SCALAR(0x1c44f80)') called at /usr/lib/perl5/vendor_perl 5.12.1/Error.pm line 339
eval {...} called at /usr/lib/perl5/vendor_perl/5.12.1/Error.pm line 329
Error::subs::run_clauses('HASH(0x20e8948)', 'Can\'t use an undefined value as an ARRAY reference at /usr/l...', undef, 'ARRAY(0x20ff218)') called at /usr/lib/perl5/vendor_perl/5.12.1/Error.pm line 426
Error::subs::try('CODE(0x222db18)', 'HASH(0x20e8948)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 650
main::perform('verbose', 0, 'split-size', undef, 'session-path', '/usr/local/psa/PMM/rsessions/20111206090856158', 'all', 1, 'migration-mode', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1210
main::__ANON__() called at /usr/lib/perl5/vendor_perl/5.12.1/Error.pm line 408
eval {...} called at /usr/lib/perl5/vendor_perl/5.12.1/Error.pm line 407
Error::subs::try('CODE(0x8cac50)', 'HASH(0x8cadb8)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1219
main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1221
----

I've searched through the forums and can't find anything that relates to this issue. What could the problem be and does anyone have any ideas on how we can fix it?

Many thanks
 
restore_response

Hi,

in the File /msessions/restore_response to locate errors:

<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1000</errcode>
<errmsg>PHP Warning: XMLReader::eek:pen ( ): Unable to open source data; File: /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php, Line: 211

Exception: PHP Warning: XMLReader::eek:pen( ): Unable to open source data; File: /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php, Line: 211

file: /usr/local/psa/admin/smb/application/library/Smb/Exception/Syntax.php line: 55 code: 0
trace: #0 [internal function]: Smb_Exception_Syntax::handleError(2, 'XMLReader::eek:pen...', '/usr/local/psa/...', 211, Array)
#1 /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php(211): XMLReader-&gt;open('/usr/local/psa/...')
#2 /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php(51): SpecificationReader-&gt;readStructure()
#3 /usr/local/psa/admin/plib/backup/Conflicts/Detector/ConflictDetector.php(88): SpecificationReader-&gt;__construct('plesk-info', Object(ResourcesDescriptionDoc), '/usr/local/psa/...', Object(SOfRCollection))
#4 /usr/local/psa/admin/plib/backup/Conflicts/ConflictsRunner.php(55): ConflictDetector-&gt;detectConflicts()
#5 /usr/local/psa/admin/plib/backup/Conflicts/Runner.php(13): ConflictsRunner::run(Array)
#6 {main}

PHP Warning: XMLReader::read(): Load Data before trying to read; File: /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php, Line: 213

Exception: PHP Warning: XMLReader::read(): Load Data before trying to read; File: /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php, Line: 213

file: /usr/local/psa/admin/smb/application/library/Smb/Exception/Syntax.php
line: 55
code: 0
trace: #0 [internal function]: Smb_Exception_Syntax::handleError(2, 'XMLReader::read...', '/usr/local/psa/...', 213, Array)
#1 /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php(213): XMLReader-&gt;read()
#2 /usr/local/psa/admin/plib/backup/Conflicts/Detector/SpecificationReader.php(51): SpecificationReader-&gt;readStructure()
#3 /usr/local/psa/admin/plib/backup/Conflicts/Detector/ConflictDetector.php(88): SpecificationReader-&gt;__construct('plesk-info', Object(ResourcesDescriptionDoc), '/usr/local/psa/...', Object(SOfRCollection))
#4 /usr/local/psa/admin/plib/backup/Conflicts/ConflictsRunner.php(55): ConflictDetector-&gt;detectConflicts()

What can i do?
 
I am unable to migrate as well after succesfully migrating 100 domains......
The report_pmm_logs.php doesn't give any output....


[root@ns3 ~]# wget http://kb.parallels.com/Attachments/14954/Attachments/report_pmm_logs.php
--2012-01-04 18:17:28-- http://kb.parallels.com/Attachments/14954/Attachments/report_pmm_logs.php
Resolving kb.parallels.com... 64.131.90.47
Connecting to kb.parallels.com|64.131.90.47|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3938 (3.8K) [application/octet-stream]
Saving to: `report_pmm_logs.php'

100%[==============================================================================>] 3,938 --.-K/s in 0.09s

2012-01-04 18:17:29 (42.2 KB/s) - `report_pmm_logs.php' saved [3938/3938]

[root@ns3 ~]# /usr/local/psa/bin/sw-engine-pleskrun ./report_pmm_logs.php
[root@ns3 ~]#
Click to expand...
 
We're in the middle of a bulk migration...
After about 100 domains it stopped working....

We still need to migrate about 40 domains....

Why isn't there any response?
 
Frater said:
The report_pmm_logs.php doesn't give any output....
Click to expand...

If I understand that script correctly it only creates any output if something fails. The result is dropped in a file named PMM-logs.zip in the current directory.
 
Hi,

in the File /msessions/psdump.log to locate errors...

[19484]: 12:08:32 INFO ------------------------------------------------------------
[19484]: 12:08:32 INFO Migration status reporting initialized.
[19484]: 12:08:32 INFO Status file: /usr/local/psa/PMM/rsessions/20120125130830698/dump-status.xml
[19484]: 12:08:32 INFO ------------------------------------------------------------
[19484]: 12:08:36 ERROR e1470427-1034-497b-8d36-c73177ea3bbe Unable to create dump:
at /usr/local/psa/PMM/agents/shared/Logging.pm line 84
Logging::error('Unable to create dump', 'fatal') called at /usr/local/psa/admin/bin/plesk_agent_manager line 648
main::__ANON__('Error::Simple=HASH(0x22f9268)', 'SCALAR(0x1c4aa28)') called at /usr/lib/perl5/vendor_perl/5.12.3/Error.pm line 339
eval {...} called at /usr/lib/perl5/vendor_perl/5.12.3/Error.pm line 329
Error::subs::run_clauses('HASH(0x21011f8)', '\'undef\' value passed to XmlNode::setAttribute for \'value\'...', undef, 'ARRAY(0x2100a18)') called at /usr/lib/perl5/vendor_perl/5.12.3/Error.pm line 426
Error::subs::try('CODE(0x20faa58)', 'HASH(0x21011f8)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 650
main::perform('verbose', 0, 'split-size', undef, 'session-path', '/usr/local/psa/PMM/rsessions/20120125130830698', 'all', 1, 'migration-mode', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1210
main::__ANON__() called at /usr/lib/perl5/vendor_perl/5.12.3/Error.pm line 408
eval {...} called at /usr/lib/perl5/vendor_perl/5.12.3/Error.pm line 407
Error::subs::try('CODE(0x8ccc50)', 'HASH(0x8ccdb8)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1219
main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1221


What can i do???
 
I wish I knew...

We have to pay each month for a server because we suddenly can't migrate domains anymore...
Most probable due to one of the infamous micro-updates....
 
same line errors like maddes in the psdump.log .

the error protocol in the frontend just said

<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error" log-location="/usr/local/psa/PMM/rsessions/20120126093759719/migration.result">
<message id="3a500bfa-3c9f-4f58-8633-2452dbba5e9e" severity="error" code="fatal">
<description>Unable to create dump</description>
</message>
</execution-result>

regardless of migration one or more domains from Plesk 9.5.4 (SLES 10.1) to 10.4.4 Update #13 (OSS 11.4), both 64 bit.
 
Come on Parallels!

This is a serious issue and there's not even attempt to get it fixed.

Plesk-Plesk Migration isn't something that's being done by many users but it is something we should be able to rely on.
Generic (non-plesk) stuff is something I could troubleshoot, but this isn't.
Especially because I'm not owning the original Plesk server and I have to rely on a third party for this.

The only thing I can do right now is to ask them each week if they're able to migrate a domain in the hope some micro-update fixed it. I wish this micro-update wasn't turned on at all... I don't know why it happens.

We need to transfer only 1 domain from a Plesk 8.5 server and about 50 from a 9.5 server.

Tell us at least what we can check.
 
IgorG said:
Why you do not ask free migration assistance here - http://www.parallels.com/support/plesk/free10assistance_toc/ ?
Click to expand...

Igor,

I followed your suggestion, I got free migration assistence and it seems the issue is now resolved.
I'm saying "it seems" as I'm not the admin of the source server and can't initiate the migration myself.

The migration engine is dependent of perl.

For my SMTP-proxy (ASSP) I needed to upgrade my perl installation in the past.
It turned out the DBD::mysql module was missing from this Perl.5.14.2 installation and couldn't be added because it failed to compile. It failed to compile because my CentOS was missing the mysql-devel installation.

After installing mysql-devel with the command:
yum install mysql-devel.x86_64
Click to expand...

I was able to install DBD::mysql
perl -MCPAN -e 'install DBD::mysql'
Click to expand...

This was however only half the issue.
The support team discovered a problem which they reported to the development team.
The ID of the issue is '96819'
I assume this will soon be fixed now.

My PleskX.pm got patched.
It will probably soon be fixed with a micro-update.

# cd /usr/local/psa/PMM/agents/PleskX
# diff PleskX.pm.orig PleskX.pm
47d46
<
2514a2514
> my @tmplData;
2515a2516,2520
> my @tmplElem = @{$ptrRow};
> push @tmplData, \@tmplElem;
> }
>
> foreach my $ptrRow (@tmplData) {
7234a7240
>
Click to expand...
 
migration problem on openSUSE 11.4 (x86_64)

I got a reply too ,that solves the migration problem on openSUSE 11.4 (x86_64)

same as above perl-DBD-mysql was not installed by the one-click-installer and autoinstaller

zypper install perl-DBD-mysql
Click to expand...

no restart of psa needed, migration was successfull. Thanks PLESK Support!
 
You must log in or register to reply here.

Similar threads

P
Issue Plesk Migrator does not copy databases from DirectAdmin.
Replies
3
Views
890
peter21581
P
M
Resolved Unable to access Backup manager
Replies
3
Views
996
moussaelhajraoui@gmai
M
N
Resolved Urgent - Failed Backup Restore
Replies
12
Views
1K
NITROFOX
N
M
Issue File dump-header not found on first position in archive.
Replies
0
Views
749
massin
M
K
Issue Plesk Migrator can't handle umlaut domain names properly
Replies
0
Views
599
kassi
K
Back
Top