• 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.

cron.daily/asl failing with "/usr/bin/find: invalid argument `+' to `-ctime'"

The issue has been reported to Atomicorp.
In their Helpdesk ticket #10472
 
Hello,

i'm having the same issue. Is this something I should worry about? Don't really understand what it is.

Regards.
 
Hello, I would like to know if there are new news about the case

I have the same problem but when I went to check the file /etc/cron.daily/asl I already had the line

grep PURGE_LOGS asl

if [["$ PURGE_LOGS"! = "no"]]; then
DAYS = $ PURGE_LOGS

does that mean that the file has already been updated and therefore the problem has already been solved?

Thanks in advance.

A greeting.
 
Issue should be fixed in the meanwhile: the /etc/asl/config file (which is updated by cron every night) now contains the PURGE_LOGS variable:

Code:
PURGE_LOGS="no"

So even without any workaround all should go fine again for now.
 
Issue should be fixed in the meanwhile: the /etc/asl/config file (which is updated by cron every night) now contains the PURGE_LOGS variable:

Code:
PURGE_LOGS="no"

So even without any workaround all should go fine again for now.

I'm still having this. How do I fix this? Is there an update needed?
 
Back
Top