syslog-ng.conf disables standard OS logging

[GoogleCodeExporter]

PLEASE NOTE!  This Issue Tracker is NOT intended for normal support
requests!  Support requests should go to the mailing list first.  Once
we've confirmed your issue on the mailing list, we may ask you to create a
ticket here.

If you have contacted the mailing list first and we've asked you to create
a ticket here, please answer the following questions:

What steps will reproduce the problem?
1. tail -f /var/log/messages
2. tail -f /var/log/maillog
3.

What is the expected output? What do you see instead?

Expected, to see logs from non-SO processes, but found empty files instead.


Are you using the new Security Onion 12.04?

Yes.

Did you install from the ISO image or did you install your own version of
Ubuntu and then add our PPA and packages?

ISO

Please provide any additional information below.

I presume OS logs can be put into ELSA, but failing that (this needs fine 
tuning) to get logs moving to /var/log, I added the following lines to 
/etc/syslog-ng/syslog-ng.conf:


# First some standard logfile
#
destination authlog { file("/var/log/auth.log"); };
destination syslog { file("/var/log/syslog"); };
destination cron { file("/var/log/cron.log"); };
destination daemon { file("/var/log/daemon.log"); };
destination kern { file("/var/log/kern.log"); };
destination lpr { file("/var/log/lpr.log"); };
destination user { file("/var/log/user.log"); };
destination uucp { file("/var/log/uucp.log"); };


# This files are the log come from the mail subsystem.
#
destination mail { file("/var/log/mail.log"); };
destination maillog { file("/var/log/maillog"); };
destination mailinfo { file("/var/log/mail.info"); };
destination mailwarn { file("/var/log/mail.warn"); };
destination mailerr { file("/var/log/mail.err"); };

# Some `catch-all' logfiles.
#
destination debug { file("/var/log/debug"); };
destination messages { file("/var/log/messages"); };

filter f_authpriv { facility(auth, authpriv); };
filter f_syslog { not facility(auth, authpriv) and not facility(mail); };
filter f_cron { facility(cron); };
filter f_daemon { facility(daemon); };
filter f_kern { facility(kern); };
filter f_lpr { facility(lpr); };
filter f_mail { facility(mail); };
filter f_user { facility(user); };
filter f_uucp { facility(cron); };
filter f_debug { not facility(auth, authpriv, news, mail); };
filter f_messages { level(info .. warn)
        and not facility(auth, authpriv, cron, daemon, mail, news); };
filter f_emergency { level(emerg); };

filter f_info { level(info); };
filter f_notice { level(notice); };
filter f_warn { level(warn); };
filter f_crit { level(crit); };
filter f_err { level(err); };

###############################################################
#
# log statements actually send logs somewhere, to a file, across the network, 
etc
#

log { source(s_syslog); filter(f_authpriv); destination(syslog); };
log { source(s_syslog); filter(f_syslog); destination(syslog); };
log { source(s_syslog); filter(f_cron); destination(cron); };
log { source(s_syslog); filter(f_daemon); destination(messages); };
log { source(s_syslog); filter(f_kern); destination(messages); };
log { source(s_syslog); filter(f_lpr); destination(lpr); };
log { source(s_syslog); filter(f_mail); destination(mail); };
log { source(s_syslog); filter(f_user); destination(messages); };
log { source(s_syslog); filter(f_uucp); destination(uucp); };
log { source(s_syslog); filter(f_mail); destination(maillog); };
log { source(s_syslog); filter(f_mail); filter(f_info); destination(mailinfo); 
};
log { source(s_syslog); filter(f_mail); filter(f_warn); destination(mailwarn); 
};
log { source(s_syslog); filter(f_mail); filter(f_err); destination(mailerr); };
log { source(s_syslog); filter(f_debug); destination(debug); };
log { source(s_syslog); filter(f_messages); destination(messages); };
log { source(s_syslog); filter(f_emergency); destination(messages); };

Original issue reported on code.google.com by rfifa...@gmail.com on 17 Feb 2014 at 11:05