/etc/cron.weekly/geoipupdate:
Received Error -21 (Sanity check database_info string failed) when attempting to update GeoIP Database
Received Error -21 (Sanity check database_info string failed) when attempting to update GeoIP Database
Received Error -21 (Sanity check database_info string failed) when attempting to update GeoIP Database
Received Error -21 (Sanity check database_info string failed) when attempting to update GeoIP Database
If I’m honestly I don’t know. I thougt it is part of ntop or suricata, so they can locate hosts or something.
If it’s not NS related, I’m sorry to bother you.
This machine is migrated from NS6 to NS7. Maybe an old artefact?
And started to supply a new db, called GeoLite2 https://dev.maxmind.com/geoip/geoip2/geolite2/
which are provided in CSV and binary format. Also with API for manage.
Data is provided under Creative Commons Attribution-ShareAlike 4.0 International License.
So I was right with my assumption that GeoIP is needed for notop and suricata.
But if GeoIP 1.x is no longer supported and the database no more updated, it’ll become more and mor inaccurate. Wouldn’t it be worth to think about a change to GeoIP 2.x or something similar (i.e. ip2location lite)?
I think that both projects will have to take that decision… Suricata and NTOP will take a choice and will upgrade.
Therefore, NethServer maybe can upgrade package too. Or change addon.