rsyslog

Invalid (network stream) driver mode

A driver mode was set that the current network stream driver does not support. For example, a TLS-encryption mode may have been set for the plain tcp (non-TLS) stream driver.

Note that ordering of statements is important: if e.g. you select TLS driver mode on line 1, but select the TLS driver on line 2, that will fail. If you swap lines one and two (thus specifying the driver before the mode), the sequence will work.

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

Max nbr of listeners reached, can not create more.

This error code usually happens with imtcp. This plugin has a maximum number of listeners (server ports) that can be used. That limit is set at build time. If you experience this problem, there are two solutions: if you run under linux and do not need TLS, you can use imptcp instead, which is faster and does not have this limitation. If you need to stick with imtcp, you need to do a custom build and increase the max number of listeners #define.

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

Maximum number of sessions reached.

The maximum number of sessions has been reached. This can happen, for example, with imtcp, but also with other modules that have a session limit. Usually, there should be some specific information in the error message that points you to the component experiencing the problem. Check its documentation for how to increase the maximum number of sessions.

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

Error adding (TLS) certificate

This message occurs with TLS netstream driver. For TLS, certificates (.pem files) are needed to provide security credentials. This error is issued if there is a problem with these files. The message contains a more precise error description. That error text is taken directly from the underlying TLS library.

A common cause is that the file can not be found or accessed (permissions!). In that case, a rsyslogd-2040 error will follow.

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

Could not bind socket, defunct.

This problem occurs when no socket could be initialized. A probable cause is a tcp receiver (imtcp/imptcp) where the configured IP address is invalid (where invalid means “not on this local machine”). A simple typo can do.

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

Invalid port value.

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

Sender for mail destination is missing.

Ommail needs to know the sender address to deliver mail. This is required to generate wellformed smtp messages. Relay servers will often ignore messages without a sender. It was tried to create an ommail action for which no sender address was specified. Note that it may not required to provide a real sender address, a dummy address (like rsyslogd@example.net) might be sufficient.

The most probable case is that some configuration statements are missing from the action definition. See ommail documentation for a configuration samples and the required configuration statements.

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

Recipient for mail destination is missing.

Ommail needs to know whom to deliver mail to (for obvious reasons…). This is the so-called “To” recipient. It was tried to create an ommail action for which no To-Recipient was specified.

The most probable case is that some configuration statements are missing from the action definition. See ommail documentation for a configuration samples and the required configuration statements.

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

Module could not be loaded – init failed.

When rsyslog loads a loadable module, it calls an entry point called “init()” inside that module. This message is emitted when the module could be loaded, but init() failed for some reasons. Probable causes could be a version mismatch between the loadable module and the rsyslog core, some third party libraries that could not be loaded or loading the same module more than once (rsyslog tries to prevent this, but if modules are renamed, it may still happen).

Usually, there should be some related error messages right in front of the message in question.

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

Module could not be loaded – init() missing.

The plugin (loadable module) architecture demands that each plugin provides an initialization entry point to the rsyslog core. Without it, the plugin is invalid.

During the load of a module, the rsyslog core could not find this init() entry point (it tries so via dlload()/dlsysm()). This most probably is an indication of one of the following failure conditions:

a) the plugin file is corrupt
b) there is a permission problem
c) the file in question is not a plugin file

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