What you'll need to do is just uncomment 2 lines in the /etc/rsyslog.conf file:
# provides UDP syslog receptionThat's if you want to provide UDP syslog service. Uncomment the following 2 lines if you want to provide TCP syslog service:
$ModLoad imudp
$UDPServerRun 514
# provides TCP syslog receptionOnce you've made the changes, either reload or restart the rsyslogd service:
$ModLoad imtcp
$InputTCPServerRun 514
myhost:/etc# /etc/init.d/rsyslog reloadI've chose to enable UDP for my server. We'll use netstat to check if rsyslogd is listening to the specified port:
Reloading enhanced syslogd: rsyslogd.
myhost:/etc# netstat -tlnup | grep 514rsyslogd is indeed listening to the proper port and protocol.
udp 0 0 0.0.0.0:514 0.0.0.0:* 13282/rsyslogd
udp6 0 0 :::514 :::* 13282/rsyslogd
Next stop, actual logging and probably more configuration :)
6 comments:
how i have to configure the /etc/rsyslog.conf file in the client-side? i have to insert the server address?
Hi roberto,
Please look at my other post here:
http://techtots.blogspot.com/2011/12/rsyslogd-logging-to-remote-server.html
HTH
Thanks for this. It got me out of a quick bind.
Hi, I followed your instructions with rsyslog V5.8.6 Ubuntu 12.04.
I configured udp and successfully ran the netstat cmd with the same out as you. I generated a syslog msg from a remote device and it is not being received.
syslog did show the following error message after the restart:rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
I did check that out but didn't get very far.
Any ideas?
Damn.... it started working???
Not sure why. Seems the error messages were just a red herring.
Thanks for your instructions!!!
Bob
Damn, seems like the error message was a red herring.
Thanks for your instructions!!
Post a Comment