• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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