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

Backup Errno 2

keff

Basic Pleskian
Hi,

I've got this error durring backup:

Stacktrace is: Traceback (most recent call last):
File "/opt/psa/admin/share/pmmcli/pmmcli_daemon_actions.py", line 509, in process
action_item.process(logger)
File "/opt/psa/admin/share/pmmcli/pmmcli_daemon_actions.py", line 284, in process
mailsender.send(logger,self.__mail_to,self.__task_type,self.__task_status,self.__owner_guid,self.__owner_type,self.__creation_date,self.__fullname,self.__logfilename)
File "/opt/psa/admin/share/pmmcli/pmmcli_daemon_actions.py", line 245, in send
sendmail = subprocess.Popen(["sendmail",mail_sender,"-t","-oi"], stdin = subprocess.PIPE)
File "subprocess.py", line 543, in __init__
errread, errwrite)
File "subprocess.py", line 975, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

Any Ideas ?
 
Python version is 2.5.2 which seems to be the latest version for debian 5. Would a remove and reinstall have any side effects on a running system?

Plesk version is 9.5.2 so I'm afraid the hotfix won't work.
 
The error seems to be connected to the email notification of the backup of each domain (which does not work for scheduled backup). In case of a manual backup the error does not appear and the email notifications arrive.
 
Back
Top