<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="4">syslog-ng version 3.36.1 has introduced an
additional time stamp in some of its internally generated log
messages.</font></p>
<p>[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'</p>
<p>In the past this log message would have been formatted as</p>
<p>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'<br>
</p>
<p>Is this intentional?</p>
<p>Why is it not consistent with other internal messages such as</p>
<p>syslog-ng starting up; version='3.36.1'</p>
<p><br>
</p>
<p>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()"<br>
</p>
<p><br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Evan</pre>
</body>
</html>