Re: [mod-security-users] Problems accessing ModSecurity Console

[Ryan B. <Ryan.Barnett@Breach.com>]

> -----Original Message-----
> From: mod...@li... [mailto:mod-
> sec...@li...] On Behalf Of Dan Denton
> Sent: Friday, August 15, 2008 3:21 PM
> To: mod...@li...
> Subject: Re: [mod-security-users] Problems accessing ModSecurity
Console
> 
> Hello list, an update. Finally, the console seems to be responding by
> loading the home page, but it takes about 8 minutes to load. Once it
> loads,
> there appears to be 140,000+ alerts for one of my sensors. Upon
looking at
> the memory stats at the bottom of the page, the allocated and maximum
mem
> thresholds are both at approx 513MB. If I click on the sensor with the
> alerts to view the list, half the time I get a 500 error and the other
> half
> it loads, but attempting to click on anything means more time waiting
and
> another 500 error.
> 
> I'm guessing the massive amount of alerts being recorded are being
loaded
> into memory to be displayed and are exceeding the memory limits for
the
> GUI.
> I need to get some of the data out of the equation so I can atleast
load
> the
> GUI and get a picture of what's going on. How do I go about purging
what's
> in the inbound queue for the app, or purge out some of the already
> recorded
> alerts?
> 
> Is this even the right way to go?
[Ryan Barnett] The FAQ is your friend -
http://www.modsecurity.org/documentation/faq.html#d0e487