This should not happen just because you shut down the server (do you mean
this by "logger"?). However, if you shut down the forwarding rsyslog
("client") while the server is down, RELP does not protect against loss in
that case.

Rainer


On Wed, Sep 3, 2014 at 12:55 PM, Gareth Bult <[email protected]> wrote:

> Hi,
>
> I seem to have an issue with message loss when sending messages between a
> client and a server.
> - this seems to be repeatable.
>
> Scenario;
>
> Client using RELP (or tcp):
> Server using RELP (or tcp):
> (configs below)
>
> Client> logger HELLO WORLD
> Server> Sees "HELLO WORLD"
>
> <stop logger on server>
>
> Client> HELLO WORLD 1
> Client> HELLO WORLD 2
> Client> HELLO WORLD 3
> Client> HELLO WORLD 4
>
> Client log sees all entries.
>
> <start logger on server>
>
> Client> HELLO WORLD # (to force a flush)
>
>
> Server sees>
>
> Server> HELLO WORLD 1
> Server> HELLO WORLD 3
> Server> HELLO WORLD 4
> Server> HELLO WORLD
>
>
> Looking at the code, it appears to work as follows;
>
> a. Queue first entry
> b. Queue second entry
> c. Remove entry from Queue
> d. Submit to transport
> e. If transport fails, go into retry loop
> f. When transport comes back up, proceed to dequeue next entry (!)
>
> Issues;
> - this always skips an entry on reconnect, seems to happen with both RELP
> and TCP
> - I've not tested this, but I'm guessing shutting down the client while in
> retry mode also loses the entry as the retry entry isn't on the queue
>
> It "looks" like a design issue ... i.e. one-in-the-chamber rather than
> queue peek .. am I misreading? or does anyone have a workaround??
> (or did I do something bad in the config?)
>
> Server config;
>
>
>
> module(load="impstats")
> module(load="imuxsock")
> module(load="imklog")
> module(load="imrelp")
>
> input(type="imrelp" port="514")
>
> action(type="omfile" File="/var/log/syslog" sig.provider="gt"
> sig.keepTreeHashes="on" sig.keepRecordHashes="on")
>
>
>
>
> Client config;
>
>
>
>
> module(load="imfile")
> module(load="imuxsock")
> module(load="imklog")
> module(load="omrelp")
>
> $ActionForwardDefaultTemplate RSYSLOG_ForwardFormat
>
>
>
>
> type="omrelp"
>
> Target="<target server IP>"
> Port="514"
> queue.filename="forwarding"
> queue.type="LinkedList"
> queue.saveonshutdown="on"
> queue.maxdiskspace="1g"
> queue.spoolDirectory="/var/lib/rsyslog"
> queue.size="16384"
> queue.highwatermark="12000"
> action.resumeRetryCount="10"
> action.resumeInterval="5"
>
> )
>
>
> tia
>
> Regards,
> Gareth.
>
>
> _______________________________________________
> 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.

Reply via email to