I downloaded and installed the OVA, all worked fine. I then updated to the latest version and still all good. Somewhere along the steps of following http://docs.graylog.org/en/2.3/pages/installation/virtual_machine_appliances.html?highlight=ova and hardening the appliance I ran into the issue that graylog seemed not to be starting anymore.
so I tried: graylog-ctl reconfigure-as-backend which resulte in these 2 lines in my /opt/graylog/conf/graylog.conf
rest_listen_uri = h**p://0.0.0.0:9000/api web_listen_uri = 192.168.99.2
as I had also run graylog-ctl local-connect before
with the above configuration inside /var/log/graylog/server/current I see
ERROR Invalid Configuration Parameter web_listen_uri should be an absolute URI (found 192.168.99.2)
so I went and changed it to:
web_listen_uri = h**p://192.168.99.2/
which still doesn’t give any positive results. graylog-ctl status shows elasticsearch, etcd, graylog-server and mongodb running which indicates nginx is somehow down.
graylog-ctl tail nginx shows this:
while 192.168.99.2 is graylog’s IP and 192.168.99.0 is its gateway and 192.168.0.2 was the client I was connecting from.
Most important question: is there a command to reset an OVA to its default config?
I’ve read through here but not sure what would fit this scenario: h**p://docs.graylog.org/en/2.3/pages/configuration/graylog_ctl.html
- Graylog Version: latest version after updating the OVA via apt-get
- Elasticsearch Version: latest version after updating the OVA via apt-get
- MongoDB Version: latest version after updating the OVA via apt-get
P.S. yes I know that the OVA is not recommend for production so I have read h**p://docs.graylog.org/en/2.3/pages/securing.html#securing-graylog and acted accordingly. Also, this OVA is separated via firewall rules so only the necessary ports are accessible from any other machines.
P.P.S. Since I am a new user I am only allowed 2 external links so I replaced a few http occurances with h**p