[syslog-ng] 3.3.7 oddity with file source

Evan Rempel erempel at uvic.ca
Fri Feb 8 20:23:25 CET 2013


Normally when a syslog line is produced, the host has the format of

{source}@{hostname}

so when the log reaches my central server it looks like

2013-02-08T11:15:01-08:00 local at gpfs10.westgrid.uvic.ca/chrysaor.westgrid.ca cron.info CROND[20315]: ...

but on this same host, I have a file source (different source definition), its messages go to the same
destination using a separate log statement, but when they reach the central syslog server it looks like

2013-02-08T11:11:35-08:00 gpfs10.westgrid.uvic.ca/gpfs10.westgrid.uvic.ca/chrysaor.westgrid.ca local2.info mmfs: ...

So it seems that the file source is populating the host with {hostname}/{hostname}

Was this intentional?


source mmfs { file("/var/adm/ras/mmfs.log.latest" log_fetch_limit(100) program_override(mmfs) default-facility(local2) default-priority(info) flags(no-parse) ); };




More information about the syslog-ng mailing list