Any idea if this is a branch issue or what might have actually broken? I'm trying to keep all of our systems on the latest stable release so i've been yum updating from the stable repo instead of compiling things.
I was autocorrected to "cents 6". I'm really using the CentOS 6 rsyslog 8 stable repo for everything. Thoughts? Thanks in advance. Cheers, JB On Fri, Mar 11, 2016 at 3:23 PM, Joe Blow <[email protected]> wrote: > I was using cents 6 with the rsyslog 8 stable repos and it broke. > > Is centos delivered differently than rhel? > > > > Original Message > From:[email protected] > Sent:March 11, 2016 1:59 PM > To:[email protected]; [email protected] > Reply-to:[email protected] > Subject:Re: [rsyslog] problem with leap year and unixtimestamp template > option > > resending as the list bounced things from my new mailserver. > > On Thu, 10 Mar 2016, David Lang wrote: > > > Date: Thu, 10 Mar 2016 20:52:15 -0800 (PST) > > From: David Lang <[email protected]> > > To: [email protected], rsyslog-users <[email protected]> > > Subject: Re: [rsyslog] problem with leap year and unixtimestamp template > > option > > > > Speaking of liblognorm, any idea when 2.0 packages will be available? > > > > David Lang > > > > On Thu, 10 Mar 2016, Andre Lorbach wrote: > > > >> Date: Thu, 10 Mar 2016 09:42:59 +0100 > >> From: Andre Lorbach <[email protected]> > >> To: rsyslog-users <[email protected]> > >> Subject: Re: [rsyslog] problem with leap year and unixtimestamp template > >> option > >> > >> Which Version of liblognorm is installed? > >> For rsyslog 8.17 we need newer version V1.1.3. > >> > >> Packages for Ubuntu, Redhat and Debian are up to date in our > repositories. > >> > >> > >> Best regards, > >> Andre Lorbach > >> > >>> -----Ursprüngliche Nachricht----- > >>> Von: [email protected] [mailto:rsyslog- > >>> [email protected]] Im Auftrag von Rainer Gerhards > >>> Gesendet: Mittwoch, 9. März 2016 23:02 > >>> An: rsyslog-users > >>> Betreff: Re: [rsyslog] problem with leap year and unixtimestamp > template > >>> option > >>> > >>> This looks like a too old version of liblognorm. I need to check with > >> the > >>> package guys why this is not automatically updated. Andre? Florian? > >>> > >>> Rainer > >>> > >>> Sent from phone, thus brief. > >>> Am 09.03.2016 19:33 schrieb "Joe Blow" <[email protected]>: > >>> > >>> > Hey all, > >>> > > >>> > After the update to 8.17 to fix this, i'm now getting this when > >>> > mmnormalize > >>> > loads: > >>> > > >>> > rsyslogd-2066: could not load module '/lib64/rsyslog/mmnormalize.so', > >>> > dlopen: /lib64/rsyslog/mmnormalize.so: undefined symbol: > >>> > ln_setErrMsgCB > >>> > [v8.17.0 try http://www.rsyslog.com/e/2066 ] > >>> > > >>> > Any fix? This basically broke our elasticsearch parsing. > >>> > > >>> > Thanks in advance. > >>> > > >>> > Cheers, > >>> > > >>> > JB > >>> > > >>> > On Wed, Mar 2, 2016 at 12:12 PM, Rainer Gerhards > >>> > <[email protected] > >>> > > > >>> > wrote: > >>> > > >>> > > 2016-03-02 16:51 GMT+01:00 Peter Portante > >>> <[email protected]>: > >>> > > > And it appears to also affect the "$date-ordinal" property. Can > >>> > > > you confirm? > >>> > > > >>> > > Yeah, right because it uses the same helper function. But so the > >>> > > same fix fixes that issue as well. But... having said that, it's > >>> > > probably better to add some tests for it to the testbench as well. > >>> > > > >>> > > Thanks for bringing it up. > >>> > > > >>> > > Rainer > >>> > > > > >>> > > > On Wed, Mar 2, 2016 at 10:47 AM, Peter Portante < > >>> > > [email protected]> > >>> > > > wrote: > >>> > > > > >>> > > >> Hi Rainer, > >>> > > >> > >>> > > >> Does this also affect ommongodb use? > >>> > > >> > >>> > > >> -peter > >>> > > >> > >>> > > >> > >>> > > >> On Wed, Mar 2, 2016 at 6:11 AM, Rainer Gerhards < > >>> > > [email protected]> > >>> > > >> wrote: > >>> > > >> > >>> > > >>> Hi all, > >>> > > >>> > >>> > > >>> I just wanted to let you know that we have found an issue with > >>> > > >>> the unixtimestamp formatting option in leap years. The problem > >>> > > >>> started on March, 1st and will persist till the end of the > year. > >>> > > >>> The timestamp > >>> > is > >>> > > >>> one day in the past. > >>> > > >>> > >>> > > >>> A patch is available here, it shall probably work with almost > >>> > > >>> all rsyslog versions: > >>> > > >>> > >>> > > >>> > >>> > > > >>> > > >>> https://github.com/rgerhards/rsyslog/commit/ffb321f1698a971e0acda48caf > >>> > a97bb344cf0829 > >>> > > >>> > >>> > > >>> Full details can be found in this issue tracker: > >>> > > >>> https://github.com/rsyslog/rsyslog/issues/830 > >>> > > >>> > >>> > > >>> Note that I will NOT release a 8.16.1 version for this fix. > >>> > > >>> Usually, > >>> > I > >>> > > >>> would have done so, but the 8.17.0 release is due next Tuesday > >>> > > >>> and will probably available as RC on friday. Given the fact > that > >>> > > >>> I would need at least one additional day to craft 8.16.1, I > >>> > > >>> don't think this makes much sense. > >>> > > >>> > >>> > > >>> Distro packages (and other users as well, of course) can apply > >>> > > >>> above-mentioned short patch. I actually suggest to do so, as > >>> > > >>> this problem exists, I think, in all versions supporting the > >>> > > >>> "unixtimestamp" formatting option (side-note: v5.8 does not > have > >>> > > >>> this option). > >>> > > >>> > >>> > > >>> Rainer > >>> > > >>> _______________________________________________ > >>> > > >>> 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. > >>> > > >>> > >>> > > >> > >>> > > >> > >>> > > > _______________________________________________ > >>> > > > 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. > >>> > > _______________________________________________ > >>> > > 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. > >>> > > > >>> > _______________________________________________ > >>> > 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. > >>> > > >>> _______________________________________________ > >>> 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. > >> _______________________________________________ > >> 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. > _______________________________________________ > 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. > _______________________________________________ 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.
