Error on start of Syslog-NG
I using Syslog-NG on 3.2.6 on Ubuntu 10.04 If I start / reload syslog-ng I see following error: 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; * My Configuration is: @version: 3.2 #ADM_NTINST @ 09:41 13.01.2012 source s_local {internal(); unix-stream("/dev/log");}; source s_udp {udp(port(514));}; destination d_SYSLOG { file("/var/log/syslog");}; destination SUA002254_localhost_SYS_SYSLOG_local {program("/usr/bin/mysql --host=localhost --user=USR_SYS_SYSLOG --password=pw_Syslog SYS_SYSLOG" template("INSERT INTO local (host, source_ip,facility, priority, tag, unixtime,program, msg) VALUES ('$HOST','$SOURCEIP','$FACILITY','$PRIORITY','$TAG','$UNIXTIME','$PROGRAM',' $MSGONLY' );\n") template-escape(yes));}; destination d_udp1514 {udp("192.168.2.108" port (1514); keep-hostname(););}; destination SUA002254_localhost_SYS_SYSLOG_uaagent {sql( type(mysql) host("localhost") username("USR_SYS_SYSLOG") password("pw_Syslog") database("SYS_SYSLOG") table("uaagent") columns("host", "source_ip", "facility", "priority", "tag", "unixtime", "program", "msg") values("$HOST","$SOURCEIP","$FACILITY","$PRIORITY","$TAG", "$UNIXTIME","$PROGRAM","$MSGONLY") indexes("host", "source_ip", "facility", "priority", "tag", "unixtime", "program", "msg"));}; #log_local log { source(s_local); destination(d_SYSLOG); destination(SUA002254_localhost_SYS_SYSLOG_local); }; #log_uaagent log { source(s_udp); destination(d_udp1514); destination(SUA002254_localhost_SYS_SYSLOG_uaagent); destination(d_SYSLOG); }; Freundliche Grüße / Best regards
"Michael Kolowicz" <michael.kolowicz@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. -- |8]
On Tue, 2012-01-17 at 16:59 +0100, Gergely Nagy wrote:
"Michael Kolowicz" <michael.kolowicz@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
participants (3)
-
Balazs Scheidler
-
Gergely Nagy
-
Michael Kolowicz