# Issues with Topbeat --\> ES since version 1.0.0-rc1

**URL:** <https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928>\
**Category:** Beats\
**Created:** [November 18, 2015, 11:24am UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928 "2015-11-18T11:24:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![wabit](https://avatars.discourse-cdn.com/v4/letter/w/a6a055/32.png) [@wabit](https://discuss.elastic.co/u/wabit)\
**Post date:** [November 18, 2015, 11:24am UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928/1 "2015-11-18T11:24:32Z")

</div>

Title says it all really,

I am unable to get any metrics to be sent to Elastic search since upgrading topbeat to version 1.0.0-rc1 on Centos 6.

I cant see anything in system logs and everything starts up without any issues.

can you recommend where to look to see where it is failing?

Thanks.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [November 18, 2015, 11:43am UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928/2 "2015-11-18T11:43:35Z")

</div>

Can start up topbeat with -e -d "\*" flag. Thiw will output the debug messages. There you should find some more information and you can also post it here for further analysis.

---

<div class="post-metadata">

**Author:** ![wabit](https://avatars.discourse-cdn.com/v4/letter/w/a6a055/32.png) [@wabit](https://discuss.elastic.co/u/wabit)\
**Post date:** [November 18, 2015, 11:59am UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928/3 "2015-11-18T11:59:21Z")

</div>

Thanks for the advice but this hasnt really pointed to anything new

```
[root@##### ~]# topbeat --version
topbeat version 1.0.0-rc1 (amd64)
[root@##### ~]# topbeat -e -d "*"
2015/11/18 11:56:05.588635 beat.go:94: DBG Initializing output plugins
2015/11/18 11:56:05.588664 geolite.go:52: WARN Couldn't load GeoIP database

```

I do find that it is trying to load the GeoIP database as the release notes say it was disabled by default.

Disable geoip by default. To enable it uncomment in config file. #305

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [November 18, 2015, 12:38pm UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928/4 "2015-11-18T12:38:15Z")

</div>

The GeoIP is made default false in RC2, and you have RC1. Just to make sure, by default topbeat reads the stats every 10 seconds, did you waited that long while running it in foreground?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [November 18, 2015, 1:55pm UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928/5 "2015-11-18T13:55:44Z")

</div>

since rc1, the outputer will probe for elasticsearch to be available. For probing a HTTP HEAD message is used (similar to GET, but response as no message body). You running ES behind a proxy/firewall?

Can you try [http://es-hostname](http://es-hostname):es-port from any browser? You see some JSON output?

Also with curl you can try elasticsearch probing via:

```
curl -XHEAD http://es-hostname:es-port
```

---

<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:** [July 5, 2017, 9:58pm UTC](https://discuss.elastic.co/t/issues-with-topbeat-es-since-version-1-0-0-rc1/34928/6 "2017-07-05T21:58:06Z")

</div>