[rsyslog-notify] Forum Thread: Re: Issue with omfwd rebindinterval usage - (Mode 'reply')

[noreply at adiscon.com]

User: JoiOwen 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=26330#p26330

Message: 
----------
Well, rsyslog is transmitting something on the order of 2500msgs/sec, and
if I set that counter too low, the servers may run out of sockets.  (My
first attempt set that value at 10, because I thought the number
represented seconds, not messages, and it opened several thousand sockets
before I could get netstat running.)  That number of 30000 gives me about 8
seconds of traffic per socket.

As for the syntax... That is an interesting question.  The file containing
that section is all ReinerScript, but it's planted in rsyslog.d and is
included by the main rsyslog.conf file (per Debian/Ubuntu package
standards.)  

[code:3is94kft]
root at monad2:/usr/share/doc/rsyslog-doc/html# rsyslogd -N2 -f
/etc/rsyslog.conf
rsyslogd: version 7.4.4, config validation run (level 2),
master config /etc/rsyslog.conf
rsyslogd: End of config validation run. Bye.
[/code:3is94kft]


It seems to like that embedded line comment just fine.      Note that my
question is about things breaking when I uncomment that line and turned on
the rebindinterval, not the other way around.  Usually when I create a
syntax error, rsyslog won't even start.  The file where I have all this in
is all ReinerScript, but it's included via the usual ubuntu-standard
rsyslog.conf file, which includes everything in /etc/rsyslog.d/.

I've gone ahead and removed all of the embedded # comments, but it doesn't
seem to have made any difference in the behavior.  I'm going to see if I
can find a newer version in ubuntu updates or backports or something to see
if the behavior changes with a newer version.