Bug 1751822

Summary:	rsync failing with out of memory in flist_expand
Product:	Red Hat Enterprise Linux 7	Reporter:	Darryl B <darryl.baker>
Component:	rsync	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.8
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-06 16:07:01 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:

Description Darryl B 2019-09-12 16:18:55 UTC

Description of problem:
rsync fails with "error allocating core memory buffers"

Version-Release number of selected component (if applicable):
rsync.x86_64                       3.1.2-6.el7_6.1

How reproducible:
Very reproducible (for me)

Steps to Reproduce:
1. run rsync frequently on large data sets. 
This issue appears unrelated to the amount of data transferred but rather to the size of dataset inspected.
2.
3.

Actual results:
ERROR: out of memory in flist_expand [sender]
rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]
rsync: [generator] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(820) [generator=3.1.2]

Expected results:


Additional info:
I found that there was a very similar issue with rsync on AIX with the same version of rsync. Since rsync is an integral part of a very critical application I was able to remediate by compiling rsync 3.1.3 from source and replacing the binaries on both sides of the transfer. The appearance of a memory issue in the message is misleading the problem continued after adding 2GB more memory to both servers involved in the transaction. The problem started after our latest patch cycle.

Comment 2 Tomáš Hozza 2019-12-06 16:06:48 UTC

Red Hat Enterprise Linux version 7 entered the Maintenance Support 1 Phase in August 2019. In this phase only qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. Other errata advisories may be delivered as appropriate.

This bug has been reviewed by Support and Engineering representative and does not meet the inclusion criteria for Maintenance Support 1 Phase. If this issue still exists in newer major version of Red Hat Enterprise Linux, it has been cloned there and work will continue in the cloned bug.

For more information about Red Hat Enterprise Linux Lifecycle, please see https://access.redhat.com/support/policy/updates/errata/

Comment 3 RHEL Program Management 2019-12-06 16:07:01 UTC

Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain  the issue receives the proper prioritization with product and development management.

https://www.redhat.com/support/process/production/#howto