I am following the setup guide from elastic for metric beat, and get the following when I run " metricbeat setup -e"
019-08-23T20:48:31.017Z INFO kibana/client.go:117 Kibana url: http://localhost:5601
2019-08-23T20:48:31.018Z ERROR instance/beat.go:877 Exiting: error connecting to
Kibana: fail to get the Kibana version: HTTP GET request to http://localhost:5601/api/status fails:
fail to execute the HTTP GET request: Get http://localhost:5601/api/status: dial tcp
127.0.0.1:5601: connect: connection refused. Response: .
Any assistance would be appreciated.
Is kibana running at
Kibana is set to:
If I set it to anything else, kibana won't start. I have the metricbeat.yml file set to point to:
I am unclear if elasticsearch kibana and metricbeat are all running on the same host or all different hosts.
In the metribeat.yml you still have to also set the kibana hosts if they are running on different hosts.
If they are all 3 on the same host and you didn't change any other settings you don't need to edit any of the ymls to make them run.
They are all running on the same host. And yes, I had to edit the files to get it running, Elastic and Kibana bith crash if I don't specifically set the IP. Also, kibana is not reachable from other hosts if I leave network.host: set to localhost.
Kibana is set to:
That is unusual why localhost does not work what OS are you on
Ubuntu server virtual machine on VMware.
The metricbeat.yml file shows:
Is that what should be set or should it be what you show above?
If you are using version 7.3.0
#============================== Kibana =====================================
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
# Kibana Host
# Scheme and port can be left out and will be set to the default (http and 5601)
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
#================================ Outputs =====================================
# Configure what output to use when sending the data collected by the beat.
#-------------------------- Elasticsearch output ------------------------------
# Array of hosts to connect to.
# Optional protocol and basic auth credentials.
If it does not look like that ... may I ask what version of metricbeat are you using?
What happens when you point a browser to
Looks like it is working now. It appears to have been an error with the host variable.
Thanks for your help!
if you run
$ cat /etc/hosts
You should see something like this. I suspect your localhost line is commented out or does not exist, if you uncomment it then the
localhost settings would probably work.
# Host Database
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
It's not commented out.
root@elk:/etc/logstash# cat /etc/hosts
127.0.0.1 elk elk
192.168.2.39 elk elk
192.168.2.39 elk-server elk-server
The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
Huh odd not sure what to tell you...
$ ping localhost and get a positive response.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.