Bugzilla – Bug 958183
syslog-ng - Error parsing config, root plugin template-function not found in /usr/share/syslog-ng/include/scl/cim/template.conf
Last modified: 2016-06-27 07:05:21 UTC
Hardware - office24, IBM Thinkcentre, MSL library host. Software - latest Tumbleweed (I ran an update this morning): # syslog-ng -F -f /etc/syslog-ng/syslog-ng.conf [2015-12-07T14:05:14.618955] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode Please update it to use the syslog-ng 3.7 format at your time of convinience, compatibility mode can operate less efficiently in some cases. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.; [2015-12-07T14:05:14.620453] WARNING: Your configuration uses a newly introduced reserved word as identifier, please use a different name or enclose it in quotes before upgrading; keyword='template_function', config-version='3.5', version='3.7', filename='/usr/share/syslog-ng/include/scl/cim/template.conf', line='23:1' Error parsing config, root plugin template-function not found in /usr/share/syslog-ng/include/scl/cim/template.conf at line 23, column 1: included from /etc/syslog-ng/scl.conf line 32, column 1 included from /etc/syslog-ng/syslog-ng.conf line 3, column 1 template-function "format-cim" "$(format-json --pair @timestamp='${R_ISODATE}' --pair @message='${MSG}' --key .cim.* --shift 5 --key _* --key .* --replace-prefix .=_ --key *.*)\n"; ^^^^^^^^^^^^^^^^^
Know bug upstream, right now we are trying to figure out the right solution. For now, change the version number in the configuration file to 3.7 as a quick fix.
(In reply to peter czanik from comment #1) > Know bug upstream, right now we are trying to figure out the right solution. > > For now, change the version number in the configuration file to 3.7 as a > quick fix. Thanks Peter, much appreciated!
A fix is available, but not yet in a release: https://github.com/balabit/syslog-ng/issues/796