-
Notifications
You must be signed in to change notification settings - Fork 1.6k
ModSecurity 3 and NginX-Connector can not log with 'SecAuditLogType Concurrent' #1585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @nobodysz, Most likely this is happening because your ModSecurity was not compiled with JSON support. As of 3036462 there will be a message in the file indicating that JSON support was not enable. |
I try to recompiled ModSecurity and confirm configure with yajl.
And the problem remains. |
By the way ,what should I use to send logs to waf-fle with modsecurity v3. |
@nobodysz you can set debug level to 9 and see if there is an error message for saving to audit_log. Check also the permissions of this directory. You can make it's user and group like nobody:nobody (the user of nginx) - this solved the problem to me. |
@intelbg I'm sure the log's directory has enough permission, but the problem remains~ |
Hi @nobodysz, Within the latest version in GitHub you should not get an empty file. The file is either not saved or saved with some content. The content however, may be "JSON is not supported". I see that you are running 304a, please try to upgrade the code to at least: 3036462 better if you can have the most recent version. |
Dear ModSecurity-Team,
I have compiled nginx 1.12 with libmodsecurity v3, nginx connector and CRS3.
I can get audit log with 'SecAuditLogType Serial',
But I can't understand why modsec audit log does not log anything in StorageDir when I set it to
All of the AuditLogFile in /var/log/mlogc/ are empty.
But the modsec_audit.log is OK.
[10/Oct/2017:17:00:14 +0800] "POST /index/index HTTP/1.1" 200 16384 - "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0" 150762601452.356607 - /var/log/mlogc/data/20171010/20171010-1700/20171010-170014-150762601452.356607 0 0.000000 md5:d41d8cd98f00b204e9800998ecf8427e
Regards,
Nobodysz
The text was updated successfully, but these errors were encountered: