Rsyslog no envía loggings al server logstash en el puerto

Tengo dos rsyslog-client y rsyslog-server. Cuando traté de "registrar -p local1.notice ALGO", no veo ninguna información en el server de un cliente, pero de otra veo salida de logstash.

He copydo rsyslog.conf, es idéntico en estos dos serveres. ¿Qué pasa?

Cuando pruebo la connection a través de telnet xxxx 10514 desde el server de problemas, la connection de telnet está bien y veo los loggings de tcpdump. Y cuando cambio tcp, escuchar el puerto logstash en 514 todo funciona correctamente.

Cuando hago logger -p en el cliente problema, no veo nada en tcpdump -i en él.

Pero si hago lo mismo en el cliente "OK" veo el tráfico externo a través de tcpdump en el puerto 10514 (o algo diferente).

Cuando cambio el puerto logstash al problema 514 resuelto.

[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 (eg 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 requinetworking, # 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, eg 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 

Esta es la testing del cliente OK: logger -p local1.notice "testing del problema centos-26"

Logstash de salida:

 { "@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" } 

y esto es del nodo problemático: logger -p local1.notice "testing del problema centos-25"

Nada en salida

rsyslog.conf es idéntico en estos clientes.

Esto es del cliente 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 (eg 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 requinetworking, # 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, eg 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