Bug 1446095

Summary:	"systemd-analyze dump" fails with "Failed issue method call: No buffer space available"
Product:	Red Hat Enterprise Linux 7	Reporter:	Renaud Métrich <rmetrich>
Component:	systemd	Assignee:	David Tardon <dtardon>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	dtardon, fsumsal, systemd-maint-list, tonay, zpytela
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-219-58.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 11:32:12 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:
Bug Blocks:	1549617, 1551061

Description Renaud Métrich 2017-04-27 09:06:31 UTC

Description of problem:

On a large system (+1200 device units) "systemd-analyze dump" fails with the "Failed issue method call: No buffer space available" error.

# systemd-analyze dump
Failed issue method call: No buffer space available

Version-Release number of selected component (if applicable):

systemd-219-30.el7_3.6.x86_64

How reproducible:

ALWAYS

Steps to Reproduce:

didn't try

Additional info:

Other systemd-analyze commands work perfectly

Comment 7 David Tardon 2018-05-09 07:44:02 UTC

This hits the defined DBus message size limit--64 MiB. We could increase that, but not by much, as the max. message size allowed by DBus spec is 128 MiB (and the max. size can be also limited by dbus daemon). What's needed is to pass the dump data via a different channel.

Comment 9 David Tardon 2018-05-15 10:24:57 UTC

https://github.com/lnykryn/systemd-rhel/pull/205

Comment 11 Lukáš Nykrýn 2018-06-14 07:52:52 UTC

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/205 -> post

Comment 15 errata-xmlrpc 2018-10-30 11:32:12 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, 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/RHBA-2018:3245