rsyslog error 2122
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.
rsyslog error 2116
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.
rsyslog error 2114
Duplicate function name (rainerscript).
This is a stub entry: If you have questions please post a comment or visit the github issue tracker.
rsyslog error 2108
ZIP functionality is not present.
This is a stub entry: If you have questions please post a comment or visit the github issue tracker.
rsyslog error 2105
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.
rsyslog error 2104
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.
rsyslog error 2103
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.
rsyslog error 2094
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.
rsyslog error 2089
Connection was aborted due to previous error.
This is a follow-up error, there should be some more specific error messages. As of this writing, it occurs with the GnuTLS driver, only. One cause may be missing authorization of the remote peer, e.g. via an invalid certificate.
This is a stub entry: If you have questions please post a comment or visit the github issue tracker.
rsyslog error 2088
Invalid certificate fingerprint.
The fingerprint configured for the certificate is incorrect. This may either be an error of the configured fingerprint OR it may show that a non-permitted remote peer tried to communicate with the rsyslogd instance that reported the error. Please note that this error can occur on clients and servers, as both support certificate fingerprint checking.
This is a stub entry: If you have questions please post a comment or visit the github issue tracker.
