rsyslog

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.

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.

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.

A provided value is invalid for the curret mode.

This problem can happen when the network stream layer is configured. The configuration settings depend on the lower-level driver (e.g. plain tcp, GnuTLS) being used as well as the mode it is set to. For example, certificate-related config commands issued to the plain tcp driver (ptcp) are rejected. Similarly, some authentication settings can not be made when the GnuTLS dirver (gtls) is in anonymous mode.

The cause often is an invalid sequence of config statements inside rsyslog.conf. Remember that order of statements is vitally important. For example, one needs to set the driver first, before driver-specific commands can be issued.

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