Did you keep it running for more than 30 seconds after it has reached the stalled state? From the log, it looks like it were only roughly 9 seconds. As I said, I don'T see any more activity inside the debug log. But maybe it is just hidden.
I suggest you restart the test and then wait for 5 minutes and se what happens. You may want to stop the producer after a few seconds, because messages are still sitting inside the queue and that makes looking at the log easier. Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Steffen Sledz > Sent: Thursday, July 29, 2010 3:18 PM > To: [email protected] > Subject: Re: [rsyslog] Buggy pipe behaviour > > On 07/29/2010 03:07 PM, Rainer Gerhards wrote: > > You set the retry count to -1, that is infinite. So > > messages are never discarded. When nobody is reading > > the pipe, a queue builds up. In the log, the queue > > capacity is simply exhausted. As it looks from the > > log, nobody seems to be reading the pipe, at least > > we consistently get error 11 back from the write API > > call. > > As i wrote before *there is someone reading* the pipe. > > In another shell i run > > while true; do cat /var/run/syslog2thinfs ; done > > Also when i kill and restart the reader the behaviour still is the > same. > > Steffen > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
