Displaying 3 results from an estimated 3 matches for "inputtcpserverrun".
2018 Sep 06
6
rsyslog listening on high port
Attempting to lookup why rsyslogd is listening on the high port
UDP/51427. Have not succeeded in what this port is used for and what
directive controls what interface it binds to.
[root at bedrock ~]# netstat --listen --inet --program --numeric | grep syslog
udp??0??0 0.0.0.0:51427??0.0.0.0:*???66655/rsyslogd?
--
Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383
2012 Jan 06
1
rsyslog server cannot get the logs
I have an rsyslog server which is running Debian Stable,
and its version of rsyslog is 4.6.4-2.
All of my Debian Stable server can send log to it now.
and run both
nc $IP $PORT <<< "HELLO"
and
echo "HELLO" | nc $IP $PORT
on client, I can get log on the server.
While for my CentOS 5.7 server,
nc $IP $PORT <<< "HELLO"
works well, but
echo
2012 Jul 11
0
[CentOS 6.3] rsyslog 5.8.10-2 - PreserveFQDN directive ignored
...(e.g. via logger command)
$ModLoad imklog.so # provides kernel logging support (previously
done by rklogd)
#$ModLoad immark.so # provides --MARK-- message capability
# Provides UDP syslog reception
#$ModLoad imudp.so
#$UDPServerRun 514
# Provides TCP syslog reception
#$ModLoad imtcp.so
#$InputTCPServerRun 514
#### GLOBAL DIRECTIVES ####
# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
#
# (BUG!)
# FQDN must be the first directive or it is not honored
# http://bugzilla.adiscon.com/show_bug.cgi?id=192
#$PreserveFQDN on
... omitted...
</config>
[0] http:...