rsyslog

Non-fatal config error

There was at least one non-fatal configuration error. A non-fatal config error is an error that disables some functionality but does not prevent an rsyslogd startup. This is a subsequent error, the original error cause should have been given in an error message prior to the 2124 error.

Action failed and is now suspended.

The “action failed” state was communicated back from the output module. Please note that, at least up to and including rsyslog v4, this means the action will not be re-activated until a restart (and this will most likely also not happen in the future).

The exact reason for this action is only known to the output module, which hopefully emitted an error message before. If it did not do that, it may be useful to run rsyslogd in debug mode.

Output modules should return this status only if there is really now way of continuing. For example, from rsyslog’s core modules, the SNMP output module returns this state if netsnmp could not properly be initialized. This is a situation from which no recovery is deemed possible. Most other output modules return transient error states, which are retrieable and will not show as error 2123.

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

Output plugin status: previous record was committed (an OK state!).

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

Error setting max. nbr open files process limit.

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

Duplicate function name (rainerscript).

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

ZIP functionality is not present.

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

Queue is full, operation could not be completed.

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

Config file or directory not found.

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

No active actions are configured (no output will be created).

This error occurs when now action at all has been configured in rsyslog.conf. This most probably is a follow-up error that occurs because actions were incorrectly configured and thus not activated.

If no actions are configured, rsyslogd will not do any useful work.

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

X.509 cert’s activation time not yet reached.

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