undefined method `slice!' for nil:NilClass about geoip HOT 7 CLOSED

This is commonly caused by concurrency issues. seek_record is safe, but are you sure you have a valid GeoIP instance?

from geoip.

Concurrency as in inter-process? We use Unicorn and not using threads, FWIW. We've been using this gem for years and haven't had any errors.

from geoip.

Oh, wait. The slice() you mention is in the IPv6 code, which is fairly new. What database file are you using? The file contains a binary search tree, where each bit of the IP address chooses one of two pointers from a node. The search is supposed to stop when a pointer points outside the tree data section. If this termination-test fails for some path down the tree (perhaps because the data size is wrong), the next node read may return nil and cause the exception in slice!.

To debug it, you need (or I need) a copy of the database file, and the IP address which fails. We need to know what the start and end offsets are of the search tree in the file, and the offset and contents of the node which points outside the tree and hence causes the failed read.

from geoip.

The failing IP address was 115.80.0.109, but as I said, I can't reproduce the error, which is weird.

The database file was downloaded from http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz a while ago - on Aug 22, 2012.

from geoip.

That file is not even an IPv6 data file, so the initialiser for GeoIP has failed to correctly read the file header and/or identify the file format version. I suspect perhaps an I/O error? How many times did the error occur?

from geoip.

There's no other errors - this error occurred only once.

As I said, we've been using the gem for years and haven't had any problems except this one. Here's the code we have in initializer:

class GeoIP
  DB = GeoIP.new(Rails.root.join('db/geoip/GeoLiteCity.dat'))
end

and rails console:

$ zeus console
Loading development environment (Rails 3.2.13)
[1] pry(main)> GeoIP::DB.city('166.137.186.47')
=> #<struct GeoIP::City
 request="166.137.186.47",
 ip="166.137.186.47",
 country_code2="US",
 country_code3="USA",
 country_name="United States",
 continent_code="NA",
 region_name="CA",
 city_name="Encinitas",
 postal_code="",
 latitude=33.037000000000006,
 longitude=-117.292,
 dma_code=825,
 area_code=760,
 timezone="America/Los_Angeles">

from geoip.

Put it down to a glitch in your I/O system. If it's not re-occuring, it's not a bug that can be fixed.

from geoip.