rsyslog

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.

Module could not be loaded – problem in dlopen().

A problem occurred during dlopen()ing a loadable module (e.g. an input or output plugin).

Most common causes for this are that the module either does not exist or has incorrect permission settings. Permission problems are less likely if rsyslogd runs as root, what it does by default.

Note that most packages only distribute a very limited set of plugins via the core rsyslog package. To use enhanced functionality (like the file input, database or mail outputs and many more), you need to install additional packages (there names are distro-specific, so they can not be given here).

When building from source, check the ./configure output on which modules are built. A summary is given at the end of the configure run. Use “./configure -help” to see which options enable which modules.

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

A host is not permitted to perform an action it requested.

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

Object (name) is already registered.

this error code should usually not be visible.

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