• 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 Logrotation not working

Jens Johansson

Basic Pleskian
Server operating system version
CloudLinux 8.10
Plesk version and microupdate number
Plesk Obsidian 18.0.64
Hi,

one of our server is not rotating their logs (maillog, maillog.processed, fail2ban.log, messages, secure, etc.). I made sure that /etc/cron.daily/logrotate is present. rsyslog is installed and active.

To fix the issue I tried to move the file /usr/local/psa/var/logrotate.status and executed /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f ExecuteStatistics But this rotated the logs only once.
 
@JVG Thank you very much that solved the problem. Now that I think of it, it's very obvious, but I didn't check for that.
Yeah, the same thing happened to me, after reviewing every logrotate file and service, finally I checked the cron service and voilá.
 
Back
Top