• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Migration error

Chris1

Regular Pleskian
I am trying to migrate a domain from one Plesk server to another but I get the following error:

Code:
 Error:

'NoneType' object has no attribute 'get_dump_status'

How do I fix this issue?
 
Try to remove all files from /usr/local/psa/PMM/tasks/ and start migration again.
 
Hi Igor,

That didn't work unfortunately. I've attached a screenshot that shows some pre-check things, would any of these cause this error?

I've got Dovecot on the new server.

I can't seem to install mod_python. I'm on CentOS 7 if that helps?

EDIT: I've since read that mod_python is not supported on CentOS 7, is this required for the migration manager to work? If so, I might go back to CentOS 6.

Kind regards,
Chris
 

Attachments

  • migration-problem.JPG
    migration-problem.JPG
    87.9 KB · Views: 4
Last edited:
I solved the problem.

I've got a separate disk mounted at /var/lib/psa/dumps and I also changed the location that Plesk stores temporary dump files to var/lib/psa/dumps/tmp.

I thought I had created the "tmp" directory in here but it was missing. I re-created it and attempted the migration again and it succeeded.

It did come up with the follow error after migration:

Code:
Warning:

python is not supported. It will be disabled for the following objects: example.com

Are there any plans for python support?
 
What do you mean? Python is supported for a long time.
 
Yeah, is it worth it being on CentOS 7 at the moment or is better going back to CentOS 6?
 
It's up to you. If these modules are critical for you - use CentOS6. Or just wait when mentioned bug will be fixed for CentOS7.
 
Back
Top