this is a testing epo server running on vm player 12 with 16 GB for the epo, it has been running for 3 days, what do you think? I will check the production server later.
What do you have enabled in access protection? It really wasn't an issue on the ePO server itself. It was on clients reporting to it. I'm sure the issue exists there too though. On a 2012 system I have no idea how long it will take to actually fill, but if your non-paged pool keeps rising, try disabling access protection to see if it drops and stops.
what is the ram size? and how long did it take to have the ultimate error generated when the pool runs out since the last system restart?
did you run full scan on this server?was it daily full scan?
2 GB of ram. On this particular system it took about a month and a half. It was a 2008r2 system, so it's non paged pool limit is about 1.5 GB, or 5 times 2003's. This lines up with the time it took.
In our production NOC, no scheduled scans. On-Access and scheduled scans aren't related to this. It seems tied directly to Access Protection.
This MFeB tag usage issue should be reported to Support.
I've seen a couple others come through already, so, there's definitely something of interest here. We don't have enough data to conclude yet whether this is a leak or just high usage.
A leak is defined as memory that's allocated and never released.
But the design and dependencies in the product are such that we are oft times victims of another's bad behavior - as in, we are tracking objects that they are leaking.
Whatever the case, the behavior needs to be understood first.