rsyslog

Correctable problems with the rsyslog working directory.

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

Problems with the rsyslog working directory.

This error code is generated when there is a problem setting the rsyslog working directory, for example if the user that rsyslogd is running under does not have sufficient permission. The actual error message contains the cause of this error

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

Error during hdfsOpen (e.g. file does not exist).

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

Some messages discarded due to exceeding a rate limit.

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

Epoll_create() failed.

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

No listener defined (e.g. inside an input module).

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

No socket (name) was configured where one is required.

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

Error occured during socket rcv operation.

This error code indicates that there was a problem receiving from the remote host. Check network connectivity to see if there is a physical problem. This can especially occur if there is a partly-functioning network component.

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

Epol_ctll() returned with an unexpected error code.

This is a problem that usually should not occur. It happens, when the epoll_ctl API fails. One probable cause is that rsyslog was build on a newer kernel than the running kernel. If this is the cause, a correction is available in 5.7.10 and above. If you see this error under other circumstances, please post a description of your environment and what you see to the attached discussion thread. We would really love to sort out reasons if this problem still exists.

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

Parser with the specified name was not found.

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