Bug 1772330

Summary:	Logrotate fails in mariadb [10.5 stream]
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan ONDREJ <ondrejj>
Component:	mariadb	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Zachar <lzachar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	databases-maint, hhorak, jcsible, orion, rbedia, terry1
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 15:55:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1929348
Bug Blocks:	1861714

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