# \_cat/indices?v - no winlogbeat **URL:** \ **Category:** Elasticsearch\ **Created:** [August 10, 2019, 9:58am UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701 "2019-08-10T09:58:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![james\_007](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@james\_007](https://discuss.elastic.co/u/james_007)\ **Post date:** [August 10, 2019, 9:58am UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701/1 "2019-08-10T09:58:07Z")
Hi All. first time with this ELK system, running WS2016, i have installed Kibana, logstash and winlogbeat, all version 7.3 all of the services are up and working. \_cat/indices?v health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .kibana\_task\_manager CCedQtRoQ4mHI5MqR2ifeg 1 0 2 0 45.6kb 45.6kb green open .kibana\_1 UkqPQYgXT2-t\_8STZfhu8g 1 0 4 1 24.6kb 24.6kb I guess because i can't see my winlogbeat - this is why it is not passing any data, any help will be much appreciated. thanks I haved looked at the winlogbeat log and i am getting this error. Failed to connect to backoff(async(tcp://10.101.10.10:5044)): dial tcp 10.101.10.10:5044: connectex: No connection could be made because the target machine actively refused it. 2019-08-10T14:19:26.785+0100 INFO pipeline/output.go:93 Attempting to reconnect to backoff(async(tcp://10.200.198.67:5044)) with 46 reconnect attempt(s) it looks like port 5044 is not open, netstat -a Any ideas ? ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 12, 2019, 8:03am UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701/2 "2019-08-12T08:03:18Z")
Hey, can you share the output configuration to winlogbeat? You are writing to logstash it seems. How is logstash configured? Are you seeing any data on the logstash side of things? It seems, as if logstash is not properly set up or not running on that port, from what I interpret out of that single log line. --Alex ---
**Author:** ![james\_007](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@james\_007](https://discuss.elastic.co/u/james_007)\ **Post date:** [August 13, 2019, 2:57pm UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701/3 "2019-08-13T14:57:33Z")
Hey Alex - thanks for the reply I am using Ws2016 and did not have the correct version of java installed, had version 8, once i upgraded to 11.04 port 5044 opened on the logstash and i am now getting logs, - on a separate discussion, it does look to me that ELK services runs better on linux than windows - your thoughts ? cheers ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 14, 2019, 7:12am UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701/4 "2019-08-14T07:12:00Z")
Hey, glad you got it working. Pretty much all parts of the stack are tested under windows as well. However from my personal experience (and thus total biased) I would say there are far more people running the stack under linux, which just makes it easier for many to debug issues who do not feel home with windows based systems, like myself. --Alex ---
**Author:** ![james\_007](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@james\_007](https://discuss.elastic.co/u/james_007)\ **Post date:** [August 19, 2019, 6:46am UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701/5 "2019-08-19T06:46:39Z")
Alex - noted: i shall deploy an Linux version ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 16, 2019, 6:46am UTC](https://discuss.elastic.co/t/cat-indices-v-no-winlogbeat/194701/6 "2019-09-16T06:46:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.