Red Hat Bugzilla – Bug 46545
minilogd eats all available memory
Last modified: 2014-03-16 22:21:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607
Description of problem:
On several occaisions i've seen minilogd (belongs to initscritps.x-x.rpm)
use as much as 260mb ram.. The box then enters "swap hell".. and the only
thing to do is press the reset button.
when the problem occurs i'm usually running Gnome + a few gterms, samba-2.2
(rebuilt from srpm with --target=i586) and sshd.
Is syslogd running?
minilogd did have a memory cap added to it before 7.1; what version of initscripts
are you running?
yes.. syslogd is running, and the version of the initscripts is 5.83-1
[root@chantry /root]# ps ax | grep syslogd
423 ? S 0:00 syslogd -m 0
1032 pts/0 S 0:00 grep syslogd
[root@chantry /root]# rpm -qa | grep initscripts
syslogd is running at the same time as minilogd? this is *odd*.
Okay, I was having the same problem.
minilogd sends kernel information that is logged to syslogd. If syslogd isn't
running, minilogd can't send it anywhere so it just queue's it up. The queue
is in memory.
If syslog isn't running you will have a problem. Once you start syslog, it
will take some time for minilog to send all the info to syslog. At that point,
minilogd will free memory.
If you don't care about loosing the contents of the kernel log, restarting the
box will free the memory :-)
Do the following to check if syslog is set to run on reboot:
/sbin/chkconfig --list syslog
syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off
If it isn't set to run on reboot or dies at some point the problem will come
Closing out bugs on older, no longer supported releases. Apologies for any lack
of response. Please reopen if it persists on current releases.