Hi EXP, The module is logcollector. These leaks will be gone if you remove every localfile block with the eventchannel log format. Also, as an alternative, you can replace every localfile with the eventchannel log format by eventlog so that the events are returned in other format, this won't cause the memory leak to happen.
Kind regards, Cristina On Thursday, May 30, 2019 at 5:05:05 AM UTC+2, EXP wrote: > > yes, all windows happen > > 在 2019年5月29日星期三 UTC+8下午7:13:48，dan (ddpbsd)写道： >> >> On Wed, May 29, 2019 at 3:46 AM EXP <[email protected]> wrote: >> > >> > Hi ! >> > >> > wazuh version : 3.8.0-1 >> > >> > windows : Server 2012 R2 Standard 6.2.9200 x86_64 >> > >> > I found a Memory leak problem on windows. >> > >> > >> > When wazuh was just started, it used memory about 8M >> > >> > >> > But it will take up about 0.2M per min. >> > >> > >> > I wait a long time (about 2 day) , it use Memory 450M : >> > >> > >> > >> > >> > This is the memory situation of my machine for the last 2 weeks : >> > >> > >> >> Does this also happen if you use OSSEC? >> What is your configuration? >> >> > >> > >> > >> > >> > >> > >> > >> > -- >> > >> > --- >> > You received this message because you are subscribed to the Google >> Groups "ossec-list" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/ossec-list/e7ec5c67-403d-43a9-a48e-542bd206453b%40googlegroups.com. >> >> >> > For more options, visit https://groups.google.com/d/optout. >> > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ossec-list/ec9ec089-6010-461e-b758-7c1c91795945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
