Bug 1250184 - Exhausting available inotify watches can result in inability to login
Summary: Exhausting available inotify watches can result in inability to login
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glib2
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-04 16:48 UTC by Matt Newsome
Modified: 2020-12-15 07:35 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:35:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matt Newsome 2015-08-04 16:48:41 UTC
Description of problem:

RHEL7 CSB gdm logins would spin infinitely after password entry, never authenticating the user back in. A symptom was the GUI for the login prompt would lack the word "Password:" when it presented.

Disabling software using lots of inotify watches results in the ability to login again.

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

accountsservice-0.6.35-7.el7.x86_64

How reproducible:

With software maxing out inotify watches, every time.

Steps to Reproduce:
1. Use more inotify watches than the RHEL7 CSB default max
2. Lock GNOME desktop (top right menu -> Lock)
3. Try to authenticate

Actual results:

Spins forever

Expected results:

Authenticates

Additional info:

Adding these lines to /etc/sysctl.d/00-local.conf resolves the issue:

fs.inotify.max_queued_events = 65535
fs.inotify.max_user_instances = 65535
fs.inotify.max_user_watches = 65535

Comment 4 RHEL Program Management 2020-12-15 07:35:49 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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