Re: [rsyslog] rsyslog 8.31.0 (v8-stable) released

2017-11-29 Thread Michael Biebl via rsyslog 
Please be aware that the test-suite now requires python to run due to
rscript_parse_time.sh which uses ./tests/rscript_parse_time_get-ts.py

Regards,
Michael

2017-11-28 13:00 GMT+01:00 Florian Riedl :
> Hi all,
>
> Today, we release rsyslog 8.31. This is probably one of the biggest
> releases in the past couple of years. While it also offers great new
> functionality, what really important about it is the focus on further
> improved software quality. For a more detailed description, please
> read Rainer’s blog post. Detailed information about the huge list of
> changes is available in the changelog.
>
> http://blog.gerhards.net/2017/11/rsyslog-831-important-release.html
>
> The packages have received some notable changes as well. First off, we
> were able to implement the Redis output module as a separate package
> on Ubuntu 14.04 and newer. Also there was a dependency change for the
> ommongo module, thus it is now only available on Ubuntu 16.04 or
> newer, but not on CentOS/RHEL anymore. Platform restrictions are
> unavoidable right now due to dependency availability.
>
> ChangeLog:
>
> https://github.com/rsyslog/rsyslog/blob/v8-stable/ChangeLog
>
> Download:
>
> http://www.rsyslog.com/downloads/download-v8-stable/
>
> As always, feedback is appreciated.
>
> Best regards,
> Florian Riedl
> ___
> 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.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
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.

Re: [rsyslog] Updates 8.29 -> 8.30 broke several logs

2017-11-29 Thread Rainer Gerhards 
just quickly (busy for obvious reason ;-))

https://github.com/rsyslog/rsyslog/issues/2134

Rainer

2017-11-29 15:20 GMT+01:00 Mike Schleif :
> On Fri, Nov 24, 2017 at 11:55 AM, Rainer Gerhards 
> wrote:
>
>> 2017-11-24 16:49 GMT+01:00 Mike Schleif :
>> > How will we return to the $basearch repository?
>>
>> It'll be part of next Tuesday's 8.31.0 release. Packages are done
>> usually on the same day or day after. You should be safe to switch
>> back to them once this is done.
>>
>> Rainer
>>
>
> Yesterday, we updated: rsyslog.x86_64 0:8.30.0.2-1.el7
>
> To:
> $ /usr/sbin/rsyslogd -v
> rsyslogd 8.31.0, compiled with:
> PLATFORM:   x86_64-redhat-linux-gnu
> PLATFORM (lsb_release -d):
> FEATURE_REGEXP: Yes
> GSSAPI Kerberos 5 support:  No
> FEATURE_DEBUG (debug build, slow code): No
> 32bit Atomic operations supported:  Yes
> 64bit Atomic operations supported:  Yes
> memory allocator:   system default
> Runtime Instrumentation (slow code):No
> uuid support:   Yes
> Number of Bits in RainerScript integers: 64
>
> Everything regarding this issue appeared to function properly. So, we
> decided to restart rsyslogd:
>
> # /bin/systemctl restart rsyslog
>
> Unfortunately, that never returns to the prompt! rsyslogd -n is in the
> process table, logs are being logged and ommysql is writing to two
> databases.
>
> /bin/systemctl stop rsyslog - behaves properly; but, /bin/systemctl start
> rsyslog - also never returns to prompt.
>
> Full reboot appears to complete properly, although /bin/systemctl status
> rsyslog - contains two errors about connecting to the databases.
>
>
> Is this topic for new thread?
>
> Ought we revert to rsyslog.x86_64 0:8.30.0.2-1.el7 ?
> ___
> 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.

Re: [rsyslog] Updates 8.29 -> 8.30 broke several logs

2017-11-29 Thread Mike Schleif 
On Fri, Nov 24, 2017 at 11:55 AM, Rainer Gerhards 
wrote:

> 2017-11-24 16:49 GMT+01:00 Mike Schleif :
> > How will we return to the $basearch repository?
>
> It'll be part of next Tuesday's 8.31.0 release. Packages are done
> usually on the same day or day after. You should be safe to switch
> back to them once this is done.
>
> Rainer
>

Yesterday, we updated: rsyslog.x86_64 0:8.30.0.2-1.el7

To:
$ /usr/sbin/rsyslogd -v
rsyslogd 8.31.0, compiled with:
PLATFORM:   x86_64-redhat-linux-gnu
PLATFORM (lsb_release -d):
FEATURE_REGEXP: Yes
GSSAPI Kerberos 5 support:  No
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported:  Yes
64bit Atomic operations supported:  Yes
memory allocator:   system default
Runtime Instrumentation (slow code):No
uuid support:   Yes
Number of Bits in RainerScript integers: 64

Everything regarding this issue appeared to function properly. So, we
decided to restart rsyslogd:

# /bin/systemctl restart rsyslog

Unfortunately, that never returns to the prompt! rsyslogd -n is in the
process table, logs are being logged and ommysql is writing to two
databases.

/bin/systemctl stop rsyslog - behaves properly; but, /bin/systemctl start
rsyslog - also never returns to prompt.

Full reboot appears to complete properly, although /bin/systemctl status
rsyslog - contains two errors about connecting to the databases.


Is this topic for new thread?

Ought we revert to rsyslog.x86_64 0:8.30.0.2-1.el7 ?
___
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.