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

Error migrating standard forwarding domain

P

Paul M

Guest
Migrating from one server to another I get the following error.

Both servers are Linux/Plesk 8.3


Traceback (most recent call last):
File "/usr/local/psa/admin/share/supervisor/processor.py", line 116, in doActivityRunner
newState = self.doActivity()
File "/usr/local/psa/admin/share/supervisor/processor.py", line 550, in doActivity
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>
 
Have boost, glibc or log4cpp been recompiled manually? If they have it may cause the error. I know about just the same issue when the reinstallation of boost solved the problem. Try it.
 
Back
Top