• 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 python errors

F

frostie

Guest
I'm looking to migrate a bunch of accounts from a redhat 9.0 Plesk 7.0.4 server to a Centos 4.4 Plesk 8.1.1 server. Does anyone know of any issues doing this as I have received some python errors. Will post shortly...

Further info :
New server has Centos 4.4 & Plesk 8.1.1 cleanly installed (i.e. fresh).
The old server has redhat 9.0 & Plesk 7.0.4 .

The ONLY license we have is on the new machine and it is for version 8.1.1 and we don't have the option of updating the old machine to 7.5 or 8.1.1 (because the OS it too old and we don't have a license key for it).
 
Hi,

I would upgrade the old machine to plesk 7.5.4 and downgrade the new machine to 7.5.4 .

ftp://download1.swsoft.com/Plesk/Plesk7.5/RedHat9.0

Then rsync the home folder , the necessary files from /etc/ (passwd, group, the shadow files ) , migrate mysql , rsync mail , the crontabs, maillists.

So far none of these operation need the psa.key.



Then upgrade the new machine to plesk 8.1.1 and you can use the plesk key

Or you could upgrade to 7.5.4 the old server and migrate. I believe that you do not need psa.key on the source machine.

Then correct the errors.
 
That's great thanks. I may well give that solution a try shortly. We'll see how things pan out. I'm currently trying a migration from 7.0.4 to 8.1.1 . Nothing untoward as of yet but who knows ....
 
This is the .py (python) error I appear to be getting when migrating from a 7.0.4 plesk server to a 8.1.1 plesk server. Any thoughts?

Traceback (most recent call last):
File "/usr/local/psa/admin/share/supervisor/processor.py", line 115, in doActivityRunner
newState = self.doActivity()
File "/usr/local/psa/admin/share/supervisor/processor.py", line 400, in doActivity
state = self.translateDump()
File "/usr/local/psa/admin/share/supervisor/processor.py", line 383, in translateDump
cmd.spawn()
File "/usr/local/psa/admin/lib/python/subproc.py", line 238, in spawn
proc.run()
File "/usr/local/psa/admin/lib/python/subproc.py", line 193, in run
BaseSubprocess.run(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 177, in run
self.wait()
File "/usr/local/psa/admin/lib/python/subproc.py", line 197, in wait
BaseSubprocess.wait(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 185, in wait
raise SignalException(self, os.WTERMSIG(status))
SignalException: <unprintable instance object>
 
Back
Top