[syslog-ng] 3.36.1 new log format of some internal messages
Evan Rempel
erempel at uvic.ca
Tue Apr 5 14:20:29 UTC 2022
syslog-ng version 3.36.1 has introduced an additional time stamp in
some of its internally generated log messages.
[2022-04-05T07:10:27.574110] WARNING: Configuration file format is too
old, syslog-ng is running in compatibility mode. Please update it to use
the syslog-ng 3.36 format at your time of convenience. 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; config-version='3.34'
In the past this log message would have been formatted as
WARNING: Configuration file format is too old, syslog-ng is running in
compatibility mode. Please update it to use the syslog-ng 3.36 format at
your time of convenience. 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; config-version='3.34'
Is this intentional?
Why is it not consistent with other internal messages such as
syslog-ng starting up; version='3.36.1'
Another thing of note is that the configuration warning is actually
logged via journald while all other internal messages are only available
in the syslog-ng log streams sourcing "internal()"
--
Evan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20220405/3f4baacd/attachment.htm>
More information about the syslog-ng
mailing list