• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Migration Error

pould

Basic Pleskian
Trying to conduct a migration from one Plesk server to another and keep coming up with this error:

Traceback (most recent call last):
File "/opt/psa/admin/share/supervisor/processor.py", line 84, in getStatus
return (None, self.realGetStatus())
File "/opt/psa/admin/share/supervisor/processor.py", line 541, in realGetStatus
return getRunningAgentState(self.session)
File "/opt/psa/admin/share/supervisor/processor.py", line 497, in getRunningAgentState
d = minidom.parseString(content)
File "/usr/lib/python2.4/xml/dom/minidom.py", line 1925, in parseString
return expatbuilder.parseString(string)
File "/usr/lib/python2.4/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
File "/usr/lib/python2.4/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
ExpatError: no element found: line 1, column 0

Any ideas?
 
Hi
What is the Plesk version and OS on the destination server? At the moment it is not possible to say anything certain, could you please post here a piece of migration.log? Seach it in /usr/local/psa/PMM/var/
 
Back
Top