Memory issues on NXLog
Tags:
NXLog Community Edition
#1
Wernervdmerwe
We have an application that does some multiple updates every morning between 6am and 7am. During this time, it generates massive amounts of log entries. This in turn causes the box to run out of memory, triggering Linux's OOM daemon. Running the NxLog-ce.
I have added
PersistLogqueue TRUE SyncLogqueue TRUE CacheFlushInterval always CacheSync TRUE
To the config, and will see if that makes a difference, but it seems that is more to safeguard messages from being lost.
I have looked at https://nxlog.co/question/802/nxlog-ce-memory-leak and https://nxlog.co/question/4132/cache-disk-works-not-good, but not sure those two are what I am after?
#1
Wernervdmerwe
We have an application that does some multiple updates every morning between 6am and 7am. During this time, it generates massive amounts of log entries.
This in turn causes the box to run out of memory, triggering Linux's OOM daemon. Running the NxLog-ce.
I have added
PersistLogqueue TRUE
SyncLogqueue TRUE
CacheFlushInterval always
CacheSync TRUE
To the config, and will see if that makes a difference, but it seems that is more to safeguard messages from being lost.
I have looked at https://nxlog.co/question/802/nxlog-ce-memory-leak and https://nxlog.co/question/4132/cache-disk-works-not-good, but not sure those two are what I am after?
Hey Werner,
Not sure if the same case. Can you paste your config here?
