Installing ELK on a new Linux box on Azure

Elastic Stack Elasticsearch
1

I am a Linux n00b, sorry, but I am trying :slight_smile:

What do I need to do to access Kibana from the another machine once I deploy to Linux?

Problem:
I just provisioned a new Ubuntu Linux box on Azure and installed Elastic search + Kibana.
I followed the steps here: https://www.elastic.co/start

But used the debian packages, so I started elasticsearch and kibana as services -
There was no message when I launched 'sudo service kibana start' so I assume the service started correctly.

Now the final steps says to open a browser and go http://localhost:5601, but of course I cannot do that on a SSH session, so I tried: http://"my Linux box IP":5601 from my PC, but no luck, the request times out.

The firewall is not active I think, but I also tried to activate it and open port 5601 without luck.

Any hint?

Thx,
Mauro.

2

You need to change server.host - https://www.elastic.co/guide/en/kibana/current/settings.html

3

I set it to 0.0.0.0 and then to the public IP address, but did not work.
The connection timed out.

4

So elasticsearch seems started but I can't tell because of security?

wget localhost:9200

--2017-01-22 02:12:41--  http://localhost:9200/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:9200... connected.
HTTP request sent, awaiting response... 401 Unauthorized

Username/Password Authentication Failed.

This is the kibana.yml:

server.port: 5601
server.host: 40.112.217.143

If I try to launch kibana I get the following:

sudo /usr/share/kibana/bin/kibana

  log   [02:14:10.150] [fatal] Error: listen EADDRNOTAVAIL 40.112.217.143:5601
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at Server._listen2 (net.js:1244:19)
    at listen (net.js:1293:10)
    at net.js:1403:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
FATAL { Error: listen EADDRNOTAVAIL 40.112.217.143:5601
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at Server._listen2 (net.js:1244:19)
    at listen (net.js:1293:10)

If I change the address to 127.0.0.1, then kibana starts and I can access it locally (wget gives me access denied but it connects), but I cannot connect to it remotely.

Which address should I use?

5

Did you install X-Pack?

Is that an IP attached to an interface on the host?

6

I know this doesn't directly answer your question, but did you check out our ARM template for installing Elasticsearch with Kibana on Azure? The template is able to install an Elasticsearch cluster in a number of different topologies, complete with Kibana. Deploying from the command line with the Azure CLI (cross-platform) is as simple as

# login to azure
azure login

# switch CLI to ARM mode
azure config mode arm

# create a resource group
azure group create "<name>" "<location>"

# specify a parameters.json file with the parameters and deploy the cluster using template and parameters
azure group deployment create --template-uri https://raw.githubusercontent.com/elastic/azure-marketplace/master/src/mainTemplate.json --parameters-file parameters/password.parameters.json -g "<name>"

It might save you a lot of time in configuring all of the resources required on Azure yourself (unless of course the aim is to become more acquainted with Azure resources :smile:).

7

I think the problem is that the IP is not addressable, the host only sees 10.0.0.XYZ

I think I need to configure a public IP on the Azure VM, but I am not sure how to do that, I will investigate more.

No, I did not install X-Pack, will do next time, for now reverting to a Windows instance and using it locally remoting into it, I just needed a test instance, thanks.

8

Thanks @forloop, I will give it a try.

9

Awesome! Feel free to open a discuss thread for any questions that you have about the ARM template :thumbsup:

10

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.