Return
-
Title
Error initializing message pipeline -
Description
The following errors are reported in the internal logs
++++++++++++++++++
- directory-monitor-inotify: could not create inotify object; errno='Too many open files (24)'
- Free directory monitor; dir='<directory>'
- Wildcard source: could not create directory monitoring object! Possible message loss; dir='<directory>', location='/opt/syslog-ng/etc/syslog-ng.conf:1036:5'
- Error initializing message pipeline; plugin_name='wildcard_file', location='/opt/syslog-ng/etc/syslog-ng.conf:1036:5'
++++++++++++++++++
-
Cause
The “fs.inotify.max_user_instances” value is too low for the number of wildcard-file sources to work
-
Resolution
The default value is fot “fs.inotify.max_user_instances” 128 and this should allow up to 124 wildcard-file sources to work
For the purposes of this KB article the value is being increased to 256.
To check the current setting run:
# sudo sysctl -a | grep max_user_instancesTo temporarily increase the value run:
# sudo sysctl -w fs.inotify.max_user_instances=256
To permanently increase the value (so it will survive reboots) run:
# echo "fs.inotify.max_user_instances=256" >> /etc/sysctl.d/99-sysctl.conf
-
Additional Information
If the number of wildcard sources is increased again then the limit will have to be increased accordingly. However it is not recommended that it is set too high as a catch-all. This is a value that should be increased as the use case requires it to be.