ekrn.exe memory leak on server

[unarcher 0]

Hi

One of our servers became unresponsive a few weeks ago.

We saw that ekrn.exe was eating more than 2000 MB RAM

 

We did a reboot, it came back to normal, around 80/100MB RAM

We upgraded the client to 5.0.2214

 

I did some monitoring graphs, and I noticed that server would crash the same way in a few weeks.

ekrn.exe is slowly eating RAM, actually 800 MB RAM.

It just slowly increase day after day

 

 

Server host a IBM Cognos application

 

 

Is there a fix to solve this?

Any way to restart ekrn.exe every weeks for example? (we tried to kill task access denied, no way to stop service, access denied)

Stopping protection for 10 minutes does not grant back memory

 

Hope I would not need to reboot server every few weeks, this server should never stop

[Marcos 5,259]

Is there a reason why you installed ESET Endpoint Antivirus or Security on servers instead of ESET File Security? Does the problem occur with protocol filtering disabled?

[unarcher 0]

I didn't know servers need a different version of ESET

Never had this kind of problems on any of our 40 others servers

 

 

Protocol filtering is actually activated.

I disabled this one but ekrn.exe still using a lot of ram. I dont know how to restart the program to see if this change would have an effect in the future

[webyourbusiness 4]

unarcher, you should talk to your reseller - I know that as our customers came up for renewal, we were explaining the difference between endpoint protection and the server versions for at least the last 2 years - this isn't something that just appeared in the last few weeks.  There have been a number of customers who said they either had no servers, or that they didn't want to change their licensing, who have later come back and added a server or two.   The customers who appeared most resistant to the changes have been the smaller businesses - but to offset the problems, we were offering free cross-grades to server licenses - ie, convert 1 or 2 of the current license to WFS licensing for free - this free cross-grade period has now ended, but the difference in cost between a WFS license and an endpoint license is quite minor (at least in the US).

 

The ESET server protection products are DEFINITELY what you want to be running on the servers - not a program optimized for an endpoint system.

[Marcos 5,259]

Protocol filtering is disabled in server products by default to prevent issues stemming from bugs in Windows Filtering Platform (BSOD, memory leaks, etc.) and to avoid excessive memory consumption if a higher number of connections is created at a time.