• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Crontabmng error after migration

GPDCenter

New Pleskian
Hi all,

we successfully migrated web and email from a Plesk 9.3 system to the new Plesk 12.0 system.
Afterwards i try to install new extensions and / or try to delete existing extensions and receive the following error

Die Erweiterung Webserver Configurations Troubleshooter kann nicht entfernt werden: crontabmng failed: /usr/bin/crontab execution failed: "crontabViWP46":11: bad command errors in crontab file, can't install. System error: crontab execution error

Means that i am not able to delete the extension "Webserver Configurations Troubleshooter". But the extension is delete (but not completelly - only a checkbox is shown without entry).

Is something comes with a config of the old server? All works proper until migration.

Thanks in advance for your help
 
You will need to open the crontab file with
Code:
crontab -e
and in it find any bad commands and either put a # before them or delete them.
 
Back
Top