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 1182614 - Logs full of: error: gio_poll_dispatch_update: Adaptor for descriptor 8 is not in-use
Summary: Logs full of: error: gio_poll_dispatch_update: Adaptor for descriptor 8 ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Andrew Beekhof
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-15 14:54 UTC by Jaroslav Kortus
Modified: 2015-11-19 12:12 UTC (History)
3 users (show)

Fixed In Version: pacemaker-1.1.13-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 12:12:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2383 0 normal SHIPPED_LIVE Moderate: pacemaker security, bug fix, and enhancement update 2015-11-19 10:49:49 UTC

Description Jaroslav Kortus 2015-01-15 14:54:57 UTC 
Description of problem:
After I created 300 resources in a cluster and then deleted them via cibadmin --replace quote from manpage for <resources/> the cluster started to be really busy. As it's on relatively weak virts, it was hogging up CPU quite heavily and that lead to some timeouts. In the end the cluster recovered well, but the interim messages filled up the syslog (and caused journald to sweat heavily too).

While systemd-journald filtered these messages out (like "suppressed 50000 messages"), the file /var/log/pacemaker.log did not have such luck and filled up the drive completely with messages like:

Jan 14 20:27:27 [21120] virt-084.cluster-qe.lab.eng.brq.redhat.com       lrmd:    error: gio_poll_dispatch_update:      Adaptor for descriptor 8 is not in-use

[root@virt-084 log]# grep "Adaptor for descriptor 8 is not in-use" pacemaker.log | wc -l
33327376

These log messages should be limited (or log size in general, or something that will prevent the disk filling up).

Version-Release number of selected component (if applicable):
pacemaker-1.1.12-15.el7.x86_64

How reproducible:
did it once

Steps to Reproduce:
1. for i in `seq -w 1 300`; do echo "Creating $i"; pcs resource create dummy$i ocf:heartbeat:Dummy; done
2. cibadmin --replace --scope resources --xml-text '<resources/>'
3.

Actual results:
logs get spammed as described above. The weaker the HW running it on, the more it will probably be

Expected results:
Log messages limited if they are directed to other targets than syslog (where it does the suppression automatically)

Additional info:
Comment 2 Andrew Beekhof 2015-01-16 03:09:55 UTC 
David: I've never seen this in any of my CTS runs... has something changed in libqb recently?

Sounds like you're asking for log compression too, which would be best implemented as a  feature for libqb.
Comment 3 David Vossel 2015-01-16 17:13:33 UTC 
(In reply to Andrew Beekhof from comment #2)
> David: I've never seen this in any of my CTS runs... has something changed
> in libqb recently?

I have not seen this. It must correlate to load.

> Sounds like you're asking for log compression too, which would be best
> implemented as a  feature for libqb.
Comment 4 David Vossel 2015-04-30 17:15:49 UTC 
(In reply to David Vossel from comment #3)
> (In reply to Andrew Beekhof from comment #2)
> > David: I've never seen this in any of my CTS runs... has something changed
> > in libqb recently?
> 
> I have not seen this. It must correlate to load.
> 
> > Sounds like you're asking for log compression too, which would be best
> > implemented as a  feature for libqb.

I actually know what causes this now. Under load, it's possible that libqb will have to start queuing events to be sent out later because internal send buffers are full. When this occurs, libqb uses the poll modify callback to start watching for the POLLOUT events in order to know when the fd is available for writes again.

Now, here's the problem. Pacemaker's usage of glib's mainloop has a race condition in the poll's modify function that causes the fd to be marked as "unused" even though it is actually still in use.

This patch to pacemaker should resolve this issue.
https://github.com/davidvossel/pacemaker/commit/0178380549fbff35b3de919db898d4b2d27e23d2

-- David
Comment 6 Jaroslav Kortus 2015-09-14 19:32:35 UTC 
Retested with pacemaker-1.1.13-6.el7.x86_64, the messages are gone.
Comment 7 errata-xmlrpc 2015-11-19 12:12:24 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://rhn.redhat.com/errata/RHSA-2015-2383.html
Note You need to log in before you can comment on or make changes to this bug.