# TOPBEAT \> WINDOWS : Topbeat starting but showing error in log

**URL:** <https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428>\
**Category:** Beats\
**Created:** [March 15, 2016, 1:06pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428 "2016-03-15T13:06:53Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 15, 2016, 1:06pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/1 "2016-03-15T13:06:53Z")

</div>

Hi, I am using Topbeat for monitoring. I've downloaded and followed process as per instructions.  
I am using WINDOWS and I want to post my logs to a the computer in my network(10.77.240116)

After running topbeat powershell as a service, it runs with no successful message. I saw following message in C:/ProgramData/topbeat/Logs as,

**2016-03-15T18:01:14+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid**

Any probable reason?

NOTE: We are inside firewall of company. Ping from my machine to above IP is successful.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 15, 2016, 1:14pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/2 "2016-03-15T13:14:27Z")

</div>

If you post your configuration **formatted as code** it might be easier to help.

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 15, 2016, 1:24pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/3 "2016-03-15T13:24:44Z")

</div>

Hi @magnusbaeck

Here is the configuration.

```
input:
  period: 10

  procs: [".*"]

  stats:
    system: true

    proc: true

    filesystem: true

    cpu_per_core: false

output:

  elasticsearch:
    hosts: ["10.77.240.116:9200"]

    index: "krtopbeat"

  console:
    pretty: false

shipper:
logging:

  files:
    rotateeverybytes: 10485760 # = 10MB

```

We are using default configuration, sending you by removing comments.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 15, 2016, 1:30pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/4 "2016-03-15T13:30:14Z")

</div>

I would assume it's the console output that's causing this. Not sure why Topbeat attempts to open /dev/stdout on Windows (or the error message is bad).

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 15, 2016, 1:31pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/5 "2016-03-15T13:31:52Z")

</div>

Actually we ain't even seeing any message on console, so I enable it. Shall I try without console as output.?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 15, 2016, 1:35pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/6 "2016-03-15T13:35:35Z")

</div>

When debugging why something doesn't work it's _always_ a good idea to disable features to see what might be behind the problems.

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 15, 2016, 1:38pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/7 "2016-03-15T13:38:42Z")

</div>

True. Any reason why it is happening? or Solution?

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 16, 2016, 5:38am UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/8 "2016-03-16T05:38:37Z")

</div>

Hi @magnusbaeck,  
**What do you mean by " it's the console output that's causing this"?**  
Are you pointing to,

```
console:
    pretty: false

```

?

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 16, 2016, 6:23am UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/9 "2016-03-16T06:23:43Z")

</div>

Yeah @magnusbaeck,

You are right. The **"error message is bad"** I tried with localhost by putting loggin level **info** , worked.

Logfile says,

```
2016-03-16T11:48:47+05:30 INFO GeoIP disabled: No paths were set under output.geoip.paths
2016-03-16T11:48:47+05:30 INFO Activated console as output plugin.
2016-03-16T11:48:47+05:30 INFO Activated elasticsearch as output plugin.
2016-03-16T11:48:47+05:30 INFO Publisher name: DIN16000704
2016-03-16T11:48:47+05:30 INFO Flush Interval set to: 1s
2016-03-16T11:48:47+05:30 INFO Max Bulk Size set to: 2048
2016-03-16T11:48:47+05:30 INFO Flush Interval set to: 1s
2016-03-16T11:48:47+05:30 INFO Max Bulk Size set to: 50
2016-03-16T11:48:47+05:30 INFO Init Beat: topbeat; Version: 1.1.1
2016-03-16T11:48:47+05:30 INFO topbeat sucessfully setup. Start running.
2016-03-16T11:48:58+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid.
2016-03-16T11:48:58+05:30 INFO Error bulk publishing events: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:08+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:08+05:30 INFO Error bulk publishing events: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:18+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:18+05:30 INFO Error bulk publishing events: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:28+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:28+05:30 INFO Error bulk publishing events: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:38+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:38+05:30 INFO Error bulk publishing events: write /dev/stdout: The handle is invalid.
2016-03-16T11:49:44+05:30 INFO Cleaning up topbeat before shutting down.

```

**Not getting whats wrong. Any Idea?**

Tried with another computer in network, loglevel = **info**

```
2016-03-16T11:58:25+05:30 INFO Connecting error publishing events (retrying): Head http://10.76.170.79:9200: dial tcp 10.76.170.79:9200: connectex: No connection could be made because the target machine actively refused it.
2016-03-16T11:58:25+05:30 INFO send fail
2016-03-16T11:58:25+05:30 INFO backoff retry: 1s
2016-03-16T11:58:27+05:30 INFO Connecting error publishing events (retrying): Head http://10.76.170.79:9200: dial tcp 10.76.170.79:9200: connectex: No connection could be made because the target machine actively refused it.
2016-03-16T11:58:27+05:30 INFO send fail
2016-03-16T11:58:27+05:30 INFO backoff retry: 2s
2016-03-16T11:58:30+05:30 INFO Connecting error publishing events (retrying): Head http://10.76.170.79:9200: dial tcp 10.76.170.79:9200: connectex: No connection could be made because the target machine actively refused it.
2016-03-16T11:58:30+05:30 INFO send fail
2016-03-16T11:58:30+05:30 INFO backoff retry: 4s
2016-03-16T11:58:35+05:30 ERR Error sending/writing event: write /dev/stdout: The handle is invalid.
```

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 16, 2016, 11:41am UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/10 "2016-03-16T11:41:26Z")

</div>

@magnusbaeck ,Team, is there a way to force or cheat around topbeat to push meaning problem or log.

has any body pushed topbeat to remote elasticsearch with or without proxy?

We can always go around change network policy but we need to know what ??

Regards, Chirag Shah

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 16, 2016, 12:03pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/11 "2016-03-16T12:03:09Z")

</div>

> 2016-03-16T11:58:30+05:30 INFO Connecting error publishing events (retrying): Head [http://10.76.170.79:9200](http://10.76.170.79:9200): dial tcp 10.76.170.79:9200: connectex: No connection could be made because the target machine actively refused it.

"Connection refused" in other words. Is ES listening on 10.76.170.79:9200 in the first place? If yes, is there a firewall blocking the access?

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 16, 2016, 12:05pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/12 "2016-03-16T12:05:23Z")

</div>

@magnusbaeck **Yes, we are inside a firewall. Any proxy settings??**

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [March 17, 2016, 9:36pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/14 "2016-03-17T21:36:52Z")

</div>

> [@krushnat\_khawale](#):
>
> Any proxy settings??

The Elasticsearch output supports using an HTTP proxy. You configure the proxy using the [`proxy_url`](https://www.elastic.co/guide/en/beats/topbeat/current/elasticsearch-output.html#_proxy_url) option.

---

<div class="post-metadata">

**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\
**Post date:** [March 18, 2016, 2:16am UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/15 "2016-03-18T02:16:55Z")

</div>

Hi @andrewkroh, Thanks for you time.

Yeah, I saw that in ES configuration, I'm not a networking guy honestly and I don't have any  
that what should be the value of ' **proxy\_url**'?

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [March 18, 2016, 3:03am UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/16 "2016-03-18T03:03:33Z")

</div>

The value can be `http://host:port` or `http://username:password@host:port` if you need to do basic auth. `host` is the IP address or hostname of your proxy server and `port` is the port number that the proxy server is listening on.

So if I had a squid server on my network at 192.168.1.100 I would write:

```auto
output:
  elasticsearch:
    hosts: ["1.2.3.4:9200"]
    proxy_url: http://192.168.1.100:3128

```

---

<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:54pm UTC](https://discuss.elastic.co/t/topbeat-windows-topbeat-starting-but-showing-error-in-log/44428/17 "2017-07-05T21:54:33Z")

</div>


