Thelma
On 1/3/21 9:02 AM, Michael wrote:
> On Saturday, 2 January 2021 04:46:58 GMT the...@sys-concept.com wrote:
>> Status engine is currently disabled, enable it by set SecStatusEngine to On.
>>
>> How to enable "SecStatusEngine to On" in Apache 2.4
>>
>> From my log file:
>> [Fri Jan 01 19:44:52.649498 2021] [core:notice] [pid 14152] AH00094:
>> Command line: '/usr/sbin/apache2 -D DEFAULT_VHOST -D INFO -D SSL -D
>> SSL_DEFAULT_VHOST -D LANGUAGE -D PHP -D SECURITY -d /usr/lib64/apache2
>> -f /etc/apache2/httpd.conf'
>> [Fri Jan 01 21:10:26.781254 2021] [mpm_prefork:notice] [pid 14152]
>> AH00169: caught SIGTERM, shutting down
>> [Fri Jan 01 21:10:27.871561 2021] [:notice] [pid 16586] ModSecurity for
>> Apache/2.9.3 (http://www.modsecurity.org/) configured.
>> [Fri Jan 01 21:10:27.871577 2021] [:notice] [pid 16586] ModSecurity: APR
>> compiled version="1.7.0"; loaded version="1.7.0"
>> [Fri Jan 01 21:10:27.871579 2021] [:notice] [pid 16586] ModSecurity:
>> PCRE compiled version="8.44 "; loaded version="8.44 2020-02-12"
>> [Fri Jan 01 21:10:27.871581 2021] [:notice] [pid 16586] ModSecurity:
>> LIBXML compiled version="2.9.10"
>> [Fri Jan 01 21:10:27.871582 2021] [:notice] [pid 16586] ModSecurity:
>> Status engine is currently disabled, enable it by set SecStatusEngine to On.
>
> I would think you set it on in the config file for your vhost. I don't use
> this function, but there are instructions how to configure it here:
>
> https://github.com/SpiderLabs/ModSecurity/wiki
>
> HTH.
Adding:
SecStatusEngine On
to: 79_mod_security.conf
solved the problem, the error message went away, but I'm puzzled why these
messages appear in file: error_log
these are not error logs just information.
