Status engine is currently disabled ?

Hello, all

Here info: centos 6.6 with cwp 0.9.7, how to solve this warn below:

[root@server01]# tail  /usr/local/apache/logs/error_log
[Tue Jan 20 16:47:20 2015] [notice] caught SIGTERM, shutting down
[Tue Jan 20 16:47:21 2015] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Tue Jan 20 16:47:21 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Tue Jan 20 16:47:21 2015] [notice] ModSecurity for Apache/2.8.0 (http://www.modsecurity.org/) configured.
[Tue Jan 20 16:47:21 2015] [notice] ModSecurity: APR compiled version="1.5.1"; loaded version="1.5.1"
[Tue Jan 20 16:47:21 2015] [notice] ModSecurity: PCRE compiled version="7.8 "; loaded version="5.0 13-Sep-2004"
[Tue Jan 20 16:47:21 2015] [warn] ModSecurity: Loaded PCRE do not match with compiled!
[Tue Jan 20 16:47:21 2015] [notice] ModSecurity: LIBXML compiled version="2.7.6"
[Tue Jan 20 16:47:21 2015] [notice] Status engine is currently disabled, enable it by set SecStatusEngine to On.
[Tue Jan 20 16:47:22 2015] [notice] Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips configured -- resuming normal operations

Sorry to open this old thread but I am facing the same issue. Is there any ayone who can help us to resolve the issue?

try to rebuild modsecurity by running modsecurity installer again form cwp

This is what I'm getting:

Mod Security Configurator For instructions please use our forum.
 We recommend to use Comodo WAF rules as they are much simplier and easier for beginners.

Mod Security configuration is: not installed [test]
 If you get 403 Forbidden message that means that the mod_security rules work, don't forget to check the logs below.

 Select which rules you would like to use:
 OWASP old (Old rules which come as default with CWP)
 OWASP latest (Latest version of OWASP rules with automatic updates) [CWPpro required]
 Comodo WAF (Latest version of Comodo WAF rules with automatic updates) [CWPpro required] Installed version: 1.117

try to rebuild modsecurity by running modsecurity installer again form cwp

In newest CWP the mod config file is no longer available to edit.  So, I went to filezilla and whitelisted my IP

SecRule REMOTE_ADDR "@ipMatch 71.0.69.137" "id:26091975,phase:2,pass,nolog,allow,ctl:ruleEngine=Off"

I rebooted apache and now modsec will not run..or at least there are no log entries.  Test show Fobidden 403 though.

In newest version config files are visible withing mod security module in cwp.admin

You should check error log for any issues

In newest version config files are visible withing mod security module in cwp.admin

You should check error log for any issues

I have 20+ websites.  Writing a single rule for each domain name is not convenient.

Log errors will not fix bad uninstall.

I know this is an old thread, but I saw this error today (Status Engine is Currently Disabled) and found this post while searching for a solution. So I thought I'd share my findings with anyone else who has the same 'error'.

It seems that it is OK for the Status Engine to be disabled because all it does is provide feedback to the ModSecurity team.

See here : https://www.trustwave.com/Resources/SpiderLabs-Blog/Introducing-ModSecurity-Status-Reporting/

Hope someone finds it useful.