• 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 Manager Not Working Now

A

artm

Guest
Oh dear... Nothing seems to work properly any more.

Now the Migration Manager is screwing up following the latest Plesk "updates" (I would rather call them "downdates").

Migrating a site form Plesk 5 I get:

19:01:47 INFO Dumping domain mailsystem
19:01:47 TRACE SQL: SELECT id, password, 'plain' FROM mail WHERE dom_id=13 ORDER BY mail_name
19:01:47 TRACE SQL: SELECT * FROM mail WHERE id = 11
'undef' value passed to XmlNode::addAttribute for 'allowed' at XmlNode.pm line 61, <STDIN> line 1.

Migrating sites from this server worked perfectly well before. Now I can't do it for any site.

Oh, misery!

:mad:
 
same problem, no solution yet. working on it now. need to migrate two servers fast!
 
Originally posted by are_eye_see_kay
same problem, no solution yet. working on it now. need to migrate two servers fast!

I don't remember if this was the fix for this problem but simply removing tomcat4 (or tomcat5) it began to work... it's a terrible workaround I know

on a RHEL system I did:

yum remove tomcat4
(you may have to do tomcat5 depending on your system)
 
Tried removing tomcat, and restarting plesk, still got the same problem. It's got something to do with the way it's handling XmlNode.pm. I don't think I can kill that feature in the migration utility without breaking something. If you remember what it was, let me know.

Thanks!
 
Back
Top