Thanks Rainer!! Rainer Gerhards wrote: >> Rainer Gerhards wrote: >> >>> Used the wrong words ;) Of course, this should read: >>> >>> Sure, but let me phrase it that way: My interest is finding bugs, >>> >> support >> >>> questions often lead to that. If there is no bug involved, my >>> >> personal >> >>> interest in support is *extremely limited*. Still, there is the rest >>> >> of >> >>> the community, and they often provide advice. So Adiscon created the >>> commercial support for corporations that want to have a solution and >>> >> save >> >>> time while doing so. >>> >>> And: why is my interest limited? Support to get someone else going >>> contributes almost nothing back to the project... >>> >>> >> Im going to make probes with deleting the config line EST=... >> >> When we have coclusion I will tell you, and I will back my concluison >> to >> this magic project. :) >> > > I have taken another look at the log files in the meantime, assuming that > $EST were not present ;) However, I do not see anything obviously wrong. But > I think I remember there was a condition that caused messages to be processed > to slowly. Probably the best idea is to see if the issue persists with the > current v3-stable release. If it does, we should go to v4 and if it still > persists we need to obtain debug logs. But I think chances are extremely high > that the current v3-stable will solve it. > > however, those forwarding rules to $EST can never have worked, and may > actually be overruning the retry mechanism after a while... > > Rainer > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com >
-- Mikel Jimenez Fernandez Irontec, Internet y Sistemas sobre GNU/LinuX - http://www.irontec.com +34 94.404.81.82 _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
