MonitorWare Knowledge Base

Hi,

I've noticed, that a very useful directives in my config:

Code: Select all

$HUPisRestart off
$MaxMessageSize 4k


results an error messages:

Code: Select all

rsyslogd: [origin software="rsyslogd" swVersion="3.18.3" x-pid="3211" x-info="http://www.rsyslog.com"] restart
rsyslogd: invalid or yet-unknown config file command - have you forgotten to load a module?
rsyslogd: the last error occured in /etc/rsyslog.conf, line 123
rsyslogd: invalid or yet-unknown config file command - have you forgotten to load a module?
rsyslogd: the last error occured in /etc/rsyslog.conf, line 124


Is it a bug ?
Is it fixed in current version ?

Arv

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

I think both are simply not supported in your (outdated ) version

I have the same message as the original poster in my logs. So in which version are these two config options supported? I'm using version 3.20.4 and running it with the -c3 flag. Thanks.

These are relatively new directives.

$HUPisRestart was introduced in 4.1.0 and $MaxMessageSize in 3.21.4.

HTH
Rainer

Rainer,
I think it would be a pretty good idea if the configuration variables (features) in the documentation where flagged with the version, when they were added.

Very often people are pointed to the online documentation, which reflects the current master branch. So they try options which are not supported by the version shipped in their distribution.

mbiebl wrote:Rainer,
I think it would be a pretty good idea if the configuration variables (features) in the documentation where flagged with the version, when they were added.

Very often people are pointed to the online documentation, which reflects the current master branch. So they try options which are not supported by the version shipped in their distribution.

Shame on me, I should have looked closer. It seems that you already started to add this information (e.g. for $PrivDropToUser).

Well, if so, shame on both of us... I started to add this information, but obviously not consistently. Otherwise it should be present on$HUPIsRestart, where it is not. I had to dig it out from the ChangeLog myself. Will try to more consistently add it (overall, the doc would benefit from a brush-up, but so much to do...).