Bug 1553700

Summary: Increase max open files to 16384 to align with systemd-journald
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: rsyslogAssignee: Jiří Vymazal <jvymazal>
Status: CLOSED ERRATA QA Contact: Ondrej Moriš <omoris>
Severity: medium Docs Contact: Marie Hornickova <mdolezel>
Priority: medium    
Version: 7.6CC: apmukher, dapospis, dkopecek, jvymazal, mdolezel, mthacker, omoris, pasik, rmetrich
Target Milestone: rcKeywords: EasyFix, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rsyslog-8.24.0-23.el7 Doc Type: Known Issue
Doc Text:
*Rsyslog* cannot proceed if the default maximum of open files is exceeded *Rsyslog* sometimes runs over the default limits for maximum number of open files. Consequently, *rsyslog* cannot open new files. To work around this problem, modify the rsyslog configuration by increasing this limit to align with systemd-journald. To do so, create a drop-in file named `/etc/systemd/system/rsyslog.service.d/increase_nofile_limit.conf` with the following content: [Service] LimitNOFILE=16384
 Story Points: ---
Clone Of:
: 1564054 (view as bug list) Environment:
Last Closed: 2018-10-30 10:17:00 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: 1595781    
Bug Blocks:    

Description Renaud Métrich 2018-03-09 11:00:15 UTC 
Description of problem:

Currently, the default max open files limit for rsyslog is:
soft: 1024
hard: 4096

These numbers are too low because rsyslog connects to the system journal and this can lead to numerous file descriptors be used (see BZ 1550575 and BZ 1540132)

systemd-journald service unit has the following property:
LimitNOFILE=16384

rsyslog service unit should have the same limit set.
Comment 13 Jiří Vymazal 2018-07-23 08:44:21 UTC 
*** Bug 1540132 has been marked as a duplicate of this bug. ***
Comment 32 errata-xmlrpc 2018-10-30 10:17:00 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/RHEA-2018:3135