Welcome to WebmasterWorld Guest from 54.159.246.164

Forum Moderators: Ocean10000 & incrediBILL & phranque

Message Too Old, No Replies

Upgraded Apache now ModSecurity is not working.

Upgrade Apache ModSecurity

   
4:57 pm on Aug 20, 2009 (gmt 0)

5+ Year Member



Hey Guys, can anyone help me out here. Earlier this week I upgraded Apache from 2.2.6 to 2.2.13 and Modsecurity stopped working. This is what I see in my error log:

[error] ModSecurity: ModSecurity requires mod_unique_id to be installed.

I re-installed the new version of Apache with "--enable-unique-id" and I now see this module listed as installed:

[root@digm1 logs]# httpd -l
Compiled in modules:
core.c
mod_authn_file.c
mod_authn_default.c
mod_authz_host.c
mod_authz_groupfile.c
mod_authz_user.c
mod_authz_default.c
mod_auth_basic.c
mod_include.c
mod_filter.c
mod_log_config.c
mod_env.c
mod_unique_id.c
mod_setenvif.c
mod_version.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_asis.c
mod_cgi.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_so.c

I also added the LoadModule to my httpd.conf:

LoadModule unique_id_module modules/mod_unique_id.so

But I still get the Modsecurity error above and nothing is written to the modsecurity logs. Any idea what I am missing? Thanks

8:11 pm on Aug 20, 2009 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Just to be clear, did you restart your server after changing httpd.conf?

Jim