rsyslog

Module loaded, but no listeners are defined.

You tried to configure some server, but no (valid) configuration statement was provided to actually start one. So while the module was loaded, it does not do any useful work at all. This may be caused by some configuration problems with the statements that are intended to setup the server.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

Missing configuration parameters.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

Config objects (v6 conf) are not supported here.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

Module (config name) is unknown.

In almost all most cases, this message is caused by

1. a typo in the module name
2. module not being installed

Please note that rsyslog usually is packaged via a core package (usually called “rsyslog”) and feature packages (usually called “rsyslog-feature”). The core package contains only what is frequently needed. For extra functionality, you need to install the feature package. For example, omelasticseach is usually packaged in a package named along the lines of “rsyslog-omeleasticsearch” or “rsyslog-elasticsearch”. The actual package name depends on your distro and/or custom repository used (e.g. rsyslog’s package repositories).

Please note that not all modules are packaged. It depends on the distro and/or package maintainer. Especially some very infrequently modules are often not packaged in official distros. Some are inside the rsyslog repositories. The same holds true for contributed modules which are not officially supported by the rsyslog core team.

Check the rsyslog repositories to see if you can install a module from there if your distro does not provide it. If  you do not find the module there, you need to build it from source.

If you have further questions please post a comment or visit the github issue tracker.

Required parameter in config object is missing.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

(Fatal) error parsing config file.

Something is syntactically wrong with the mentioned config file, so that further interpretation is impossible. The error most often actually is on the quoted line, or at least very close in front of it. A syntax error can be caused by invalid spelling of RainerScript commands, e.g. “stopp” instead of the correct “stop”.

Sample Data:
rsyslogd: version 7.1.11, config validation run (level 3), master config /etc/rsyslog.conf
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 51: syntax error [try http://www.rsyslog.com/e/2207 ]
rsyslogd: CONFIG ERROR: could not interpret master config file ‘/etc/rsyslog.conf’. [try http://www.rsyslog.com/e/2207 ]
rsyslogd: run failed with error -2207 (see rsyslog.h or try http://www.rsyslog.com/e/2207 to learn what that number means)

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

There is a problem with configured thread scheduling params.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

Config directive existed, but no longer supported.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

Whitespace is missing in some config construct.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

Some outdated statementor/functionality is being used in conf file.

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.