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

python error on restoring? check this out...

K

kensavage

Guest
for this site:
http://www.kensavage.com

I get this error when trying to restore my huge 3.1 gig file of 1 website:

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 817, in doActivity
cmd.spawn(os.environ.has_key("PLESKRESTORE_MODE"))
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 187, in wait
raise NonzeroExitException(self, os.WEXITSTATUS(status))
NonzeroExitException: was finished with exit code 1

any ideas what this is or how to fix it?

I also must say that I think I had python installed on this site when I backed it up and now the new rebuilt server did not have python installed. I've since installed python thought 'yum install python' and restarted apache. But I still get the same error.

any help appreciated.
 
ok install python on the new server and it got rid of that error.
 
Back
Top