GeoIP2 files present in /etc/ingress-controller/geoip, but the controller logs show "GeoLite2-City.mmdb not found" about ingress-nginx HOT 5 CLOSED

/remove-kind bug

Geoip legacy support was dropped in controlller v1.10 . So you could potentially use only geoip legacy in older versions of controller. I am not convinced you can have both enabled concurrently.

/close

from ingress-nginx.

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from ingress-nginx.

I think I found the issue, the v1.0.5 version looks for those files in /etc/nginx/geoip (which was later changed with this commit), but when I attach the volume into that directory, then I'm getting this error on startup:

Error: exit status 1
Error Opening file /etc/nginx/geoip/GeoIP.dat
2024/06/12 22:19:07 [emerg] 25#25: GeoIP_open("/etc/nginx/geoip/GeoIP.dat") failed in /tmp/nginx-cfg2362337476:116
nginx: [emerg] GeoIP_open("/etc/nginx/geoip/GeoIP.dat") failed in /tmp/nginx-cfg2362337476:116
nginx: configuration file /tmp/nginx-cfg2362337476 test failed

Because obviously these files are not present anymore, because I only include the .mmdb files for GeoIP2.

from ingress-nginx.

I have disabled use-geoip: false now, and it all started to work. However, I think we are using GeoIP as well in our organization. Can I have both of them enabled?

from ingress-nginx.

@longwuyuan: Closing this issue.

from ingress-nginx.