HLstatsX: CE

This isn't necessarily a bug. If you have the geo lookup option set to use the binary file, both the file and the Geo::IP::PurePerl module are required to run.

Will resolve in next release. Just need better error handling.

So I've reviewed this, and I'm not sure how you've managed to get into this situation, to be honest. Here's the chunk of code that handles this:

hlstats.pl line 1709 as of hlx-16 r773:
@ my $geotell = ((!defined($g_gi)) ? -1 : tell $g_gi{fh});

if ($g_geoip_binary > 0 && $geotell == -1) {
        my $geoipfile = "$opt_libdir/GeoLiteCity/GeoLiteCity.dat";
        if (-r $geoipfile) {
            eval "use Geo::IP::PurePerl"; my $hasGeoIP = $ ? 0 : 1;
            if ($hasGeoIP) {
                $g_gi = Geo::IP::PurePerl->open($geoipfile, "GEOIP_STANDARD");
            } else {
                &printEvent("ERROR", "GeoIP method set to binary file lookup but Geo::IP::PurePerl module NOT FOUND", 1);
                $g_gi = undef;
            }
        } else {
            &printEvent("ERROR", "GeoIP method set to binary file lookup but $geoipfile NOT FOUND", 1);
            $g_gi = undef;
        }
    } elsif ($g_geoip_binary == 0 && $geotell > -1) {
        close($g_gi{fh});
        $g_gi = undef;
    }

We first check to see if the setting to use the binary file is enabled -- we should pass that check. Then we set a var to the DAT file path and then check if we can open it. If so, we immediately check if we have Geo::IP::PurePerl installed -- if perl can load this, it returns 1. If not, it returns 0. We then immediately check if we received a 1 (yes we have Geo::IP) or 0 (we don't). In your particular case, you have the file, so pass the first check. Then you don't have PurePerl loaded, so you should fail the check., which will set $g_gi to undefined, and then geolookup won't work anywhere else. However you're hitting $g_gi = Geo::IP::... Why, I'm not sure. Perhaps a really old Geo::IP::PurePerl module?

Anyways, something else I noticed is that if your .DAT file is corrupt you get weird errors like this. Check that your .DAT file isn't corrupted (just redownload it).

Since the logic appears to work according to all my testing, I'm rejecting this report.