• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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