On Wed, Feb 17, 2016 at 11:01 AM, David Lang <[email protected]> wrote:
> On Wed, 17 Feb 2016, helices wrote:
>
>> 1) What do I gain by moving to the newer rsyslog.conf?
>>
>
> lots of bugfixes, lots of speed improvements, lots of new features
>
> but I thought you had already upgraded to 8.16, what version are you
> running.
>
I did the following, which did NOT change /etc/rsyslog.conf:
yum update rsyslog
> 2) If I change to the new rsyslog.conf, how can I test this on this
>> production server, _without_ losing and events that must be forwarded to
>> DB?
>>
>
> Ok, then I'm not clear which rsyslog.conf you are running, the original
> one or the default one?
>
See above
3) Yes, under other conditions, I would love to start from scratch, and
>> build the new rsyslog.conf through trial and error. I cannot do that on
>> this production server. I hoped that both of these brief and short
>> rsyslog.conf files would readily lend itself to experienced
>> recommendations
>> for what to remove ...
>>
>
> It's not a matter of removing things. It's a matter of understanding what
> you have told rsyslog to do.
>
I am a bit bewildered by differences between the 7.4.7 Centos 7 based
rsyslog.conf and the 8.16.0 adiscon.com based conf.
> If you re-write the forwarding/db/queue stuff in the new action() format,
> it should be clear to you where the queues exist. This should make it
> obvious why local messages are being delayed.
>
"new action() format" ???
> We are seeing and understanding this, but you are not.
>
What am I missing? How can I make changes without losing DB data from the
forwarding?
_______________________________________________
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.
