Spork Schivago
- Total activity 692
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 97
Comments
Recent activity by Spork Schivago-
Maybe something like: /usr/local/apache/logs/modsec_audit.log { rotate 15 daily missingok compress postrotate /usr/local/cpanel/scripts/restartsrv_httpd 2> /dev/null > ...
-
...I think the best help I can give is to describe how I analyze concerning modsec hits... This helped a lot, you sharing how you analyze the logs. I've been analyzing them incorrectly. This w...
-
a) The Requests from 127.0.0.1. I did not address this very well. All the logs you posted regarding the [hostname "127.0.0.1"> issue were about log events that occurred within one second of each ot...
-
I see some stuff in the access_log as well: 41.209.71.187 - - [21/Jun/2017:00:08:27 -0400] "GET login.cgi HTTP/1.0" 400 10084 "-" "-" 127.0.0.1 - - [21/Jun/2017:11:15:32 -0400] "GET /whm-server-s...
-
I should add that I do have some IP addresses whitelisted in CSF and ModSec, but they belong to ScanMyServer.... # CSF Whitelisted IP addresses # Our home IPv4 address - Thu Apr 20 22...
-
And here's where the hostname changes to 127.0.0.1. [Wed Jun 21 10:59:16.225079 2017] [:error] [pid 21522] [client 177.19.152.77] ModSecurity: Warning. Operator EQ matched 0 at REQUEST_HEADERS. [...
-
Hello, Do you see any corresponding entries in /usr/local/apache/logs/error_log? Thank you. Only the ModSec warnings and access denied messages. So ModSec definitely seemed to have caught every...
-
Seems to be fixed now. Thanks!
-
This happens to me from time to time with EPEL. I generally just skip that repo for that update and try it again later I missed this post earlier. I think we were posting at the same time. I was...
-
Hello, That looks like an issue with the EPEL repository. I'm not seeing the same error message when running "yum check-updates" on test systems with the stock CentOS repos. Thank you. But when y...