W dniu 01.06.2012 13:06, Rainer Gerhards pisze:
>>> for x in $(seq 1 1000); do logger "seq:${x} time:$(date +%T)" ; echo
>>> "write_to_exim_log:${x} time:$(date +%T)" >> /var/log/exim/exim_main.log
>>> ; sleep 0.4; done
>>> (Thunderbird wraps lines:/)
>>> After seq:206 rsyslogd stops to write to wszystko.log. I've forgot to
>>> say earlier i'm testing with relp destination unavailable.
>>
>> Ah, OK, that is quite a bit more than a handful of messages. I never tried
>> with
>> that volume.
> OK, this did the trick. I see the same issue. The sleep isn't even necessary.
> The problem is strictly related to a non-responsive RELP server. In that case
> the action queue fills up, and light delay blocking kicks in. However,
> something seems to go wrong with that, and the queue may fill up. Or the real
> cause may simply be that the logger-created messages fill it completely.
>
> Anyhow, now that I can reproduce, I can check the specifics. Thanks for your
> help to getting to this point. Will keep you posted, but it may take me a
> while to figure out what is going wrong.
Sleep was used for convenience of my eyes;)
It's good to hear you can reproduce issue, usual this is problem for me
to create 100% successful testcase.
Thanks,
Marcin
_______________________________________________
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
