On Fri, 20 Jul 2012, Nikolaus Rath wrote:
[email protected] writes:
On Fri, 20 Jul 2012, Nikolaus Rath wrote:
*.* /dev/tty8
$ActionQueueType LinkedList
$ActionResumeRetryCount -1
$WorkDirectory /var/cache/rsyslog
$ActionQueueFileName spitzer_queue
*.* :omrelp:spitzer:2514
Now I am getting all the messages on spitzer, but also the boot process
slows down to a crawl. Looking at tty8, I can see that while the first
kernel log messages just rush by, at some point the messages appear very
slowly, at maybe 1 message per second. I suspect that this is what slows
down the booting.
Also, according to lsof, the rsyslog process does not seem to open any
file in /var/cache/rsyslog, even though it has the right permissions.
It's been a while, but I seem to remember seeing rsyslog open and
close the files frequently, so you may not catch them open with lsof.
try running strace against it and log something while the VPN is down
and see if you see files opened and closed.
When I disconnected the VPN and created enough syslog messages, the
files indeed showed up. However, the slowdown that I observe during
system boot did not appear.
Is there anything special about messages from the kernel? Or a way to
get rsyslogd be more verbose about what it's doing and why?
there shouldn't be anything special about kernel messages (they arrive
through a different input, but that shouldn't matter)
if you start rsyslogd with the debug flag it will tell you a LOT about
what it's doing.
The other thing you can try doing is to set the maximum number of messages
that it will queue in memory to some larger value so that it doesn't need
to try to get out to disk for the boot.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
