# Problem with Filebeat and Kibana

**URL:** https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806
**Category:** Beats
**Tags:** filebeat
**Created:** [October 9, 2019, 9:46am UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806 "2019-10-09T09:46:37Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Jonathan\_Sieger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_sieger/32/48640_2.png) [@Jonathan\_Sieger](https://discuss.elastic.co/u/Jonathan_Sieger)
#### Post date: [October 9, 2019, 9:46am UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/1 "2019-10-09T09:46:37Z")

</div>

Hi,

I use Filebeat 7.4 and Kibana 7.3.2 . Filebeat receive cleanly the log. But he don't forwad to Kibana.  
When I do : `filebeat setup`  
I have this result :

```
Index setup finished.
 Loading dashboards (Kibana must be running and reachable)
 Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://172.17.2.9:5601/api/status fails: fail to execute the HTTP GET request: Get http://172.17.2.9:5601/api/status: dial tcp 172.17.2.9:5601: connect: connection refused. Response: .

```

Can you help me please ?  
Best regards,

---

<div class="post-metadata">

### Author: ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)
#### Post date: [October 9, 2019, 10:34am UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/2 "2019-10-09T10:34:10Z")

</div>

hey @Jonathan_Sieger

do you see anything in Kibana logs? can you connect to Kibana from where Beat is running? can you verify that Kibana is in fact listening on specified port on that URL?

---

<div class="post-metadata">

### Author: ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)
#### Post date: [October 9, 2019, 12:17pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/4 "2019-10-09T12:17:27Z")

</div>

> [@Jonathan\_Sieger](#):
>
> @Jonathan_Sieger,
> 
> Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to [http://172.17.2.9:5601/api/status](http://172.17.2.9:5601/api/status) fails: fail to execute the HTTP GET request: Get [http://172.17.2.9:5601/api/status:](http://172.17.2.9:5601/api/status:) dial tcp 172.17.2.9:5601: connect: connection refused. Response: .

As per above error it is clear that your kibana server is not reachable from that machine where you installed filebeat and trying to rin `filebeat setup`.

Can you please try below command on machine where you run `filebeat setup`:

```auto
telnet 172.17.2.9 5601

```

If you are not able to telnet then check your firewall rule and kibana service.

Thanks.

---

<div class="post-metadata">

### Author: ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)
#### Post date: [October 9, 2019, 12:21pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/5 "2019-10-09T12:21:02Z")

</div>

@Jonathan_Sieger,

> [@Jonathan\_Sieger](#):
>
> netstat -paunt | grep 5601 tcp 0 0 127.0.0.1:5601 0.0.0.0:\* LISTEN 29963/node

According to this output your kibana is running on localhost. You need to run it over internal IP (private ip) then it will be reachable from beat machine. If both machine are not reachable then contact your system admin team they will help you in reach ability of both machine.

Thanks.

---

<div class="post-metadata">

### Author: ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)
#### Post date: [October 9, 2019, 12:33pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/7 "2019-10-09T12:33:30Z")

</div>

@Jonathan_Sieger,

> [@Jonathan\_Sieger](#):
>
> telnet: `connect to address `172.17.2.9`: Connection refused`

Run your kibana over `172.17.2.9` or change in your `filebeat.yml` configuration replace kibana IP 172.17.2.9 with `127.0.0.1`.

Thanks.

---

<div class="post-metadata">

### Author: ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)
#### Post date: [October 9, 2019, 12:43pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/9 "2019-10-09T12:43:11Z")

</div>

@Jonathan_Sieger,

Can you please check filebeat service is running properly or not? If no can you please provide some error logs from filebeat?

Also please provide your `filebeat.yml` config.

Thanks.

---

<div class="post-metadata">

### Author: ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)
#### Post date: [October 9, 2019, 12:51pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/11 "2019-10-09T12:51:19Z")

</div>

@Jonathan_Sieger ,

> [@Jonathan\_Sieger](#):
>
> setup.kibana.host: "[http://127.0.0.1](http://127.0.0.1)" setup.kibana.protocol: "http" setup.dashboard.enabled: true

In above part `port` is missing.

```auto
setup.kibana:
  host: "127.0.0.1:5601"

```

Thanks.

---

<div class="post-metadata">

### Author: ![Jonathan\_Sieger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_sieger/32/48640_2.png) [@Jonathan\_Sieger](https://discuss.elastic.co/u/Jonathan_Sieger)
#### Post date: [October 9, 2019, 1:03pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/12 "2019-10-09T13:03:46Z")

</div>

Nothing have changed

```
systemctl status filebeat.service : 
oct. 09 15:06:12 filebeat[4148]: 2019-10-09T15:06:12.055+0200 WARN elasticsearch/client.go:535 Cannot index event publisher.Event{Content:beat.Event{Timestamp:time.Time{wall:0xbf5f...
oct. 09 15:06:18 filebeat[4148]: 2019-10-09T15:06:18.973+0200 WARN elasticsearch/client.go:535 Cannot index event publisher.Event{Content:beat.Event{Timestamp:time.Time{wall:0xbf5f...
```

---

<div class="post-metadata">

### Author: ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)
#### Post date: [October 10, 2019, 3:21am UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/13 "2019-10-10T03:21:13Z")

</div>

@Jonathan_Sieger, did you restart the filebeat service after making changes in `filebeat.yml` file?  
If yes, please provide log from filebeat because service status is not enough to troubleshoot the issue log may give some lead.

Thanks.

---

<div class="post-metadata">

### Author: ![Jonathan\_Sieger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_sieger/32/48640_2.png) [@Jonathan\_Sieger](https://discuss.elastic.co/u/Jonathan_Sieger)
#### Post date: [October 15, 2019, 11:41am UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/14 "2019-10-15T11:41:06Z")

</div>

Hi,

I resolve my issue, the filebeat.yml was not properly configured with my last version of elasticsearch and my app Wazuh in Kibana. Thanks you for your help.

But after the upgrade, Elasticsearch and Kibana use the CPU at 122%.. I have 8 Go RAM and 2 vCPU. I add more CPU ?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 12, 2019, 11:41am UTC](https://discuss.elastic.co/t/problem-with-filebeat-and-kibana/202806/15 "2019-11-12T11:41:09Z")

</div>

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