search

Zuehlke / cookbook-elk-stack

0 stars 1 forks source link

elasticsearch not accessible #4

Open damphyr opened 8 years ago

damphyr commented 8 years ago

Running on virtualbox. Fixed port forwarding in #3

Kibana runs but elasticsearch and the plugin are not accessible over port 9200.

a-zen commented 8 years ago

Strange it worked for me.

a-zen commented 8 years ago

Ah with virtualbox it worked with 127.0.0.1, but with vmware I need to use the guest internal ip 192.168.153.XX .

a-zen commented 8 years ago

Hm others have this issue too:

http://stackoverflow.com/questions/31167025/vagrant-port-forwarding-not-working-on-windows-8

a-zen commented 8 years ago

Open issue @vagrant

https://github.com/mitchellh/vagrant/issues/5838

damphyr commented 8 years ago

The problem here is that I am running Virtual Box on Mac OS X :) And apparently there is no process running that binds 9200 on the box. I'll try and reproduce again today.

a-zen commented 8 years ago

Strange can you try

service elasticsearch status

and

service elasticsearch restart

tknerr commented 8 years ago

This should be fixed via 804131c853a8e0be1517171726e027a09066b357 in #5

The issue was that both port forwardings have the same id ("elastic"). I renamed the other one to "kibana" and then it worked:

  cfg.vm.network "forwarded_port", guest: 9200, host: 9200, id: "elastic", auto_correct: true
  cfg.vm.network "forwarded_port", guest: 80, host: 8080, id: "kibana", auto_correct: true

(P.S.: I also removed the ssh portforwarding becasue vagrant does that automatically anyway)