We saw this in a test deployment at one point - I'm not sure of the version number at the time, but 2.3 sounds about right. Upgrading to 2.4 resolved it for us.
On Fri, Sep 24, 2010 at 9:51 AM, Jason Mantor <[email protected]> wrote: > I have found a couple of machines were OSSEC and other processes were > spiking the CPU up to 100% every few minutes. > Restarting the service or rebooting the box cleared it up, but I'm > wondering if windows updates or some other environmental factor is > causing this? >
