http://bugzilla.suse.com/show_bug.cgi?id=1069821 http://bugzilla.suse.com/show_bug.cgi?id=1069821#c5 Kristyna Streitova <kstreitova@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Kristyna Streitova <kstreitova@suse.com> --- (In reply to Orlando Robledano from comment #4)

Everything works perfectly, minus two things in the tests mod_security2 and mod_evasive that gives a warn.

Hello Orlando, This warning means that you are loading mod_evasive module twice. Please check APACHE_MODULES variable in your '/etc/sysconfig/apache2' file for duplicities.

in my case I solve the test, leaving this <IfModule mod_security2.c> SecStatusEngine On SecRuleEngine On SecRequestBodyAccess On Include /etc/apache2/mod_security2.d/*.conf </IfModule>

[Sat Nov 25 19:47:33.777552 2017] [:notice] [pid 7606] ModSecurity: StatusEngine call successfully sent. For more information visit: http://status.modsecurity.org/

but at least it does not work for me if I add to the default file at the beginning, only

SecStatusEngine On

I'm not sure if I understand you correctly. Do you want to say that if you just simply add 'SecStatusEngine On' to the beginning of the default mod_security2.conf file (or if you replace the whole default config file with 'SecStatusEngine On' only) it doesn't enable Status Engine? I've tried various combinations and I cannot reproduce this behaviour. Every time I put 'SecStatusEngine On' to the config file it enables Status Engine correctly. I'm closing this bug as WORKSFORME for now. But feel free to reopen it if you can provide me with specific steps (with a minimal configure file) how to reproduce this problem. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.