IgorG Plesk addicted! Plesk Certified Professional Mar 15, 2018 #21 The issue has been reported to Atomicorp. In their Helpdesk ticket #10472
frdho New Pleskian Mar 16, 2018 #22 Hello, i'm having the same issue. Is this something I should worry about? Don't really understand what it is. Regards.
Hello, i'm having the same issue. Is this something I should worry about? Don't really understand what it is. Regards.
D derbaumi New Pleskian Mar 20, 2018 #24 trumbaut said: Since the /etc/asl/config file is reset every night (by the /etc/cron.hourly/asl cron), the workarounds above doesn't work. [...] Click to expand... Do you know from where the config is generated? I can't figure it out in the /etc/cron.hourly/asl.
trumbaut said: Since the /etc/asl/config file is reset every night (by the /etc/cron.hourly/asl cron), the workarounds above doesn't work. [...] Click to expand... Do you know from where the config is generated? I can't figure it out in the /etc/cron.hourly/asl.
A Alvaro.H New Pleskian Mar 21, 2018 #26 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.
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.
T trumbaut New Pleskian Mar 21, 2018 #28 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.
frdho New Pleskian Mar 23, 2018 #29 trumbaut said: 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. Click to expand... I'm still having this. How do I fix this? Is there an update needed?
trumbaut said: 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. Click to expand... I'm still having this. How do I fix this? Is there an update needed?
MarkM Golden Pleskian Plesk Guru Mar 24, 2018 #30 frdho said: I'm still having this. How do I fix this? Is there an update needed? Click to expand... I still have it as well; on a 17.5.3 box. Doesn't look like it's fixed to me.
frdho said: I'm still having this. How do I fix this? Is there an update needed? Click to expand... I still have it as well; on a 17.5.3 box. Doesn't look like it's fixed to me.
P pleskpanel Regular Pleskian Mar 27, 2018 #31 Indeed the same issue is still popping up on CentOS 7.4.x systems running 17.5.3 here as well (no manual fix attempted). Looks like the Plesk folks updated their bug report about five hours ago: cron.daily/asl failing with "/usr/bin/find: invalid argument `+' to `-ctime'"
Indeed the same issue is still popping up on CentOS 7.4.x systems running 17.5.3 here as well (no manual fix attempted). Looks like the Plesk folks updated their bug report about five hours ago: cron.daily/asl failing with "/usr/bin/find: invalid argument `+' to `-ctime'"