• 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.

migration fails with a "NoSuchAttribute" message in the log

M

msc_onoma

Guest
Trying to migrate from cpanel 11 to plesk 8.3

The site has only a simple database and no emails.

All seem fine and the result states that it finished but with errors. The domain is not created and the only error message in the migration log file is a NoSuchAttribute message. My last 2 lines of the migration.log are as follows

[16:14:38|INFO:21575:p.log] NoSuchAttribute: Node migration-dump does not have attribute dump-version [./xml_parse.cpp:238]
[16:14:38|INFO:21575:p.log] deployer finished. Exit code: 0


any hint??
 
Did you manage to figure out what was wrong here? I'm having the same problem.
 
no, nothing... it's obviously a bug. I'll wait in case someone else manages to fix this.

sk
 
same problem here migrating from confixx pro 3.x.
it worked o.k. last week before update to Plesk migration manager Jan 31, 2008

Must be a Bug and I need a workaround or fix asap.

is parallels onto this problem ?
 
Still nobody found a solution ? I really need a urgent fix on this subject !
 
me too! After updating the migration manager the error appeared!
 
If parallels isn't interested in keeping us as customers ...
 
The /usr/local/psa/admin/sbin/deployer file is broken in this update. Parallels support has given me an updated version, but it is too big to attach to this post. PM me and I can send it to you
 
i'm having the same problem... can someone tell me where do I get that deployer?

PS: And why should I pay for something that I already paid for?
 
I'm having the same error.
Will this be fixed in the next plesk version? Will there be an update?

Has anybody used the new deployer-file and does it work?
 
I'm having the same error.
Will this be fixed in the next plesk version? Will there be an update?

Has anybody used the new deployer-file and does it work?

This will be fixed in Plesk 8.4 (arrives in the end of April). The deployer varies from OS to OS, so suitable ones work like a charm.
 
Back
Top