rsyslog

We had a problem parsing JSON (or extra data).

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

Error in RELP processing.

If this message occurs:
imrelp: could not activate relp listner, code 10046

This means that the platform does not provide TLS auth support. In general, this means that GnuTLS is too old.

Here is the recommended solution:
Install a current version of GnuTLS on that system and rebuild librelp from source.

Alternatively you can try to use TLS in anonymous mode! Please note that this does not guard against man-in-the-middle attacks, it at least keeps message flow encrypted.

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

(Input) module does not support input() statement.

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

Legacy parameter no longer permitted.

There is a conflict between a v6+ style module parameter and a legacy parameter. Once module-global parameters have been set in a module() statement, they can no longer be changed via legacy parameters. Note that this applies to all parameters, no matter if they are explicitly specified in the module() statement or not. Legacy parameters are blocked in order to prevent inconsitent results.

If you absolutely need to use the legacy parameters, you can still use $ModLoad instead of module(). Note, however, that this may result in inconsistent result, as it was always the case in the legacy system.

To solve the problem: The accompanying error message lists the legacy statement in question. Please check the module documentation to the equivalent v6+ parameter.

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

Module already in current configuration.

A module is already present in the configuration. In most cases, this means that there are multiple $ModLoad or module() statements for the same module within the configuration file(s). Except for built-in modules this is not possible to avoid inconsistency in module paramters. For built-in modules, the same parameter can not be set twice.

If you have questions please visit the github issue tracker or post a comment (probably takes longer to receive an answer via commenting).

The module (no longer) supports legacy action syntax.

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

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.