Hello everybody Now I'm trying to configure rsyslog to spool log messages to disk, while the connection to the central log collector is down. But it does not work......
I am using rsyslog v 3.21.2 I have configured the client rsyslog like this: $ModLoad imuxsock $ModLoad omrelp $WorkDirectory /var/spool/rsyslog $ActionQueueType LinkedList $ActionQueueFileName rsyslog-buffer $ActionResumeRetryCount -1 $ActionQueueSaveOnShutdown on *.* :omrelp:172.16.0.43:2514 Which is similar to the reliable forwarding configuration from the documentation, except that I prefer to use RELP. But When I test it, by stopping rsyslog on the central log collector, and running this small shell script on the client: #! /bin/sh for ((i=1;i<=10000;i+=1)); do logger Log line $i done The shell script does not complete until I restart rsyslog, on the central log collector, and when I look at the timestamps in the logfile on the log collector, I see a large time difference between log line 3303 and 3304. My plan is to get rsyslog to spool all log entries locally, while the connection the the central log collector is interrupted, and then flush all the spooled log messages to the central log collector when the communication is restored - while the rest of the client system continues with business as usual. I can send you a debug log is needed. -- David Darville _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
