Article ID: 114197, created on Jun 25, 2012, last review on Jun 14, 2016

  • Applies to:
  • Plesk 10.x for Linux

Symptoms

Scheduled backups with “Suspend domain until backup task is completed” option does not return domains/aliases back to the original state and incomprehensive error messages are reported (see examples below). The issue is quite sporadic and does not affect all of the domains. It occurs on Parallels Plesk Panel with Postfix mail server.
 
These errors may be shown:
 
1.      <description>Unable to backup Site Builder publishing status on site domain.tld  (ErrorCode: 1, STDOUT:).</description>
 
Even if Web Presence Builder is not used on the server.
 
2.      Fatal error: plesk::Exc<&(plesk::ExecCmd::Failed(bool))>(Execution of postconf -d -h mail_version failed with return code 1.
Stdout is
$features['MailName_SetName'] = true;
... <list of $features goes here> …
$features['Message_Submission_Dedicated_IP'] = false;
forkExecvPipes: execv() failed: No such file or directory
System error 2: No such file or directory
Stderr is
forkExecvPipes: execv() failed: No such file or directory
System error 2: No such file or directory
)
PleskUtilException: /opt/psa/admin/bin/mailmng '--features' failed with message: $features['MailName_SetName'] = true;



Cause

The issue has been fixed in Micro-update #27 for Parallels Plesk Panel 10.4.4. Consider updating/upgrading your installation to get it fixed.

Workaround

If you do not wish to upgrade right now, you may follow the steps below:
 
1. Back up the domains without suspending them. However the error about Parallels Plesk Sitebuilder will still occur in this case.
2. Suspend/Activate any domain in order to set 'mailmng:features' in 'BackendCache' table.
3. Set the PATH to 'postconf' utility for /etc/cron.d/plesk-backup-manager – usually it is /usr/sbin/. You can do that for example by adding this line to the beginning of /etc/cron.d/plesk-backup-manager:
 
PATH=/usr/sbin:/usr/bin:/sbin:/bin


Additional Information

The issue is discussed on the forum as well:
 
Backup error after recent update

dd0611b6086474193d9bf78e2b293040 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838

Email subscription for changes to this article
Save as PDF