rsyslog

Warning parsing config file.

This unfortunately is a pretty generic error code which is emitted when there is a problem understanding the configuration files. The main configuration file is usually /etc/rsyslog.conf and it may include other configuration files. The error message names the file and the approximate location of the error.

The error text should describe what needs to be fixed. If that does not help, it may make sense to check out rsyslog support options.

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

Indicates a (config) validation run, processing not carried out.

This is an expected code for config validation runs (those with -N<nbr> on the command line). It just indicates why rsyslog did not do a full startup.

This is a trick for the debuging system – it means no iRet is provided

Implementation is missing (probably internal error or lazyness ;))

Memory allocation failed

This usually means that your system ran out of memory. This may be caused by queue sizes to be configured too high. Use impstats to gather more insight into ressource allocation.

Size of this buffer is too small

The caller provided a buffer, but the called function sees the size of this buffer is too small – operation not carried out.

An digit was expected, but none found (mostly parsing)

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

An expected trailing quote is missing

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

Invalid config command

This error occurs when either an invalid configuration command is part of rsyslog.con or when the command is valid, but resides in a not-yet-loaded plugin.

To use commands provided by plugins, the plugin must be loaded first (via $ModLoad). Only after that the command can be used.

This error may also be caused by a module load failure. Be sure to check error messages before this one, they may point you into the right direction. Please note that this message should be followed by another one which tells you on which line of rsyslog.conf the problem occurred.

Sample Data:
2008-06-27T12:29:44.828434+02:00 machine.example.net rsyslogd-3003:invalid or yet-unknown config file command – have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]

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

Imfile file name contains wildcard, which may be problematic.

This message tells the user that a state file is specified for an imfile input which uses wildcards. This is usually an extremely bad idea, as the state file becomes corrupted if multiple files match the wildcard. The option primarily exist for exotic use cases and it is strongly recommended not to specify state file names in this setup.

For more details check the documentation

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