• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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