[syslog-ng] Error on start of Syslog-NG

Balazs Scheidler bazsi at balabit.hu
Thu Jan 19 14:07:55 CET 2012


On Tue, 2012-01-17 at 16:59 +0100, Gergely Nagy wrote:
> "Michael Kolowicz" <michael.kolowicz at km-f.eu> writes:
> 
> > If I start / reload syslog-ng I see following error:
> 
> It's a warning, not an error. Unless syslog-ng doesn't start afterwards
> (it should).
> 
> > Reloading syslog-ng's config file: WARNING: Configuration file format is too
> > old, please update it to use the 3.2 format as some constructs might operate
> > inefficiently;
> > WARNING: the expected message format is being changed for unix-domain
> > transports to improve syslogd compatibity with syslog-ng 3.2. If you are
> > using custom applications which bypass the syslog() API, you might need the
> > 'expect-hostname' flag to get the old behaviour back;
> 
> Off the top of my head, I can't see what triggers this in your config,
> except if not this line:
> 
> > source s_local {internal(); unix-stream("/dev/log");};
> 
> Try changing that unix-stream to unix-dgram, and see if the warning goes
> away.

It won't. The error message indicates that the config version is not
tagged with the latest '@version:' header.

Are you sure your syslog-ng is using the syslog-ng.conf file you quoted?
Try passing the config file path using the -f command line parameter.

-- 
Bazsi




More information about the syslog-ng mailing list