On Thu, 1 Oct 2015, Kendall Green wrote:
Rsyslog 8.13 and 8.12 have issues when writing omfile to dfs fuse mount.
The messages are stuck in limbo until stopping or restarting rsyslog.
Changing the omfile destination from the fuse mount path to a local disk
directory results in logs output immediately.
There are no apparent issues with the fuse mounted filesystem (other than
rsyslog omfile delivery is stalled until service shutdown/restart).
Has anyone ran across this problem?
I'll bet that if you HUP rsyslog the contents will appear as well. It sounds
like the data is not getting flushed out to where it's visible to readers on
these more complex filesystems, but on a local filesystem you are seeing the
data flushed much more rapidly.
I'd also bet that if you keep writing data, eventually you will cross some
threshold and a large chunk of data will appear.
writing data out compressed increases the window for this because the
compression algorithm really wants a full buffer before it processes the data
and writes it out.
if you look at the omfile documentation, you will see soem flush and checkpoint
paramters that you can use to tweak this behavior. It sounds as if there may
also be some stuff you can do with fuse to adjust the amount of buffering and
when the data becomes visible.
David Lang
_______________________________________________
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.
