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

Resolved Frequency of Log File Rotation

Quotes

New Pleskian
How do I check/change the scheduled task relating to processing the log file rotation?

I already know how to update the log file rotation settings for each subscription (e.g. by size, daily, weekly, how many to retain, etc). What I don’t know is how to run the maintenance script that carries out the actual log file processing, and see if I can increase the frequency the log files are processed.
 
Thank you IgorG, that is almost what I wanted, although that solution is for a specific domain, and I want something to run server-wide.

I am trying to deal with sudden bursts in log file size due to brute force attacks. I am also considering move log files to a separate disk although if that fills up I don’t know if Apache would continue to run if it can’t create a log file properly.
 
I found this article which runs a different script to rotate logs for the whole server - How to force Plesk to rotate logs more often on Linux

However, I think that what is needed is an auto-rotate feature when logs reach an exceptional size. The settings currently allow for rotation over a filesize of choice but that is rather useless during a brute force attack (in my case 14GB error log generated in 30 minutes). The process needs to be more nimble. I will put this forward as a suggestion.
 
Back
Top