-
Notifications
You must be signed in to change notification settings - Fork 93
Missing steps in Vagrant setup? #16
Comments
And for fun, here is the entire log output I got after all those steps – I still don't know what the problem is, hopefully you can help me:
|
I just tested the vagrant setup yesterday to reproduce a different issue. It worked fine for me. It looks like the initial provisioning of the vagrant box failed. Can you please |
And yes, you are not supposed to do anything manually. 😃 All packages will be installed and setup automatically. Something failed regarding the provisioning and we have to find out what happened. |
@fhemberger all the missing components are installed under /opt/graylog2. There is no need to install anything manually. However for some reasons your graylog2-server didn't startup correctly on the first try. Could you send us the output of the |
My bad … destroyed the vm, did a fresh I compared the outputs of both |
Hi, I had the same issues on my Mac OS X and after a fourth try I got an instance running (including access to the management site). I had some feeling of hungs with 100% at 170MB RAM usage of the VM. So it seems to be a race condition. |
I tried to install graylog2 via vagrant on my development machine to give it a first try. After starting/provisioning the machine with
vagrant up
for the first time and logging into the web interface, I was greeted with the message "No Graylog2 servers available. Cannot log in." So I fired upvagrant ssh
to have a look at the problem.First of all, java doesn't seem to get installed so I had to run
sudo apt-get update && sudo apt-get install openjdk-7-jre
manually.Then I tried to start the server manually with
sudo -u graylog2 java -jar graylog2-server.jar --debug
according to the docs, but the config file/etc/graylog2.conf
was missing, so I copied the example file and tried to start the server again.Settings for
password_secret
androot_password_sha2
(the pwgen-package is missing as well)Yay, finally some more output when starting the server (unfortunately a stack trace as well). Missing steps again:
Oh, just discovered mongodb is missing as well … installing that, too (but don't do further setup).
Ok, starting again. Still doesn't work:
ERROR: Could not successfully connect to Elasticsearch.
I'm giving up at this point!
It would be great to have all those steps added to the Vagrantfile (e.g. with a default 'admin' password hash as well for
root_password_sha2
). Usually, I expect all those things to happen automatically when I'm setting up a dev environment, so I can start testing/developing. Having to go through all those manual steps and finding out what exactly causes those errors is really cumbersome and demotivating.The text was updated successfully, but these errors were encountered: