• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Email Piping for WHMCS

G

Gary Spires

Guest
Hi

I'm trying to set up Email piping for WHMCS support tickets. However when I set the cron job in Plesk I get the following errors.

ERROR: PleskFatalException

Crontab->export() failed: crontabmng failed:
crontabmng syntax:
get <username>
to show crontab of <username>
set <username> <filename>
to set crontab of <username> from <filename>
allow <username>
to allow crontab of <username>
deny <username>
to deny crontab of <username>
remove <username>
to remove crontab of <username>
rename <username> <newusername>
to rename crontab of <username> to <newusername>
System error: crontab execution error

0: CrontabTaskPropertiesUIPointer.php:81
CrontabTaskPropertiesUIPointer->accessItem(string 'POST', NULL null)
1: UIPointer.php:596
UIPointer->access(string 'POST')
2: plesk.php:38

Any ideas how to solve this.

Thanks

Gary
 
Seems that '@'-aliases in crontab cause Plesk to throw exception on adding new task. We have already submitted bug regarding this problem. I have updated it with your problem/ I hope it will be fixed soon.
 
Many thanks for quick reply.

Is this update due soon? As the other option of email piping does not work either.

Regards

Gary
 
Hello.

I think i have the same problem.

ERROR: PleskFatalException




Crontab->export() failed: crontabmng failed:
crontabmng syntax:
get <username>
to show crontab of <username>
set <username> <filename>
to set crontab of <username> from <filename>
allow <username>
to allow crontab of <username>
deny <username>
to deny crontab of <username>
remove <username>
to remove crontab of <username>
rename <username> <newusername>
to rename crontab of <username> to <newusername>
System error: crontab execution error
0: CrontabTaskPropertiesUIPointer.php:81
CrontabTaskPropertiesUIPointer->accessItem(string 'POST', NULL null)
1: UIPointer.php:596
UIPointer->access(string 'POST')
2: plesk.php:38

Is there any patch available to fix the problem?

thanks beforehand.
 
The cause of the issue is that Plesk does not work well with crontab time "aliases" -- @weekly, @daily, @reboot and so on. As workaround I suggest you to avoid using '@'-aliases in crontabs.
 
Back
Top