Mailing List Archive: $InputTCPMaxListeners and $InputTCPMaxSessions not being respected

$InputTCPMaxListeners and $InputTCPMaxSessions not being respected

Aug 30, 2019, 3:57 PM

Post #1 of 4 (443 views)

Hello all,

I have set up many rulesets with `$RulesetCreateMainQueue on` and when I
prepend `$InputTCPMaxListeners` and `$InputTCPMaxSessions` before any
`$InputTCPServerRun` directives, the `$InputTCPMaxListeners` and
`$InputTCPMaxSessions` settings are not being respected or do not have an
active effect; `rsyslogd` is limited to the default tcp listener count of
20. Note that to reach the 20 count of IPv4 TCP connections, I am starting
with `-4`.

I am running `rsyslogd 8.24.0-41.el7_7`, and I imagine this is related to
my use of `$RulesetCreateMainQueue` but I'm not sure why this would be, as
the `$InputTCPMaxListeners` and `$InputTCPMaxSessions` are globally
effective directives.

Has anyone faced this issue? If so, how is it resolvable?

Any assistance is appreciated.

Thanks,

Matt
_______________________________________________
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: $InputTCPMaxListeners and $InputTCPMaxSessions not being respected [ In reply to ]

rsyslog at lists

Aug 30, 2019, 4:08 PM

Post #2 of 4 (443 views)

Permalink

first off, 8.24 is about 2.5 years old, I would suggest moving to a more current
version

Second, if you are setting parameters like this, please switch to the newer
syntax, it makes it much clearer as to what is going on.

Current versions also have a -o option that output what rsyslog interprets the
config to be, which also makes it easier to understand the config.

David Lang
_______________________________________________
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: $InputTCPMaxListeners and $InputTCPMaxSessions not being respected [ In reply to ]

rsyslog at lists

Aug 31, 2019, 3:32 AM

Post #3 of 4 (442 views)

Permalink

Thanks for the advice David. I'm on RHEL7 and using the stable repo to get the package. I'll find and build the last stable and respond back after troubleshooting with `-o`.

I implemented rsyslog in-flight during a project, and had worked with the legacy syntax so this is now I wrote the config. I'll also prioritize migrating to rainerscript to stay current.

Thanks,

Matt

Sent via BlackBerry Hub+ Inbox for Android

Original Message

From: david@lang.hm
Sent: August 30, 2019 7:08 PM
To: rsyslog@lists.adiscon.com
Cc: matthewbrown@gmail.com
Subject: Re: [rsyslog] $InputTCPMaxListeners and $InputTCPMaxSessions not being respected

first off, 8.24 is about 2.5 years old, I would suggest moving to a more current
version

Second, if you are setting parameters like this, please switch to the newer
syntax, it makes it much clearer as to what is going on.

Current versions also have a -o option that output what rsyslog interprets the
config to be, which also makes it easier to understand the config.

David Lang
_______________________________________________
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: $InputTCPMaxListeners and $InputTCPMaxSessions not being respected [ In reply to ]

rsyslog at lists

Aug 31, 2019, 3:57 AM

Post #4 of 4 (442 views)

Permalink

On Sat, 31 Aug 2019, Matt Brown wrote:

> I'll also prioritize migrating to rainerscript to stay current.

no need to re-write everything, but anything that depends on $something followed
by things that change behavior based on that something is probably better
written using the new module(), input() and action() syntax

David Lang
_______________________________________________
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.