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

where is the 4:?? crontab?

J

jlang

Guest
Plesk Panel 10.01, CentOS 5/64.

I'm doing my own log processing for my vhosts, swapping the files at 0:00, and so I've disabled that for my virtual domains in Plesk.

Nonetheless, shortly after 4:00 am, it seems that a Plesk cron job is started which somehow issues a reload command to the web server. The result is that the logged accesses between 0:00 and 4:?? for all vhosts are lost.

I've searched everywhere (I think), but I just can't find a crontab that is doing this, not in /etc, not in /usr/.../psa, not anywhere.

Maybe (just maybe) it's the /usr/local/psa/libexec/modules/watchdog/cp/clean-reports job at 3:07, being off by 1 hour, but does this job really reload the http server? Unfortunately, the source code is obfuscated.

So, how and where can I get rid of/edit that 4:?? cron job that messes up my log files?

[edit: forget about the /clean-reports part. I was too eager to find an easy solution and misread the crontab.]

Thanks!
Juergen
 
Last edited by a moderator:
So I thought I might have a workaround: Set the log rotation from "daily" to "size" and select a size that is never reached within a single day. After that, Plesk should leave the log files alone and let me process them the way my clients need it, right? Wrong.

At 4:02 the log files were rotated. All log files. Even those for the two domains which currently have no content at all and hence no traffic.

And yes, I don't allow log administration for the individual domains, and all domains are a following the synchronized default plan which I changed as described above.

Which brings me back to my question: Where is that annoying cron job that messes with my log files every night at 4:02?
 
Back
Top