• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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