LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Why is syslog-ng not recording any log events in /var/log/syslog.log (https://www.linuxquestions.org/questions/linux-software-2/why-is-syslog-ng-not-recording-any-log-events-in-var-log-syslog-log-4175630638/)

ToffeeYogurtPots 05-28-2018 01:07 PM

Why is syslog-ng not recording any log events in /var/log/syslog.log
 
I'm trying to get some logs out of AppArmor'd applications in complain mode. Using aa-logprof it can retrieve messages from /var/log/syslog.log and build new profiles to restrict applications.

The log file is just repeating "starting up" and "shutting down" events. No other log events appear.

Here's a snippet of my /var/log/syslog.log:
Code:

May 28 18:38:54 hostname syslog-ng[3008]: syslog-ng shutting down; version='3.14.1'
May 28 18:38:56 hostname syslog-ng[13672]: syslog-ng starting up; version='3.14.1'

Here is my /etc/syslog-ng/syslog-ng.conf:
Code:

@version: 3.14
@include "scl.conf"
#
# /etc/syslog-ng/syslog-ng.conf
#

options {
  stats_freq (0);
  flush_lines (0);
  time_reopen (10);
  log_fifo_size (10000);
  chain_hostnames (off);
  use_dns (no);
  use_fqdn (no);
  create_dirs (no);
  keep_hostname (yes);
  perm(0640);
  group("log");
};

source src {
  system();
  internal();
};

destination d_authlog { file("/var/log/auth.log"); };
destination d_syslog { file("/var/log/syslog.log"); };
destination d_cron { file("/var/log/crond.log"); };
destination d_daemon { file("/var/log/daemon.log"); };
destination d_kernel { file("/var/log/kernel.log"); };
destination d_lpr { file("/var/log/lpr.log"); };
destination d_user { file("/var/log/user.log"); };
destination d_uucp { file("/var/log/uucp.log"); };
destination d_mail { file("/var/log/mail.log"); };
destination d_news { file("/var/log/news.log"); };
destination d_ppp { file("/var/log/ppp.log"); };
destination d_debug { file("/var/log/debug.log"); };
destination d_messages { file("/var/log/messages.log"); };
destination d_errors { file("/var/log/errors.log"); };
destination d_everything { file("/var/log/everything.log"); };
destination d_iptables { file("/var/log/iptables.log"); };
destination d_acpid { file("/var/log/acpid.log"); };
destination d_console { usertty("root"); };

# Log everything to tty12
destination console_all { file("/dev/tty12"); };

filter f_auth { facility(auth); };
filter f_authpriv { facility(auth, authpriv); };
filter f_syslog { program(syslog-ng); };
filter f_cron { facility(cron); };
filter f_daemon { facility(daemon); };
filter f_kernel { facility(kern) and not filter(f_iptables); };
filter f_lpr { facility(lpr); };
filter f_mail { facility(mail); };
filter f_news { facility(news); };
filter f_user { facility(user); };
filter f_uucp { facility(uucp); };
filter f_ppp { facility(local2); };
filter f_debug { not facility(auth, authpriv, news, mail); };
filter f_messages { level(info..warn) and not facility(auth, authpriv, mail, news, cron) and not program(syslog-ng) and not filter(f_iptables); };
filter f_everything { level(debug..emerg) and not facility(auth, authpriv); };
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); };
filter f_iptables { match("IN=" value("MESSAGE")) and match("OUT=" value("MESSAGE")); };
filter f_acpid { program("acpid"); };

log { source(src); filter(f_acpid); destination(d_acpid); };
log { source(src); filter(f_authpriv); destination(d_authlog); };
log { source(src); filter(f_syslog); destination(d_syslog); };
log { source(src); filter(f_cron); destination(d_cron); };
log { source(src); filter(f_daemon); destination(d_daemon); };
log { source(src); filter(f_kernel); destination(d_kernel); };
log { source(src); filter(f_lpr); destination(d_lpr); };
log { source(src); filter(f_mail); destination(d_mail); };
log { source(src); filter(f_news); destination(d_news); };
log { source(src); filter(f_ppp); destination(d_ppp); };
log { source(src); filter(f_user); destination(d_user); };
log { source(src); filter(f_uucp); destination(d_uucp); };
#log { source(src); filter(f_debug); destination(d_debug); };
log { source(src); filter(f_messages); destination(d_messages); };
log { source(src); filter(f_err); destination(d_errors); };
log { source(src); filter(f_emergency); destination(d_console); };
log { source(src); filter(f_everything); destination(d_everything); };
log { source(src); filter(f_iptables); destination(d_iptables); };

# Log everything to tty12
#log { source(src); destination(console_all); };

I'm aware that AppArmor can misbehave with syslog-ng. However, syslog-ng starts up without error. That said, I've disabled all AppArmor restrictions on syslog-ng.

Is there something I haven't configured with syslog-ng? I'm also using openrc if that could influence things.

AwesomeMachine 05-29-2018 01:21 AM

Which distro are you using; and which version? It looks to me like it's configured to log only syslog specific messages to syslog.log. But I don't use syslog-ng.

ToffeeYogurtPots 05-30-2018 12:48 AM

Quote:

Originally Posted by AwesomeMachine (Post 5860678)
Which distro are you using; and which version?

Parabola, pretty much Arch Linux without non-free stuff. It's rolling so there isn't a version. Syslog-ng is 3.14.

Quote:

Originally Posted by AwesomeMachine (Post 5860678)
It looks to me like it's configured to log only syslog specific messages to syslog.log. But I don't use syslog-ng.

That's what I thought, but I'm not too sure how to configure AppArmor complaints with syslog-ng.

AwesomeMachine 05-31-2018 02:15 PM

You'd have to read the syslog-ng.conf instructions. https://syslog-ng.com/documents/html...ng.conf.5.html


All times are GMT -5. The time now is 09:39 AM.