我有两个 rsyslog-client 和 rsyslog-server。当我尝试“logger -p local1.notice SOMETHING”时，我没有从一个客户端看到服务器上的任何信息，但从另一个客户端看到logstash 输出。
我已经复制了 rsyslog.conf，它在这两台服务器上是相同的。怎么了？
当我从问题服务器通过 telnet xxxx 10514 测试连接时，telnet 连接正常，并且我看到 tcpdump 日志。当我将 tcp 侦听 Logstash 端口更改为 514 时，一切正常。
当我在有问题的客户端上执行 logger -p 时，我在 tcpdump -i 中看不到任何内容。
但是，如果我在“OK”客户端上执行相同的操作，我会通过 tcpdump 看到外部流量到端口 10514（或其他端口）。
当我将logstash端口更改为514时，问题解决了。
[root@centos-25 ~]# cat /etc/rsyslog.conf
# rsyslog configuration file
# For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html
# If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html
#### MODULES ####
# The imjournal module bellow is now used as a message source instead of imuxsock.
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imjournal # provides access to the systemd journal
#$ModLoad imklog # reads kernel messages (the same are read from journald)
#$ModLoad immark # provides --MARK-- message capability
# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514
# Provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514
#### GLOBAL DIRECTIVES ####
# Where to place auxiliary files
$WorkDirectory /var/lib/rsyslog
# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
# File syncing capability is disabled by default. This feature is usually not required,
# not useful and an extreme performance hit
#$ActionFileEnableSync on
# Include all config files in /etc/rsyslog.d/
$IncludeConfig /etc/rsyslog.d/*.conf
# Turn off message reception via local log socket;
# local messages are retrieved through imjournal now.
$OmitLocalLogging on
# File to store the position in the journal
$IMJournalStateFile imjournal.state
#### RULES ####
$template DynFile,"/var/log/kibana/system-%HOSTNAME%.log"
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none ?DynFile
# The authpriv file has restricted access.
authpriv.* /var/log/secure
# Log all the mail messages in one place.
mail.* -/var/log/maillog
# Log cron stuff
cron.* /var/log/cron
# Everybody gets emergency messages
*.emerg :omusrmsg:*
# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler
# Save boot messages also to boot.log
local7.* /var/log/boot.log
# ### begin forwarding rule ###
# The statement between the begin ... end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
#
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
#$ActionQueueFileName fwdRule1 # unique name prefix for spool files
#$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible)
#$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
#$ActionQueueType LinkedList # run asynchronously
#$ActionResumeRetryCount -1 # infinite retries if host is down
#### Logstash #####
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
local1.notice @@192.168.253.26:10514;json-template
# ### end of the forwarding rule ###
$LocalHostName centos-25
# Include /var/log/dmesg for logging
$InputFileName /var/log/dmesg
$InputFileTag dmesg:
$InputFileStateFile stat-file1
$InputFileSeverity notice
$InputFileFacility local1
$InputRunFileMonitor
# end of include dmesg
这是来自 OK 客户端的测试： logger -p local1.notice "test from Problem centos-26"
Logstash 输出：
{
"@timestamp" => "2017-07-04T10:43:55.121Z",
"@version" => "1",
"message" => "Test From Centos-26",
"sysloghost" => "centos-26",
"severity" => "notice",
"facility" => "local1",
"programname" => "root",
"procid" => "-",
"host" => "192.168.253.26",
"port" => 40962,
"type" => "rsyslog"
}
这是来自问题节点：logger -p local1.notice“test from Problem centos-25”
输出内容
rsyslog.conf 在这些客户端上是相同的。
这是来自 OK 客户端：
# rsyslog configuration file
# For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html
# If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html
#### MODULES ####
# The imjournal module bellow is now used as a message source instead of imuxsock.
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imjournal # provides access to the systemd journal
#$ModLoad imklog # reads kernel messages (the same are read from journald)
#$ModLoad immark # provides --MARK-- message capability
# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514
# Provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514
#### GLOBAL DIRECTIVES ####
# Where to place auxiliary files
$WorkDirectory /var/lib/rsyslog
# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
# File syncing capability is disabled by default. This feature is usually not required,
# not useful and an extreme performance hit
#$ActionFileEnableSync on
# Include all config files in /etc/rsyslog.d/
$IncludeConfig /etc/rsyslog.d/*.conf
# Turn off message reception via local log socket;
# local messages are retrieved through imjournal now.
$OmitLocalLogging on
# File to store the position in the journal
$IMJournalStateFile imjournal.state
#### RULES ####
$template DynFile,"/var/log/kibana/system-%HOSTNAME%.log"
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none ?DynFile
# The authpriv file has restricted access.
authpriv.* /var/log/secure
# Log all the mail messages in one place.
mail.* -/var/log/maillog
# Log cron stuff
cron.* /var/log/cron
# Everybody gets emergency messages
*.emerg :omusrmsg:*
# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler
# Save boot messages also to boot.log
local7.* /var/log/boot.log
# ### begin forwarding rule ###
# The statement between the begin ... end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
#
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
#$ActionQueueFileName fwdRule1 # unique name prefix for spool files
#$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible)
#$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
#$ActionQueueType LinkedList # run asynchronously
#$ActionResumeRetryCount -1 # infinite retries if host is down
#### Logstash #####
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
local1.notice @@192.168.253.26:10514;json-template
# ### end of the forwarding rule ###
$LocalHostName centos-26
# Include /var/log/dmesg for logging
$InputFileName /var/log/dmesg
$InputFileTag dmesg:
$InputFileStateFile stat-file1
$InputFileSeverity notice
$InputFileFacility local1
$InputRunFileMonitor
# end of include dmesg