rsyslog

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.

A provided value is not supported.

This usually occurs with TCP syslog and usually means that TLS parameters have been used, but the communication mode is set to plan tcp, that is without TLS. As such the TLS parameters will be ignored.

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

No TLS certificate available where one was expected.

An operation required a TLS certificate, but none was provided/configured.

Make sure you check the sequence of configuration statements. It may be the case that the certificate is provided BELOW the point where it is required.

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

Generic TLS certificate error

There is some issue with a TLS certificate being used, but the underlaying library did not return a more precise error code. It may be useful to enable debug logging. In any case, it should be ensured that the certificate has been generated in the proper sequence as shown in the (long) TLS guide inside the doc set.

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

TLS handshake failed

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

Invalid (network stream) driver mode

A driver mode was set that the current network stream driver does not support. For example, a TLS-encryption mode may have been set for the plain tcp (non-TLS) stream driver.

Note that ordering of statements is important: if e.g. you select TLS driver mode on line 1, but select the TLS driver on line 2, that will fail. If you swap lines one and two (thus specifying the driver before the mode), the sequence will work.

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

Max nbr of listeners reached, can not create more.

This error code usually happens with imtcp. This plugin has a maximum number of listeners (server ports) that can be used. That limit is set at build time. If you experience this problem, there are two solutions: if you run under linux and do not need TLS, you can use imptcp instead, which is faster and does not have this limitation. If you need to stick with imtcp, you need to do a custom build and increase the max number of listeners #define.

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

Maximum number of sessions reached.

The maximum number of sessions has been reached. This can happen, for example, with imtcp, but also with other modules that have a session limit. Usually, there should be some specific information in the error message that points you to the component experiencing the problem. Check its documentation for how to increase the maximum number of sessions.

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