MaxMind GeoLite2-City.mmdb errors

[Graham Faulkner]

Hi there,

This question relates to DSpace 5.10 (XML, Mirage 2) running on Ubuntu 16.04.7 LTS.

Our logs at /home/dspace/dspace/log/ contain error messages like the following.

ERROR org.dspace.statistics.SolrLogger @ Unable to get location of request:  The MaxMind DB file's data section contains bad data: invalid size of double.

ERROR org.dspace.statistics.SolrLogger @ Unable to get location of request:  Unexpected data type returned. The GeoIP2 database may be corrupt.

ERROR org.dspace.statistics.SolrLogger @ Unable to get location of request:  Something went horribly wrong in the decoder. An extended type resolved to a type number < 8 (7)

ERROR org.dspace.statistics.SolrLogger @ Unable to get location of request:  The MaxMind DB file's data section contains bad data: invalid size of double.

I made sure the mmdb file is working as expected, using the MaxMind tools https://github.com/maxmind/mmdbinspect and https://github.com/maxmind/mmdbverify.

The config at dspace/config/modules/usage-statistics.cfg set the db's location to /usr/share/GeoIP/GeoLite2-City.mmdb. Would it need to be at [dspace]/config/GeoLite2-City.mmdb instead?

Cheers,

Graham

Anyone have some pointers in the right direction on how to fix these errors? 

-----------------------------------------
Graham Faulkner
Web Developer / Programmer
Digital Initiatives, Library
University of Waterloo
Waterloo, Ontario N2L 3G1 CANADA
519-888-4567 x42461
graham....@uwaterloo.ca

[Jose Blanco]

I'm not sure. I have 6.3 and Mirage2 and have the file here:
[dspace]/config/GeoLite2-City.mmdb

I guess that would be an easy thing to test.

-Jose

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/YTOPR0101MB18994C57832F94099458CA0188190%40YTOPR0101MB1899.CANPRD01.PROD.OUTLOOK.COM.

[Graham Faulkner]

Thanks Jose. I'm hoping to test the change in production tomorrow. Oddly, our staging server doesn't show the same errors even though it's the same setup. I tested the change on staging and didn't see any errors still, so at least that bodes well! 

Cheers,

Graham

---

From: Jose Blanco <bla...@umich.edu>
Sent: Tuesday, October 27, 2020 10:53 AM
To: Graham Faulkner <graham....@uwaterloo.ca>
Cc: dspac...@googlegroups.com <dspac...@googlegroups.com>
Subject: Re: [dspace-tech] MaxMind GeoLite2-City.mmdb errors