RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1772330 - Logrotate fails in mariadb [10.5 stream]
Summary: Logrotate fails in mariadb [10.5 stream]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mariadb
Version: 8.0
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Michal Schorm
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On: 1929348
Blocks: 1861714
TreeView+ depends on / blocked
 
Reported: 2019-11-14 07:41 UTC by Jan ONDREJ
Modified: 2021-05-18 15:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Change of a default configuration for rotating MariaDB log to prevent ocassional errors when using the default configuration.
Clone Of:
Environment:
Last Closed: 2021-05-18 15:55:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan ONDREJ 2019-11-14 07:41:31 UTC
Description of problem:
Consider using "delaycompress" in mariadb logrotate script. Sometimes fails with an error. Reported on CentOS 8.0

Version-Release number of selected component (if applicable):
mariadb-10.3.11-2.module_el8.0.0+35+6f2527ed.x86_64

How reproducible:
sometimes

Steps to Reproduce:
1. just run mairadb

Actual results:
/etc/cron.daily/logrotate:

error: Compressing program wrote following message to stderr when compressing
log /var/log/mariadb/mariadb.log-20191114:
gzip: stdin: file size changed while zipping

Comment 1 Terry Barnaby 2020-08-05 06:25:11 UTC
I am also seeing this on CentOS Linux release 8.2.2004 (Core)

/etc/cron.daily/logrotate:

error: Compressing program wrote following message to stderr when compressing log /var/log/mariadb/mariadb.log-20200805:
gzip: stdin: file size changed while zipping

Comment 3 Jan ONDREJ 2020-12-08 05:51:30 UTC
Please, can you fix this? Adding delaycompress fixes this problem. Also reported for Fedora:

https://bugzilla.redhat.com/show_bug.cgi?id=1683981

Comment 4 Orion Poplawski 2021-02-05 16:33:22 UTC
I'm seeing this as well.  Adding delaycompress seems perfectly reasonable while we wait for upstream fixes.

Comment 5 Michal Schorm 2021-02-18 11:53:13 UTC
Current plan is to incorporate this fix to the new mariadb module 10.5 stream.

Comment 12 errata-xmlrpc 2021-05-18 15:55:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new module: mariadb:10.5), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1893


Note You need to log in before you can comment on or make changes to this bug.