Apache mod-security

Re: ModSecurity 2.5.6 Released

It does not seem a likely error caused by ModSecurity as the request is 
not altered.  Does it go away without ModSecurity?  Was this an upgrade 
of ModSecurity or a new install?  Is this a proxy install or installed 
into the same Apache as IPS?

Upon a cursory google search, the error may be a load issue and/or a 
corrupted DB.  Contact the vendor and see what could cause the error.

-B

Grant Peel wrote:
> Hi all,
> 
> After installing mod_security, I have a cleints Invision Power Board that is
> returning this error.
> 
>   IPS Driver Error
>   There appears to be an error with the database.
>   You can try to refresh the page by clicking here
> 
> 
>   Odyly enough, I don't see anything in the logs....
> 
>   Any ideas?
> 
>   -Grant
> ----- Original Message -----
> From: "Brian Rectanus" <Brian.Rectanus <at> breach.com>
> To: "Mod Security" <mod-security-users <at> lists.sourceforge.net>; "Mod
> Packagers" <mod-security-packagers <at> lists.sourceforge.net>

(Continue reading)

headers

Grant Peel | 4 Aug 13:49

Re: ModSecurity 2.5.6 Released

Brian,

Yes, the problem does completely dissappear when mod_security is removed.

I first tried detect only, and the issue persisted. Then, I remarked out the 
LoadModule and Include config line from httpd.conf and the issue 
disappeared.

In the end, I removed the 2.5.6 version and reinstalled the 2.1.something, 
and it worked fine again.

-Grant

----- Original Message ----- 
From: "Brian Rectanus" <Brian.Rectanus <at> breach.com>
To: "Grant Peel" <gpeel <at> thenetnow.com>
Cc: "Mod Security" <mod-security-users <at> lists.sourceforge.net>
Sent: Monday, August 04, 2008 12:39 AM
Subject: Re: [mod-security-users] ModSecurity 2.5.6 Released

> It does not seem a likely error caused by ModSecurity as the request is 
> not altered.  Does it go away without ModSecurity?  Was this an upgrade of 
> ModSecurity or a new install?  Is this a proxy install or installed into 
> the same Apache as IPS?
>
> Upon a cursory google search, the error may be a load issue and/or a 
> corrupted DB.  Contact the vendor and see what could cause the error.
>
> -B
>

(Continue reading)