Out of range latitude and longitude about geoip HOT 8 CLOSED

GeoIP is not thread-safe, because it seeks a file pointer and reads from that location multiple times for each lookup. If you are initialising it once, you should store the handle in thread-local storage.

from geoip.

I'm not using threads, just a regular Rails app on Unicorn, which is single threaded. Do I still need to assign it to thread-local?

from geoip.

Try it with a Mutex and see if you still get problems, but the behaviour you describe sounds very like a race.

from geoip.

Well, we don't have config.threadsafe! on production, which means all requests are inside Rack::Lock so it's already mutex'd.

from geoip.

Perhaps, but try it anyway. EventMachine can still flip things around, I believe.

from geoip.

Will try, but I doubt that's the direct cause. We're not using EventMachine either. (If you use EM you'd use Rainbows! instead of Unicorn) It's a vanilla Rails 3.2 app with Unicorn, which I believe is the most popular setup.

from geoip.

Ok, well then I have no idea... but a lot of folk are using GeoIP without problems, including long-running instances. If you can find a cause and/or a fix, I'll be happy to re-open this issue.

from geoip.

Yeah I had been using the gem for quite a while without problems, then the problem started to appear at some point. I'll update when I find something out. Thanks for your time!

from geoip.