rsyslog

Interface not supported.

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

Syntax error (in RainerScript)

This most often occurs with RainerScript (though in theory the error code may be issued for other syntax errors as well).

An incorrect syntax was found inside a RainerScript expression. To fix it, check the expression closely (if you don’t find the error, you may want to post the expression to the rsyslog mailing list).

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

Driver name missing where one was required.

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

A descriptor table’s space has been exhausted.

Imfile is able to read from a limited amount of files. If you want to change that amount (default=100) you have to change the source code (MAX_INPUT_FILES) and compile rsyslog again.

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

There is a problem with the user-provided config settings.

This error code can mean multiple things, but basically something was configured in an invalid way. The accompanying error message will list the exact cause. If it does not, or the problem is still not clear, please post the message in question to the discussion thread. Also be sure to check if the thread already contains the actual problem you experience.

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

A required file was not found.

Rsyslogd could not find a file that is required to continue the operation. The name of that file is given within the message text. While diagnosing such problems, be sure to check the messages that occurred before this message. They may point you to why this file is needed.

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

Can not access file.

an open call returned EACCES, which most probably means a file either does not exist or has the wrong permission settings (if running as root, the default, permissions are very unlikely to be the problem). This may be caused by a simple typo in a file name.

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

A required file prefix is missing.

This error indicates that a required file prefix is missing. Most often, this is associated with disk or disk assisted queues. In that context, it means that either the file base name or the directory pointed to it are not set. A common cause (at least for pre v6 versions) is that multiple ruleset queues are defined, but a queue file name is only given once. Then, the name applies only for the first queue. All other properly start up, but with auto-generated names (which is a bit dangerous, as these names depend on the order in which queues appear inside the config file). This situation should be fixed be providing file names for all queues.

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

Invalid object ID

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

Some kind of IO error happened.

This is a very generic error code that happens whenever some unexpected IO error happens. More precise information should be in the actual error message. Please check the discussion thread below if the case you are interested in is already discussed. If not, please consider adding a question to the discussion.

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