• 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 Cron Job fails

Loonx

New Pleskian
Hello,
I am getting this error every morning:
/etc/cron.daily/logrotate:

error: Compressing program wrote following message to stderr when compressing log /var/log/mariadb/mariadb.log-20201017:
gzip: stdin: file size changed while zipping
Any ideas on how I can fix this?
 
It's not a big issue. It only means that data is still written to the file when gzip is working on it. I have no explanation why this could happen, because once the file as rotated, no changes should go into it, but who knows. Maybe the file was created (space and name reserved) and the system still needs a few seconds or even fractions to fill all the data into it while gzip has already started to compress it. But really, the worst that could happen here with zipping is that the zip archive does not include all data of the file. But it's a log, if a line is missing in that here or there, that's not really a big deal.
 
It's not a big issue. It only means that data is still written to the file when gzip is working on it. I have no explanation why this could happen, because once the file as rotated, no changes should go into it, but who knows. Maybe the file was created (space and name reserved) and the system still needs a few seconds or even fractions to fill all the data into it while gzip has already started to compress it. But really, the worst that could happen here with zipping is that the zip archive does not include all data of the file. But it's a log, if a line is missing in that here or there, that's not really a big deal.
thank you very much!
 
Back
Top