On 05/22/2012 05:21 PM, Juan Jose Pavlik wrote:
I'm running OpenSuSE 12.1 and that's the rsyslog version that comes with
it, i don't like using software out of the repositories. What version
should i try??? I've heard something about bugs in this version..., this is
a good start.

The current v5 stable is 5.8.11, as shown here
http://www.rsyslog.com/project-status/

I thought that too, that's way i dissabled the database writing (the db is
in a remote server), i don't think that the other rsyslog is the one
slowing it down. Maybe is a network problem...?

Maybe. I would be helpful to have more information to narrow the diagnosis. You can look into the output from the debugging mode (-d option), but I'm not sure if it would be feasible to turn it on with this volume of data. You can have a look here:
http://www.rsyslog.com/doc/debug.html

Stops completely or just writes them incredibly slowly?

It writes them incredibly slow, right.

You can try to decrease the timeouts, as metioned bellow, even for the main queue. This comes at the price of loosing messages, but at least it should keep running.

Dropping is a default action in case of congestion, do you really see some
misbehavior?


What i see is (i've munin graphs of the server):

-disk writing goes down, to almost zero.
-rsyslog queues starts to grow dramatically fast.

OK, this could be due to the rate limiting of the inputs.

Any particular size of a queue (or available ram) is finite. If you can
identify the output that blocks the processing, put it in a separate queue
and configure enqueuing to have a short timeout. This should mitigate the
issue to some degree, not to be an ideal solution.

How can i identify the blocking proccess? any idea?

A crude solution would be add queues to all of them and look at the pstats output as the one you've provided.

Tomas
_______________________________________________
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

Reply via email to