Yes, rsyslog should pick up after a gap with TCP
I'm not sure what you're talking about when you refer to a gui.
I would suggest setting up a test where you just send a few messages and run
rsyslog in debug mode ( -dn ) and look to see what it's reporting when you down
the remote server and bring it back up.
David Lang
On Sat, 25 May 2013, Roberto Giordani
wrote:
Hello,
My distro for Client is Rhel 5.9 x86_64 with rsyslog 5.8.10 and I've Selinux
disabled and I can't use Selinux enabled.
On server there is last rsyslog stable 7.2 build from source. (I've found no
java source include for gui :-(
Finally after restart I've found .qi too and I tried to use the qi tools from
7.2 souce directory but running I didn't note any message recovery.
Finally, I want to understand if a TCP connection from client to server (no
RELP) and my configurations should be able to flush queue when rsyslog server
became available again after e short down.
Regards,
Roberto.
On 05/24/2013 07:20 PM, David Lang wrote:
there should be a .qi file in that directory, without it you will have
problems.
David Lang
On Fri, 24 May 2013, Roberto Giordani wrote:
Date: Fri, 24 May 2013 10:51:57 +0200
From: Roberto Giordani <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: rsyslog-users <[email protected]>
Subject: [rsyslog] Avoid lose messages when Centralized Rsyslog server
is down
Hello,
I need to know how to flush messages cached on disk on rsyslog client
when Centralized Rsyslog server was down for short period.
I use a tcp connection not RELP.
This is my configuration on client
$ModLoad imfile
$InputFileName /appl/logs/test1.log
$InputFileTag test1
$InputFileStateFile file1
$InputFileSeverity debug
$InputFileFacility local6
$InputRunFileMonitor
$InputFilePersistStateInterval 1000
$WorkDirectory /var/lib/rsyslog
$ActionQueueFileName fwdRule1
$ActionQueueMaxDiskSpace 1g
$ActionQueueSaveOnShutdown on
$ActionQueueType Disk
$ActionResumeRetryCount -1
$ActionQueueTimeoutEnqueue 1
$ActionSendResendLastMsgOnReconnect on
local6.debug @@10.10.1.10:10514
I see the /var/lib/rsyslog/fwdRule1.00000053 that contains the msg
recieved from local6.debug, but if I stop the Centralized Rsyslog
server 10.10.1.10 for 5 minutes, on restart the queue on client was
not flushed to it.
Could someone please indicate me the flow to reach the goal?
Thanks.
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
