-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Modsecurity is not compiling (bool modsecurity::Utils::GeoLookup::lookup Error) #2254
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
I think (if you definietly want to use the current master) you have to replace this line with
Looks like the ABI had changed in libmaxminddb in version 1.4.2, and there is an affected change which caused this error. Another solutions: use 3.0.4, or go back to cd9b8a:
(The next commit is 4f13fe, which makes @zimmerle - it would be good to collect and listed the minimal library versions. There isn't any information about this. |
Hi @OptimBro, That is happening because of you may have an outdated version of lbmaxmind. You may want to use the latest version for libmaxmind. If upgrade is not an option, you may want to disable the libMaxMind dependency using |
hello, just upgraded to the latest nginx 1.17.10 and had to recompile. Same problem |
Hi @albgen, Make sure you have the newest version of ModSecurity. Check the advise that was stated above: upgrade your libmaxmind or try to disable it by using |
Hi zimmerle, Yes, i compiled removing the libmaxmind library. Thanks |
Describe the bug
Modsecurity is not compiling
Logs and dumps
To Reproduce
Compile it from source
Used, above command from this script: https://github.com/OptimBro/OptimStack/blob/master/OptimStack.sh
Expected behavior
A clear and concise description of what you expected to happen.
Server (please complete the following information):
Additional context
Guess: MaxMind has stopped providing GEOIP files, now asking for license and key, that could be the problem, if ModSecurity uses it, I guess. I can see in the above logs.
PS: I'm not good at reporting bugs, so pardon me, if I presented in an unprofessional way.
Thanks :)
The text was updated successfully, but these errors were encountered: