Mentat

This is due to the GeoLite2 database license restrictions, as was discussed previously. A possible solution appeared on the mailing list on January 25th 2022 6:16 PM, a free 1:1 replacement. The following links are of interest:
https://github.com/adulau/mmdb-server/blob/main/db/GeoOpen-country.mmd
https://hdoc.csirt-tooling.org/GwZ3IOgPQXWRY5RA4Qm1pQ#

Rajmund Hruška, please have you followed these instructions: https://alchemist.cesnet.cz/mentat/doc/development/html/_doclib/development.html#development-with-vagrant ? I am unable to reproduce your error, perhaps I am doing something wrong. Have you tried vagrant destroy, then vagrant up to rebuild your box from scratch to make sure there are no weird artifacts breaking the provisioning? In another words: does the issue appear, when you try it on freshly cloned repository?

This looks to me like the configuration file for GeoIP was not placed into correct location prior to vagrant up as instructed in the manual and Vagrant is not able to perform the provisioning. By design it does not raise error, because in certain cases you might know, what you are doing.

There can also be an error when trying to build Vagrant box when you have previously used the repository for development the old way. For example everything breaks or Vagrant when toplevel .env file is present, because for previous development workflow it contains chroot path and breaks everything.

I tried destroying the vagrant

Jan Mach wrote in #note-3:

Rajmund Hruška, please have you followed these instructions: https://alchemist.cesnet.cz/mentat/doc/development/html/_doclib/development.html#development-with-vagrant ? I am unable to reproduce your error, perhaps I am doing something wrong. Have you tried vagrant destroy, then vagrant up to rebuild your box from scratch to make sure there are no weird artifacts breaking the provisioning? In another words: does the issue appear, when you try it on freshly cloned repository?

This looks to me like the configuration file for GeoIP was not placed into correct location prior to vagrant up as instructed in the manual and Vagrant is not able to perform the provisioning. By design it does not raise error, because in certain cases you might know, what you are doing.

There can also be an error when trying to build Vagrant box when you have previously used the repository for development the old way. For example everything breaks or Vagrant when toplevel .env file is present, because for previous development workflow it contains chroot path and breaks everything.

I followed the mentioned instructions. I tried vagrant destroy then vagrant up and it seems to be working now.

I deleted the virtual machine and the cloned repository. Then I cloned the repository again, I switched to devel, edited Makefile where I put the full address of mentat-alt server and I executed make data-fetch-config. Afterwards, I executed vagrant up followed by vagrant ssh. I switched to Mentat user by sm and entered the virtual environment by ve. Finally, I executed mentat-controller.py --command start and the same error appeared on my screen.

Then after recreating the virtual machine by vagrant destroy and vagrant up, mentat-controller.py --command start works fine.

Rajmund Hruska wrote in #note-6:

I deleted the virtual machine and the cloned repository. Then I cloned the repository again, I switched to devel, edited Makefile where I put the full address of mentat-alt server and I executed make data-fetch-config. Afterwards, I executed vagrant up followed by vagrant ssh. I switched to Mentat user by sm and entered the virtual environment by ve. Finally, I executed mentat-controller.py --command start and the same error appeared on my screen.

Then after recreating the virtual machine by vagrant destroy and vagrant up, mentat-controller.py --command start works fine.

I see the problem. The geoipupdate tool for vagrant is downloading files to different directory than for which the mentat-enricher is configured.

Attached commit resolves the issue. There was a problem with installation of geoipupdate tool, which removed prepared directory symlink. As a result database files were installed into different directory and mentat-enricher was unable to find them.