On Thu, 9 Jan 2014, DuyLong Le wrote:
On Thu, 9 Jan 2014, DuyLong Le wrote:
Hi,
Hi,
I didn't get this problem but I've tried with 7.4 or something.
Can you reproduce this problem in isolation (i.e. except for your
production machines)? If you do, then you can:
a) easily check if the bug was fixed in a later version
b) help somebody else reproduce the problem and fix it or maybe even a
workaround for your version.
Very strange, I'm testing with Rsyslog 7.4.8 and my problem is always
present.
setup the impstats module, it will give you far more information about
what's happening.
I tested with impstats, my output :
RabbitMQ logs :
## Start
=INFO REPORT==== 9-Jan-2014::16:41:12 ===
accepting AMQP connection <0.29745.207> (X.X.X.X:33400 -> X.X.X.X:5672)
=ERROR REPORT==== 9-Jan-2014::16:41:12 ===
error on AMQP connection <0.29745.207>: enotconn (socket is not
connected)
=INFO REPORT==== 9-Jan-2014::16:41:38 ===
accepting AMQP connection <0.29904.207> (X.X.X.X:33452 -> X.X.X.X:5672)
=WARNING REPORT==== 9-Jan-2014::16:41:38 ===
closing AMQP connection <0.29904.207> (X.X.X.X:33452 -> X.X.X.X:5672):
connection_closed_abruptly
=INFO REPORT==== 9-Jan-2014::16:41:52 ===
accepting AMQP connection <0.29990.207> (X.X.X.X:52565 -> X.X.X.X:5671)
...
## End
Rsyslog impstats :
## End
...
rabbitmq REPORT==== 9-Jan-2014::16:41:52 ===#012accepting AMQP
connection <0.29990.207> (X.X.X.X:52565 -> X.X.X.X:5671)
rsyslogd-pstats main Q: size=2 enqueued=334 full=0 discarded.full=0
discarded.nf=0 maxqsize=193
rsyslogd-pstats action 1: processed=333 failed=0
rsyslogd-pstats imuxsock: submitted=0 ratelimit.discarded=0
ratelimit.numratelimiters=0
rabbitmq REPORT==== 9-Jan-2014::16:41:52 ===#012accepting AMQP
connection <0.29990.207> (X.X.X.X:52565 -> X.X.X.X:5671)
rsyslogd-pstats main Q: size=2 enqueued=334 full=0 discarded.full=0
discarded.nf=0 maxqsize=193
rsyslogd-pstats action 1: processed=333 failed=0
rsyslogd-pstats imuxsock: submitted=0 ratelimit.discarded=0
ratelimit.numratelimiters=0
rabbitmq 9-Jan-2014::16:41:38 ===#012accepting AMQP connection
<0.29904.207> (X.X.X.X:33452 -> X.X.X.X:5672)
rsyslogd-pstats main Q: size=2 enqueued=330 full=0 discarded.full=0
discarded.nf=0 maxqsize=193
rsyslogd-pstats imuxsock: submitted=0 ratelimit.discarded=0
ratelimit.numratelimiters=0
rsyslogd-pstats action 1: processed=329 failed=0
rsyslogd-pstats imuxsock: submitted=0 ratelimit.discarded=0
ratelimit.numratelimiters=0
rsyslogd-pstats action 1: processed=326 failed=0
rsyslogd-pstats main Q: size=2 enqueued=327 full=0 discarded.full=0
discarded.nf=0 maxqsize=193
rsyslogd-pstats action 1: processed=323 failed=0
rsyslogd-pstats main Q: size=2 enqueued=324 full=0 discarded.full=0
discarded.nf=0 maxqsize=193
rsyslogd-pstats imuxsock: submitted=0 ratelimit.discarded=0
ratelimit.numratelimiters=0
rabbitmq =INFO REPORT==== 9-Jan-2014::16:41:12 ===#012accepting
AMQP connection <0.29745.207> (X.X.X.X:33400 -> X.X.X.X:5672)
## Start
How to understand this output?
k
well, it's harder without the timestamps to properly batch things, but
each set of numbers shows you the state of that component at that time,
so yu can see how many items have arrived in a queue or input, how many
have been processed, and any errors.
In this case, I don't see the input threads that the data is arriving
in. Is this the system running imfile?
Yes, this is the system running imfile. The problem is on the clients. I
have always imuxsock -> action -> main
I observe that the "enqueue" attribute increases, is this normal behavior?
In any case, I don't understand why I have some messages that are
"deleted" (rather not forward) with ReadMode.
Dle
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
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
