Hi, I use disk-assisted queue to buffer logs when remote logging host is unavailable or network is down. The problem I ran into is when the disk queue hits the maximal disk space limit, it stops accepting incoming logging entries as expected, but it doesn't flush existing queued entries when the remote host is back to normal. If the remote host is set before maximal disk space limit is reached, it works without issues. I tested on rsyslog 5.8.6, 5.8.13 and 7.3.13, neither seems to be working.
My rsyslog configuration on sending end: # start forwarding rule 1 of 1 $ActionQueueType LinkedList $ActionQueueFileName srvrfwd $ActionResumeRetryCount -1 $ActionQueueSaveOnShutdown on $ActionQueueMaxDiskSpace 100000000 $ActionQueueSize 200000 # Tried 100000 as well $ActionQueueHighWaterMark 600 $ActionQueueLowWaterMark 200 $ActionQueueTimeoutEnqueue 1 #local5.* :omrelp:127.255.255.1:20514 # Invalid IP to trigger log buffering local5.* :omrelp:172.17.5.28:20514 # Real IP to trigger log forwarding # end forwarding rule 1 of 1 Has anyone seen similar issues? Thanks, Fajun _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
