• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk Migration 8.3 -> 8.3 doesn't work!

C

CloneCommander

Guest
Hi!

I am trying to migrate from my old Server (Plesk 8.3, SuSE 9.3) to a new one (Plesk 8.3, SuSE 10.2) and I get this error:

Traceback (most recent call last):
File "/usr/local/psa/admin/share/supervisor/processor.py", line 84, in getStatus
return (None, self.realGetStatus())
File "/usr/local/psa/admin/share/supervisor/processor.py", line 255, in realGetStatus
+ "/scout-result.xml").childNodes[0])
File "/usr/lib64/python2.5/xml/dom/minidom.py", line 1913, in parse
return expatbuilder.parse(file)
File "/usr/lib64/python2.5/xml/dom/expatbuilder.py", line 924, in parse
result = builder.parseFile(fp)
File "/usr/lib64/python2.5/xml/dom/expatbuilder.py", line 207, in parseFile
parser.Parse(buffer, 0)
ExpatError: syntax error: line 1, column 2

If I start the Migration manager on the old Server it works... but it's the wrong direction :)

I searched this forum and found many people with the same problem, but nothing worked:

- I recreated /var/lib/psa/dumps/tmp on both servers
- I changed the temporary paths for the migration
- I tried /usr/local/psa/admin/sbin/backup_sign generate on both servers
- I set the mailman master-PW on the new Server

I hope, anyone can help :(

CC
 
LOL.
I found the error: The old server executes 'uptime' on root login - that was too much for the migration manager ^^
 
LOL.
I found the error: The old server executes 'uptime' on root login - that was too much for the migration manager ^^

Hi - what do you mean by this? - I'm experiencing the same exact problem and I'd like to understand properly what you said to try on my server...

Thanks for your time...
 
Hi, sorry for that short answer. I hat the command "uptime" added to /etc/bash.bashrc - so every time i logged in via ssh the output of "uptime" was displayed. That was also executed when PMM logged in, but he dont't expect it, and that caused the error...
maybe you also have something added to this file or /root/.bashrc (or similar)
 
Hi Clonecommander, thanks for replying so quickly. I checked the files but I only have these lines: # .bashrc # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi # User specific aliases and functions I checked under /etc/ and there's
 
And when you login to the Server yo want to migrate from (the "old" server) there is no output except of "Hava a lot of fun... last login from ..." ? Maybe empty the /etc/motd ?!
If that doesn't work I have no idea / you don't have the same problem than me :(
 
Back
Top