# Problems with ELK install

**URL:** <https://discuss.elastic.co/t/problems-with-elk-install/120723>\
**Category:** Elasticsearch\
**Created:** [February 20, 2018, 8:37pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723 "2018-02-20T20:37:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![rnvntr.h](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rnvntr.h](https://discuss.elastic.co/u/rnvntr.h)\
**Post date:** [February 20, 2018, 8:37pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/1 "2018-02-20T20:37:17Z")

</div>

Hello! I'm running Kibana 6.2.1 on a Centos 7 server. I'm able to receive logs from this same server but not from my other servers, can you guys tell me what i'm missing? I'm sharing my config files and logs. Thanks in advance!

![image](https://us1.discourse-cdn.com/elastic/original/3X/f/4/f4a405c890601213a9978f560c668996ebf9a556.png)

## /etc/nginx/conf.d/kibana.conf

```
server {
        listen 80 default_server; # Listen on port 80
        server_name myaddress.com;
        auth_basic "Restricted Access";
        auth_basic_user_file /etc/nginx/.kibana-user;

        location / {
        proxy_pass http://localhost:5601;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        }
}

```

## /etc/logstash/conf.d/syslog-filter.conf

```
filter {
  if [type] == "syslog" {
    grok {
      match => { "message" => "%{SYSLOGTIMESTAMP:syslog_timestamp} %{SYSLOGHOST:syslog_hostname} %{DATA:syslog_program}(?:\[%{POSINT:syslog_pid}\])?: %{GREEDYDATA:syslog_message}" }
      add_field => ["received_at", "%{@timestamp}"]
      add_field => ["received_from", "%{host}"]
    }
    date {
      match => ["syslog_timestamp", "MMM d HH:mm:ss", "MMM dd HH:mm:ss"]
    }
  }
}

```

## /etc/logstash/conf.d/logstash.conf

```
input {
  beats {
    port => 5044
  }
}

output {
  elasticsearch {
    hosts => "localhost:9200"
    manage_template => false
    index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
    document_type => "%{[@metadata][type]}"
  }
}

```

## /etc/kibana/kibana.yml

```
# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5601
server.host: "localhost"
# The URL of the Elasticsearch instance to use for all your queries.
elasticsearch.url: "http://localhost:9200"

```

## /etc/filebeat/filebeat.yml

```
#=========================== Filebeat prospectors =============================

filebeat.prospectors:

# Each - is a prospector. Most options can be set at the prospector level, so
# you can use different prospectors for various configurations.
# Below are the prospector specific configurations.

- type: log

  # Change to true to enable this prospector configuration.
  enabled: false

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    #- c:\programdata\elasticsearch\logs\*

#============================= Filebeat modules ===============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

#==================== Elasticsearch template setting ==========================

setup.template.settings:
  index.number_of_shards: 3
  #index.codec: best_compression
  #_source.enabled: false

setup.kibana:
output.logstash:
  # The Logstash hosts
  hosts: ["myaddress.com:5044"]

```

Now I started receiving this (/var/log/filebeat/filebeat) from kibana server

```
2018-02-20T15:43:00.563-0500 INFO [monitoring] log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":340,"time":344},"total":{"ticks":1920,"time":1933,"value":1920},"user":{"ticks":1580,"time":1589}},"info":{"ephemeral_id":"30bb4383-57cc-4745-8b86-94e35cd27edd","uptime":{"ms":1530078}},"memstats":{"gc_next":8298816,"memory_alloc":4318224,"memory_total":267606536}},"filebeat":{"harvester":{"open_files":1,"running":1}},"libbeat":{"config":{"module":{"running":1}},"output":{"events":{"batches":4,"failed":23,"total":23},"read":{"errors":1},"write":{"bytes":2919}},"pipeline":{"clients":4,"events":{"active":30,"retry":24}}},"registrar":{"states":{"current":4}},"system":{"load":{"1":1.5,"15":0.93,"5":1.18,"norm":{"1":0.1875,"15":0.1163,"5":0.1475}}}}}}
2018-02-20T15:43:05.306-0500 ERROR logstash/async.go:235 Failed to publish events caused by: read tcp 192.168.82.98:53384->192.168.82.98:5044: i/o timeout
2018-02-20T15:43:05.306-0500 ERROR logstash/async.go:235 Failed to publish events caused by: read tcp 192.168.82.98:53384->192.168.82.98:5044: i/o timeout
2018-02-20T15:43:05.306-0500 ERROR logstash/async.go:235 Failed to publish events caused by: read tcp 192.168.82.98:53384->192.168.82.98:5044: i/o timeout

```

/var/log/filebeat/filebeat (from server 1)

```
2018-02-20T15:44:48.880-0500 INFO [monitoring] log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":250,"time":259},"total":{"ticks":480,"time":495,"value":480},"user":{"ticks":230,"time":236}},"info":{"ephemeral_id":"7e165afa-baa3-437e-8243-e6ecb783aee3","uptime":{"ms":2340019}},"memstats":{"gc_next":4194304,"memory_alloc":1370248,"memory_total":17396488}},"filebeat":{"harvester":{"open_files":0,"running":0}},"libbeat":{"config":{"module":{"running":0}},"pipeline":{"clients":0,"events":{"active":0}}},"registrar":{"states":{"current":0}},"system":{"load":{"1":0.25,"15":0.49,"5":0.39,"norm":{"1":0.0156,"15":0.0306,"5":0.0244}}}}}}
2018-02-20T15:45:18.880-0500 INFO [monitoring] log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":260,"time":262},"total":{"ticks":490,"time":499,"value":490},"user":{"ticks":230,"time":237}},"info":{"ephemeral_id":"7e165afa-baa3-437e-8243-e6ecb783aee3","uptime":{"ms":2370018}},"memstats":{"gc_next":4194304,"memory_alloc":1573136,"memory_total":17599376}},"filebeat":{"harvester":{"open_files":0,"running":0}},"libbeat":{"config":{"module":{"running":0}},"pipeline":{"clients":0,"events":{"active":0}}},"registrar":{"states":{"current":0}},"system":{"load":{"1":0.37,"15":0.49,"5":0.4,"norm":{"1":0.0231,"15":0.0306,"5":0.025}}}}}}
2018-02-20T15:45:48.880-0500 INFO [monitoring] log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":260,"time":265},"total":{"ticks":490,"time":503,"value":490},"user":{"ticks":230,"time":238}},"info":{"ephemeral_id":"7e165afa-baa3-437e-8243-e6ecb783aee3","uptime":{"ms":2400018}},"memstats":{"gc_next":4194304,"memory_alloc":1761024,"memory_total":17787264}},"filebeat":{"harvester":{"open_files":0,"running":0}},"libbeat":{"config":{"module":{"running":0}},"pipeline":{"clients":0,"events":{"active":0}}},"registrar":{"states":{"current":0}},"system":{"load":{"1":1.02,"15":0.54,"5":0.55,"norm":{"1":0.0638,"15":0.0338,"5":0.0344}}}}}}
```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 20, 2018, 11:28pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/2 "2018-02-20T23:28:00Z")

</div>

Can you telnet between a host that runs Filebeat to the host that runs Logstash? If not it could be a firewall or other networking problem.

---

<div class="post-metadata">

**Author:** ![rnvntr.h](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rnvntr.h](https://discuss.elastic.co/u/rnvntr.h)\
**Post date:** [February 20, 2018, 11:46pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/3 "2018-02-20T23:46:10Z")

</div>

@warkolm Thank you for replying, I've already tried that, telnet is working...

```
[xxx@xxxxxxx] ➤ telnet 192.168.82.98 5044
Trying 192.168.82.98...
Connected to 192.168.82.98.
Escape character is '^]'.
Connection closed by foreign host.

[root@myaddress ~]# netstat -plntu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1634/mysqld
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1596/nginx: master
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1168/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1703/master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1596/nginx: master
tcp 0 0 127.0.0.1:5601 0.0.0.0:* LISTEN 754/node
tcp6 129 0 :::5044 :::* LISTEN 745/java
tcp6 0 0 :::22 :::* LISTEN 1168/sshd
tcp6 0 0 ::1:25 :::* LISTEN 1703/master
tcp6 0 0 127.0.0.1:9600 :::* LISTEN 745/java
udp 0 0 127.0.0.1:323 0.0.0.0:* 788/chronyd
udp6 0 0 ::1:323 :::* 788/chronyd
```

---

<div class="post-metadata">

**Author:** ![rnvntr.h](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rnvntr.h](https://discuss.elastic.co/u/rnvntr.h)\
**Post date:** [February 20, 2018, 11:49pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/4 "2018-02-20T23:49:19Z")

</div>

btw now the system is in "Breakdown", no changes from my side.

![image](https://us1.discourse-cdn.com/elastic/original/3X/6/d/6d5b4d451424b52f6feb71ee37e41f13218391ad.png)

---

<div class="post-metadata">

**Author:** ![rnvntr.h](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rnvntr.h](https://discuss.elastic.co/u/rnvntr.h)\
**Post date:** [February 21, 2018, 12:55am UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/5 "2018-02-21T00:55:18Z")

</div>

I'm talking to myself here 😂 So I had the elasticsearch service restarted and that fixed the issue above. Will monitor this and make sure it doesn't happen again.  
So I'm back to my main issue, only localhost is able to send logs.

---

<div class="post-metadata">

**Author:** ![harshbajaj16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshbajaj16/32/44970_2.png) [@harshbajaj16](https://discuss.elastic.co/u/harshbajaj16)\
**Post date:** [February 21, 2018, 3:58am UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/6 "2018-02-21T03:58:47Z")

</div>

> [@rnvntr.h](#):
>
> :::5044

Earlier i was getting the same issue at my end and i just enabled the TCP/UDP port on servers and restart the all services after that everything was running fine.

please try.

---

<div class="post-metadata">

**Author:** ![rnvntr.h](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rnvntr.h](https://discuss.elastic.co/u/rnvntr.h)\
**Post date:** [February 21, 2018, 2:46pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/7 "2018-02-21T14:46:17Z")

</div>

@harshbajaj16 Im running with no firewall (firewalld is stopped)

---

<div class="post-metadata">

**Author:** ![rnvntr.h](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rnvntr.h](https://discuss.elastic.co/u/rnvntr.h)\
**Post date:** [February 21, 2018, 7:50pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/8 "2018-02-21T19:50:37Z")

</div>

Doesn't this means that the server is getting the messages from the other devices?

```
[root@myaddress ~]# curl -X GET http://localhost:9200/_cat/indices | grep 2018
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 18909 100 18909 0 0 7440 0 0:00:02 0:00:02 --:--:-- 7441
yellow open filebeat-2018.02.21 zKtAOlB6TTGuDtVdHoq8XQ 5 1 123815 0 61.8mb 61.8mb
yellow open filebeat-2018.02.20 U9TXofcjTcSX3oY7fOBK0Q 5 1 22105 0 7.6mb 7.6mb
yellow open winlogbeat-2018.02.13 Df6kNpGpTgGr0lGp_uwjyg 5 1 38 0 141.6kb 141.6kb
yellow open winlogbeat-2018.02.01 tywWAi10QYGNfp9uNkFKRw 5 1 0 0 1.2kb 1.2kb
yellow open winlogbeat-2018.02.19 BbXl7SCHTWaReH20v1W6yA 5 1 8 0 57.7kb 57.7kb
yellow open winlogbeat-2018.01.19 YYscsxzYRt-M9nbTVQMF5g 5 1 6 0 67.5kb 67.5kb
yellow open winlogbeat-2018.02.18 lmcMvCnWQQa0yuuFhXkltQ 5 1 23 0 224.6kb 224.6kb
yellow open winlogbeat-2018.02.17 cZzEi_pUQOGKaeVQk_B8kA 5 1 40 0 210.3kb 210.3kb
yellow open winlogbeat-2018.02.09 nHEsvyOqQ56ucvJiP5XcyA 5 1 2 0 35.2kb 35.2kb
yellow open filebeat-2018.02.19 vJV2hrhRTqCnstwK7vf47Q 5 1 67534 0 17.9mb 17.9mb
yellow open filebeat-6.2.1-2018.02.16 qt33CY3DQnqptvEnxKrpnw 3 1 10472 0 3.6mb 3.6mb
       close .watcher-history-7-2018.02.16 gcQiEJhgTAexv_HtW8nk0w
green open .monitoring-es-6-2018.02.16 22gTHSb4QKOGSuXLqZCwOg 1 0 1264 65 727.7kb 727.7kb
yellow open winlogbeat-2018.02.14 sa_GrPaTSIKW_PqRUkUunQ 5 1 0 0 1.2kb 1.2kb
yellow open winlogbeat-2018.01.29 HUyMdfjESD2EUkL_oPlZKg 5 1 1 0 31.2kb 31.2kb
yellow open winlogbeat-2018.02.16 akwnjnvXRKKwAHCM0-p4cA 5 1 4 0 42.1kb 42.1kb

```

I'm pointing one Windows Server 2012 and one other Centos 7 server. (Plus the Kibana server itself) But im only seeing the kibana server under Discover.

---

<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:** [March 21, 2018, 7:50pm UTC](https://discuss.elastic.co/t/problems-with-elk-install/120723/9 "2018-03-21T19:50:39Z")

</div>

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