• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Migration Manager Error Confixx 3 > Plesk 10.2

K

KaiP

Guest
Hello Forum!

Trying to work with the Migration Manager on a Plesk 10.2 enabled system (300 domains, SpamAssassin) leads to this strange error:

launchpad error Code = 1: [no further explanation]

I have ssh running on a non standart port (which I entered in the MM of course) and got the root user to access the machine.

Any help would be much appreciated since I need to move the system within the next 2 days...

Thanks for any assistance!

Regards

Kai Michael Poppe
 
Hello everyone.

Thanks to the above mentioned KB article i found a log telling me what the problem was:

[15:39:35|INFO:21969:p.log] Launchpad started : /opt/psa/admin/bin/launchpad --send-scout --host=[IPADDRESS] --port=52618 --login=[ROOTLOGIN] --session-path=/opt/psa/PMM/msessions/20110706153935402
[15:39:35|INFO:21969:p.log] OptParsingError[e83ce288-9042-4209-8844-495b61120a67]: Unable to parse command line: port should be a number in [1, 65535] range [./launchpad.cpp:274]
void plesk::verify_options(plesk::config*)
[15:39:35|INFO:21969:p.log] Launchpad finished. Exit code: 1

Obviously there seems to be an error in the command line parsing, since 52618 is well between 1 and 65535... I changed the port of the ssh daemon to standard 22 now the migration is running smoothly. Maybe somebody might want to have a look at the launchpad-bin.

Thanks everyone!
 
Right. Plesk Migration Manager will work correctly only via standard 22 ssh port.
 
... which leaves the question why the migration manager GUI allows the port to be changed in the first place but anyway I changed the port to 22 and it started.

Nevertheless the next error has risen up:

[10:31:13|DEBG:32218:p.Ssh] remote stderr -> 08:31:11 INFO FileFinder: pwd resolved to /bin/pwd
08:31:11 INFO ------------------------------------------------------------
08:31:11 INFO FILE storage initialized.
08:31:11 INFO Base directory: /var/cache/20110707102814554
08:31:11 INFO Gzip bundles: no
08:31:11 INFO Bundle split size: do not split
08:31:11 INFO ------------------------------------------------------------
08:31:11 INFO ------------------------------------------------------------
08:31:11 INFO Migration status reporting initialized.
08:31:11 INFO Status file: /var/cache/20110707102814554/dumping-status.xml
08:31:11 INFO ------------------------------------------------------------
08:31:11 INFO New connection: mysql DBI connection. db confixx, user confixx, host localhost
08:31:11 WARN be6b31eb-7acf-44d6-8436-a9d80039c857 Expected to have exactly one row in result set
Use of uninitialized value $clientSystemDomain in concatenation (.) or string at Agent.pm line 249, <STDIN> line 6.
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 298, <STDIN> line 6.
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 531, <STDIN> line 6.
08:31:12 INFO FileFinder: tar resolved to /bin/tar
08:31:12 INFO Executing bundle producer: '/bin/tar -f - -c -h .' in /tmp/migration_dump_mail
Use of uninitialized value $emailAddress in pattern match (m//) at Agent.pm line 588.
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 697.
08:31:12 INFO FileFinder: idnconv resolved to /usr/bin/idnconv
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 531.
08:31:12 INFO FileFinder: tar resolved to /bin/tar
08:31:12 INFO Executing bundle producer: '/bin/tar -f - -c -h .' in /tmp/migration_dump_mail
Use of uninitialized value $emailAddress in pattern match (m//) at Agent.pm line 588.
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 697.
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 531.
08:31:13 INFO FileFinder: tar resolved to /bin/tar
08:31:13 INFO Executing bundle producer: '/bin/tar -f - -c -h .' in /tmp/migration_dump_mail
Use of uninitialized value $emailAddress in pattern match (m//) at Agent.pm line 588.
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 697.
Use of uninitialized value $domainName in concatenation (.) or string at ContentDumper.pm line 15.
08:31:13 INFO FileFinder: tar resolved to /bin/tar
08:31:13 INFO Executing bundle producer: '/bin/tar -f - -c --anchored -X '/tmp/filemDtETQ' .' in /home/htdocs/web0/html//
Use of uninitialized value $domainName in concatenation (.) or string at Agent.pm line 1146.
'undef' value passed to XmlNode::setAttribute for 'name' at shared_legacy/XmlNode.pm line 103.
at shared_legacy/XmlNode.pm line 103
XmlNode::setAttribute('XmlNode=HASH(0x89944ec)', 'name', undef) called at shared_legacy/XmlNode.pm line 73
XmlNode::_init('XmlNode=HASH(0x89944ec)', 'domain', 'attributes', 'HASH(0x86725c4)', 'children', 'ARRAY(0x8968b74)') called at shared_legacy/XmlNode.pm line 24
XmlNode::new('XmlNode', 'domain', 'attributes', 'HASH(0x86725c4)', 'children', 'ARRAY(0x8968b74)') called at Agent.pm line 251
Agent::_getSystemDomainNode('web0', 'HASH(0x8672694)') called at Agent.pm line 152
Agent::getClient('web0') called at shared_legacy/DumpComposer.pm line 408
DumpComposer::_selectionDumpProcessClient('web0', 'ARRAY(0x88952dc)', 'HASH(0x8776114)', 'HASH(0x87a12ec)') called at shared_legacy/DumpComposer.pm line 276
DumpComposer::_walkTree(undef, 'HASH(0x88db3bc)', 'HASH(0x8776114)', 'HASH(0x87a12ec)') called at shared_legacy/DumpComposer.pm line 274
DumpComposer::_walkTree('HASH(0x87b6694)', 'HASH(0x88db3bc)', 'HASH(0x8776114)', 'HASH(0x87a12ec)') called at shared_legacy/DumpComposer.pm line 274
DumpComposer::_walkTree('HASH(0x889534c)', 'HASH(0x88db3bc)', 'HASH(0x8776114)', 'HASH(0x87a12ec)') called at shared_legacy/DumpComposer.pm line 57
DumpComposer::makeDump('/var/cache/20110707102814554', 'ARRAY(0x87a0efc)', 'ARRAY(0x82b8c64)', 'ARRAY(0x87a0eac)', undef, undef, undef, 1) called at shared_legacy/AgentCLI.pm line 198
AgentCLI::main() called at /var/cache/20110707102814554/Confixx.pl line 17

[10:31:13|DEBG:32218:p.Ssh] Execution finished with return code 9
 
Right. Plesk Migration Manager will work correctly only via standard 22 ssh port.

Sorry, I was wrong. We have ability to define port in Plesk GUI. If it works wrong - you can submit detailed bugreport with this form and I will forward it to developers for investigation.
 
We prepared the following instruction to check if the problem and resolve it or get more information for further investigation:

Execute the following SQL query in Confixx DB:

SELECT * FROM domains WHERE kunde = 'web0' AND richtigedomain = 3;

Note: Credentials for confixx database could be taken from $CONFIXX_INSTALL_DIR/confixx_main.conf (where $CONFIXX_INSTALL_DIR is usually /root/confixx). Please let us know if you need more detailed instructions on how to execute the query, or need other assistance.

- If SQL query returned no records, add missing record by executing the query, and try migration again: INSERT INTO domains (domain, kunde, anbieter, pfad, richtigedomain) VALUES ('web0.tld', 'web0', 'res0', '/', 3);

- Otherwise (If record exists), increase verbosity level:

1. On Plesk box: open /usr/local/psa/PMM/agents/ConfixxX/shared_legacy/AgentCLI.pm file and replace "3" with "5" in
"# set up default verbosity
Logging::setVerbosity(3);"

(please note that there are 2 setVerbosity calls, fix only the last one - with "# set up default verbosity" comment)

2. Run migration in the same way as in previous times, wait for an error.

3. On Plesk box: go to the last session directory in "/usr/local/psa/PMM/msessions/" and find "Expected to have exactly one row in result set" warning.

4. Copy several (20 will be enough) lines of the log before the message here (we're mostly interested in SQL queries).
Providing the whole log is much appreciated, but it completely depends on your privacy policy.
 
Last edited:
Back
Top