rsyslog

Error during GSS (via TCP) send process.

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

There is an malicious entity involved.

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

An address is unknown – not necessarily an error

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

Supplied parameters are invalid.

Supplied parameters are invalid.

This is a somewhat generic error message. It often comes together with another, more descriptive, error message. Most often, it points to a configuration issue.

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

Chaining (e.g. of config command handlers) not permitted.

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

Failure during fopen, for example file not found – see errno.

Opening a file failed. There should be some other error messages in front of this one. Most probably, a configuration file could not be opened (wrong name or permissions).

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

invalid number (format?)

A configuration statement expected an integer number as its argument. However, the number was not well-formed. The configuration statement in question was ignored.

Note that only digits are permitted inside number. For example “1,000” needs to be written as “1000” (this may change in future releases).

Some value is invalid (e.g. user-supplied data).

A required template option is missing.

Some output plugins require specific template options. The template bound the the action is question does not contain this option and thus is rejected.

The most prominent example of required template options is the “SQL” set of options that many database output plugins require. This is done because if neither of these options is present, a sql injection (security issue) would happen. As such, most database plugins require one of these options (note that it is possible to write database plugins that work without this option in a secure way, it is depending on the approach taken by the plugin developer).

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

Action has disabled itself.

This is a follow-up error. Additional error messages should appear in front of this message.

What it means is that an action had a failure that caused it to disable itself. If an action is disabled, it will no longer be executed. This event will most probably happen when the configuration file is being processed, right before actual message processing begins. However, the 2006 status code may be issued at any time.

When and why it is issued is purely up to the output plugin in question. In general, an action should disable itself only if there is no chance (not even a remote one) that action processing can correctly continue. For example, omsnmp disables itself if it can not initialize the net-snmp library, in which case no further processing is possible.

A disable action will remain disabled until either rsyslogd is restarted or (for older releases) a restart-type HUP is issued (which mimics a restart and thus is the same thing).

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