Closed rickhg12hs closed 4 years ago
From what I see there are two separate problems:
1) pip failed on compilation of bcrypt_python. Do you have libpython-devel
package installed? I guess there might be a missing dependency.
2) The second problem is that the SSH private key for the vagrant VM is inaccessible:
"Warning: Identity file /home/rick/ČVUT/B191/GitHub-CESNET-List/LiST/vagrant/.vagrant/machines/list-vagrant/virtualbox/private_key not accessible: No such file or directory.
Could you look around the .vagrant directory to see where the private key is stored? It is possible that it's location has changed in some recent version. In that case, you'd just need to update ansible/inventory/hosts file with the new location.
I started again from the beginning after installing the latest vagrant
rpm from hashicorp. It seems that my VirtualBox
install was too new for my vagrant
install. This created some issues because vagrant
seemed to fallback to libvirt
as the provider since it couldn't use VirtualBox
. I don't really understand all the issues.
There was still a vagrant up
failure because a build step failed when it couldn't find Python.h
. After vagrant ssh
, I sudo yum upgrade
and then sudo yum install python-devel python3-devel python34-devel
. Probably all *-devel weren't necessary, but I just want it to work.
After exit
on the VM, I vagrant reload --provision
on the host and it seemed to complete without error.
Is there a NEMEA sanity/smoke test that can be run to check if the VM is fully functional?
Thanks for testing this. I've just pushed a commit to fix the python34-devel issue. The problem arose when python newer than 3.4 became the default for pip3 in the system.
To see whether the system works, just open https://localhost:8443/scgui/ in your browser and you should see some data. To check the nemea output, use https://localhost:8443/liberouter-gui/nemea/events (admin/admin is the login). Moreover, the list of running modules should be available at https://localhost:8443/nemea-status/
Cool! It seems to work now! Thanks!
Where/what is the source for ipfixcol? And more generally, how do I explore/modify the NEMEA configuration? If I want to try to make a python module for NEMEA, is everything I need in this VM?
IPFIXcol is here: https://github.com/cesnet/ipfixcol It will be replaced by the new ipfixcol2 in near future, but ipfixcol2 is not included in LiST since the new one does not have all necessary features yet. However, if you only focus on Nemea framework, you can use the newer one, if you want to (the old one should be fine though).
For nemea, the documentation is right in the repo and on github pages:
As for whether everything is in the VM, well, no. You still have to checkout the nemea repositories and maybe install development tools (*-devel packages and maybe tools for compilation).
I want to try NEMEA and so I followed the recommendation at https://nemea.liberouter.org/doc/#usage-by-user by using the vagrant/ansible option.
Here's what happened on a Fedora 29 host after following the instructions.