# TCP connection failure to ELK stack

**URL:** <https://discuss.elastic.co/t/tcp-connection-failure-to-elk-stack/123189>\
**Category:** Logstash\
**Created:** [March 9, 2018, 5:14am UTC](https://discuss.elastic.co/t/tcp-connection-failure-to-elk-stack/123189 "2018-03-09T05:14:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![csudaya](https://avatars.discourse-cdn.com/v4/letter/c/838e76/32.png) [@csudaya](https://discuss.elastic.co/u/csudaya)\
**Post date:** [March 9, 2018, 5:14am UTC](https://discuss.elastic.co/t/tcp-connection-failure-to-elk-stack/123189/1 "2018-03-09T05:14:11Z")

</div>

I have setup the elk stack based on [https://github.com/cisco/bigmuddy-network-telemetry-stacks](https://github.com/cisco/bigmuddy-network-telemetry-stacks).

I have build and run the stack successfully.

## cisco@ubuntu:~/bigmuddy-network-telemetry-stacks/stack\_elk$ sudo ./stack\_run

%%% Running stack\_run on stack\_elk - Fri Mar 9 00:04:34 IST 2018 %%%

Please 'tail -f log/stack\_run.log' to watch the action in detail

* * *

## %%-script:./stack\_run:LOG: Collector for stack\_elk at 10.126.168.120 %%-script:./stack\_run:LOG: Run stack containers %%-script:./stack\_run:LOG: Executing: docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 616d27ef2c90 logstash:2.3.1 "/docker-entrypoin..." 5 seconds ago Up Less than a second stack\_elk\_logstash 17c95de1eb94 kibana:4.5.0 "/bin/sh -c '/star..." 9 seconds ago Up 5 seconds 0.0.0.0:5601-\>5601/tcp stack\_elk\_kibana 38851f1e7d72 elasticsearch:2.3.1 "/docker-entrypoin..." 11 seconds ago Up 9 seconds stack\_elk\_elasticsearch

%%% Ran stack\_run on stack\_elk successfully - Fri Mar 9 00:04:45 IST 2018 %%%

* * *

Telemetry streams can be pointed at collector, and data viewed in kibana:

Collector @ 10.126.168.120  
Streams @ UDP/2103 supporting gprotobuf or JSON  
Streams @ TCP/2103 supporting JSON, GPB and self-describing GPB, compressed or not  
Kibana @ [http://10.126.168.120:5601](http://10.126.168.120:5601)

Note: if host has multiple addresses, use an address which is reachable from source (router or browser as the case may be).

* * *

However , when the telemetry data is streamed from the device , I do not see any data. Debugging on the device ,show TCP connection failure to elk stack.

I do not see any logstash.log file generated to get an idea on what is happening

can anybody help me on this ?

Thanks  
udaya

---

<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:** [April 6, 2018, 5:14am UTC](https://discuss.elastic.co/t/tcp-connection-failure-to-elk-stack/123189/2 "2018-04-06T05:14:12Z")

</div>

Closed on April 6, 2018, 5:14am UTC

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