[mod-security-users] ModSecurity starting, but not logging even with debug
Brought to you by:
victorhora,
zimmerletw
From: <mj...@te...> - 2012-05-09 19:21:08
|
I have installed ModSecurity 2.6.5 on Apache httpd 2.0.52 and I see it load in the error_log, but I get nothing from the ModSecurity logs. I have set SecDebugLogLevel to 9. I have turned debug logs on in apache as well, but am seeing nothing in the logs about ModSecurity failing. Apache is writing to it's own logs as it should and the ModSecurity logs are set to be in the same directory as the Apache logs. I have rules linked in to the activated_rules directory. I copied the error_log from apache below. I have ModSecurity running great with the same configuration on a newer httpd 2.2.3, but am unable to upgrade this older server at the moment. Thanks in advance for your time and help, Steve ... caught SIGTERM, shutting down ... suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) ... ModSecurity for Apache/2.6.5 (http://www.modsecurity.org/) configured. ... ModSecurity: APR compiled version="0.9.4"; loaded version="0.9.4" ... ModSecurity: PCRE compiled version="4.5"; loaded version="4.5" ... ModSecurity: LIBXML compiled version="2.6.16" ... [notice] Digest: generating secret for digest authentication ... ... Digest: done ... LDAP: Built with OpenLDAP LDAP SDK ... LDAP: SSL support unavailable ... mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads. ... Apache configured -- resuming normal operations |