• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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