On Thu, 26 Apr 2018, Li, Mike wrote:
Date: Thu, 26 Apr 2018 12:41:53 +0000 From: "Li, Mike" <[email protected]> To: David Lang <[email protected]>, "Li, Mike via rsyslog" <[email protected]> Subject: RE: [rsyslog] Resend: rsyslog v8.x server config with tlsDavid, I would like to continue using the input() statements because I changed all the "template (name, type ), if then { action(), stop}" stanzas to support rsyslog v8.34 I also using module(load="imudp" SchedulingPolicy="fifo" SchedulingPriority="5" threads="2" timeRequery="8" batchSize="128") to support receiving heavy rsyslogs traffic with rsyslog v8
using input() statement is good, especially when you are doing complex things
Or will "$template, if then ?; & ~" stanzas still work with rsyslog v 8.34? How to convert "module(load="imudp" SchedulingPolicy="fifo" SchedulingPriority="5" threads="2" timeRequery="8" batchSize="128")" in old syntax? I have following rpms installed rsyslog-gnutls-8.34.0-2.el6.x86_64 rsyslog-8.34.0-2.el6.x86_64 Could I be directed to the correct information on how to convert following: # make gtls driver the default $DefaultNetstreamDriver gtls # certificate files $DefaultNetstreamDriverCAFile /rsyslog/protected/ca.pem $DefaultNetstreamDriverCertFile /rsyslog/protected/machine-cert.pem $DefaultNetstreamDriverKeyFile /rsyslog/protected/machine-key.pem $InputTCPServerStreamDriverAuthMode x509/name $InputTCPServerStreamDriverPermittedPeer *.example.net $InputTCPServerStreamDriverMode 1 # run driver in TLS-only mode
all these separate lines that are designed to set parameters that are then used by:
$InputTCPServerRun 10514 # start up listener at port 10514
need to be removed, and you need to create a new input() clause that does this instead (listening on port 10514/TCP with the various parameters that you are defining)
I have not yet done any real work using encrypted connections, so I'm not going to be able to help more than the docs on how to define this, but I do recognize the error of both using the new style single-line input() syntax and the old style multi-line $InputTCP*/etc syntax in the same file.
David Lang
To work on rsyslog v8.34 ? Thanks Mike -----Original Message----- From: David Lang <[email protected]> Sent: Wednesday, April 25, 2018 8:19 PM To: Li, Mike via rsyslog <[email protected]> Cc: Li, Mike <[email protected]> Subject: [EXTERNAL] Re: [rsyslog] Resend: rsyslog v8.x server config with tls it would be clearer if you could show us a copy of your full config. But I believe that the problem is that you are mixing old and new syntax in one of the few ways that rsyslog complains about. If you have no input() statements, the obsolete multi-line version works But as soon as you have one new style input() statement, you need to convert the rest of them over as well. Confidentiality Notice:: This email, including attachments, may include non-public, proprietary, confidential or legally privileged information. If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.
_______________________________________________ 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.
