rsyslogd produces errors and consumes high amount of RAM
Issue
- Why does rsyslogd allocates the huge RAM?
3387 root 20 0 203.4g 199.0g 2.3g S 100.3 79.1 4246:16 rsyslogd
~]# systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-06-27 15:05:26 CEST; 1 weeks 1 days ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 3387 (rsyslogd)
Memory: 196.8G
CGroup: /system.slice/rsyslog.service
└─3387 /usr/sbin/rsyslogd -n
Jul 06 09:28:37 system.local rsyslogd[3387]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Permission denied [v8.24.0 try http://www.rsyslog.com/e/2013 ]
Jul 06 09:28:37 system.local rsyslogd[3387]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Permission denied [v8.24.0 try http://www.rsyslog.com/e/2013 ]
Jul 06 09:28:37 system.local rsyslogd[3387]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Permission denied [v8.24.0 try http://www.rsyslog.com/e/2013 ]
Jul 06 09:28:37 system.local rsyslogd[3387]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Permission denied [v8.24.0 try http://www.rsyslog.com/e/2013 ]
Jul 06 09:28:37 system.local rsyslogd[3387]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Permission denied [v8.24.0 try http://www.rsyslog.com/e/2013 ]
Environment
Red Hat Enterprise Linux 7.5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
