不记录kern消息的rsyslog

Question

我使用Ubuntu20.04与rsyslog和最新的软件包。我想记录来自iptable的消息。

我可以在dmesg中看到这些消息--它显示了我所期望的数据。

deploy$ dmesg -x
kern  :warn  : [37464969.767649] iptables: Incoming netperf IN=venet0 OUT= MAC= SRC=x.x.x.x DST=y.y.y.y LEN=60 TOS=0x00 PREC=0x00 TTL=51 ID=43720 DF PROTO=TCP SPT=46221 DPT=12865 WINDOW=29200 RES=0x00 SYN URGP=0
kern  :warn  : [37464969.767679] iptables: Incoming netperf IN=venet0 OUT= MAC= SRC=x.x.x.x DST=y.y.y.y LEN=60 TOS=0x00 PREC=0x00 TTL=51 ID=34689 DF PROTO=TCP SPT=58437 DPT=12865 WINDOW=29200 RES=0x00 SYN URGP=0

但是.这些消息从未保存在/var/log目录中的任何日志文件中。

据我所知，我的/etc/rsyslog.conf (以下)文件与原始文件没有变化，默认规则(在/etc/rsyslog.d/50-default.conf中--更低的部分)应该会导致将kern消息写入/var/log/kern.log。/etc/rsyslog.d/中唯一的其他文件是postfix.conf (next)。

文件权限似乎并不令人惊讶.(以下两份报告)

有什么想法？我遗漏了什么？谢谢。

/etc/rsyzab.conf

# /etc/rsyslog.conf configuration file for rsyslog
#
# For more information install rsyslog-doc and see
# /usr/share/doc/rsyslog-doc/html/configuration/index.html
#
# Default logging rules can be found in /etc/rsyslog.d/50-default.conf


#################
#### MODULES ####
#################

module(load="imuxsock") # provides support for local system logging
#module(load="immark")  # provides --MARK-- message capability

# provides UDP syslog reception
#module(load="imudp")
#input(type="imudp" port="514")

# provides TCP syslog reception
#module(load="imtcp")
#input(type="imtcp" port="514")

# provides kernel logging support and enable non-kernel klog messages
#module(load="imklog" permitnonkernelfacility="on")

###########################
#### GLOBAL DIRECTIVES ####
###########################

#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat

# Filter duplicated messages
$RepeatedMsgReduction on

#
# Set the default permissions for all log files.
#
$FileOwner syslog
$FileGroup adm
$FileCreateMode 0640
$DirCreateMode 0755
$Umask 0022
$PrivDropToUser syslog
$PrivDropToGroup syslog

#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog

#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf

/etc/rsyzab.d/50-default.conf

#  Default rules for rsyslog.
#
#           For more information see rsyslog.conf(5) and /etc/rsyslog.conf

#
# First some standard log files.  Log by facility.
#
auth,authpriv.*      -/var/log/auth.log
*.*;auth,authpriv.none      -/var/log/syslog
#cron.*          -/var/log/cron.log
#daemon.*           -/var/log/daemon.log
kern.*  -/var/log/kern.log
#lpr.*              -/var/log/lpr.log
mail.*              -/var/log/mail.log
#user.*             -/var/log/user.log

#
# Logging for the mail system.  Split it up so that
# it is easy to write scripts to parse these files.
#
#mail.info          -/var/log/mail.info
#mail.warn          -/var/log/mail.warn
mail.err         -/var/log/mail.err

#
# Some "catch-all" log files.
#
#*.=debug;\
#   auth,authpriv.none;\
#   news.none;mail.none -/var/log/debug
#*.=info;*.=notice;*.=warn;\
#   auth,authpriv.none;\
#   cron,daemon.none;\
#   mail,news.none      -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg             :omusrmsg:*

#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;\
#   news.=crit;news.=err;news.=notice;\
#   *.=debug;*.=info;\
#   *.=notice;*.=warn   /dev/tty8

/etc/rsyzab.d/postfix.conf.

# Create an additional socket in postfix's chroot in order not to break
# mail logging when rsyslog is restarted.  If the directory is missing,
# rsyslog will silently skip creating the socket.
$AddUnixListenSocket /var/spool/postfix/dev/log

ls -al /etc/rsys*

deploy:/etc$ ls -al /etc/rsys*
-rw-r--r-- 1 root root 1383 Oct 12 10:43 rsyslog.conf

rsyslog.d:
total 24
drwxr-xr-x   2 root root    4096 Feb 16 08:28 .
drwxr-xr-x 114 root deploy 12288 Feb 15 18:41 ..
-rw-r--r--   1 root root    1124 Feb 16 07:48 50-default.conf
-rw-r--r--   1 root root     242 Jun 19  2020 postfix.conf

ls -al /var/log/kern.log

deploy:/etc$ ls -al /var/log/kern.log
-rw-r----- 1 syslog adm 0 Feb 15 18:50 /var/log/kern.log

sudo systemctl状态系统d-日记. status

deploy:~$ sudo systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
     Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
     Active: active (running) since Tue 2021-02-16 09:02:16 EST; 45min ago
TriggeredBy: ● systemd-journald.socket
             ● systemd-journald-audit.socket
             ● systemd-journald-dev-log.socket
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
   Main PID: 179 (systemd-journal)
     Status: "Processing requests..."
      Tasks: 1 (limit: 38354)
     Memory: 52.7M
     CGroup: /system.slice/systemd-journald.service
             └─179 /lib/systemd/systemd-journald

Jan 31 21:42:14 example.com systemd-journald[35283]: Journal stopped
Jan 31 21:42:21 example.com systemd-journald[180]: Journal started
Jan 31 21:42:21 example.com systemd-journald[180]: Runtime Journal (/run/log/journal/77578ccc822c4f1aaa10385353e145a7) is 2.5M, max 20.4M, 17.9M free.
Jan 31 21:42:22 example.com systemd-journald[180]: Time spent on flushing to /var/log/journal/77578ccc822c4f1aaa10385353e145a7 is 29.543ms for 19 entries.
Jan 31 21:42:22 example.com systemd-journald[180]: System Journal (/var/log/journal/77578ccc822c4f1aaa10385353e145a7) is 32.0M, max 4.0G, 3.9G free.
Feb 16 09:02:10 example.com systemd-journald[180]: Journal stopped
Feb 16 09:02:16 example.com systemd-journald[179]: Journal started
Feb 16 09:02:16 example.com systemd-journald[179]: Runtime Journal (/run/log/journal/77578ccc822c4f1aaa10385353e145a7) is 2.5M, max 20.4M, 17.9M free.
Feb 16 09:02:16 example.com systemd-journald[179]: Time spent on flushing to /var/log/journal/77578ccc822c4f1aaa10385353e145a7 is 54.224ms for 20 entries.
Feb 16 09:02:16 example.com systemd-journald[179]: System Journal (/var/log/journal/77578ccc822c4f1aaa10385353e145a7) is 160.0M, max 4.0G, 3.8G free.
deploy:~$

Answer 1

更新：它现在正在工作。在对此进行故障排除时，我做了大量更改，但我认为问题在于，下面的行是在/etc/rsyslog.conf注释中注释掉的，这会导致日志条目如预期的那样出现。

#module(load="imklog" permitnonkernelfacility="on")

在这个过程中，我收集了一堆关于rsyslog的事实，我把它们放在这里给下一个有这种麻烦的穷人(包括我)：

1. iptables总是通过kern.*工具发送日志消息
2. rsyslog配置在/etc/rsyslog.conf中；它经常指向/etc/rsyslog.d中的单独文件，为各种类型的日志文件提供附加规则。
3. (正如我所了解的)，需要用module(load="imklog" ...)加载内核日志模块。其他设施可能需要其他模块。
4. /etc/rsyslog.d/50-default.conf有一行用于将kern.*消息定向到特定的日志文件。
5. 在Ubuntu20.04(至少)配置更改后，您需要使用sudo service rsyslog restart
6. rsyslogd -N1检查rsyslog配置中的错误
7. journald似乎与我遇到的任何问题无关。

一些我无法证实的事情:这并不意味着它不像记录的那样工作，只是我可能做错了。

1. 我无法使一个文件/etc/rsyslog.d/10-iptables.conf覆盖目录中的50-default.conf文件(将某些消息定向到一个单独的文件)。