# Logs from linux machine is unreadable

**URL:** https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722
**Category:** Logstash
**Created:** [July 29, 2016, 11:21am UTC](https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722 "2016-07-29T11:21:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)
#### Post date: [July 29, 2016, 11:21am UTC](https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722/1 "2016-07-29T11:21:05Z")

</div>

I have logserver running on ubuntu 14.04. ELK versions are 2 or above(kibana 4.4.x).  
I am also using nagios to monitor systems and applications. Now I need to sent error messages from nagios to logserver.  
Nagios is installed on centos . Nagios error messages are writing into /usr/local/nagios/var/archives/ . I am planning to sent this error logs to logserver. (Using a shell script I keep only one log file in that folder . Errors will write into that log file)

For that, I installed filebeat on centos.

Logstash configuration :

```
input{
     tcp{
         port => 5550
         type => "nagios"
         codec => json {
          charset => "UTF-8"
            }
      }
}

output {
 if [type] == "nagios" {
    elasticsearch {
        hosts => ["ipaddress:9200"]
        }
     }
 }

```

Now my problem is there is no readable information in logs getting in kibana .  
Below is an example. I am getting only this type of logs.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/4/403226e6b6f9abc666eece5beec9eaf66d82b53e.JPG)

How to get the actual error information in kibana. ??

---

<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: [July 29, 2016, 11:45am UTC](https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722/2 "2016-07-29T11:45:20Z")

</div>

So it's Filebeat that sends to port 5550? Use a beats input, not a tcp input.

---

<div class="post-metadata">

### Author: ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)
#### Post date: [July 29, 2016, 11:52am UTC](https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722/3 "2016-07-29T11:52:55Z")

</div>

No logs are getting with beats input plugin

---

<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: [July 29, 2016, 12:01pm UTC](https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722/4 "2016-07-29T12:01:38Z")

</div>

But that's not what the configuration snippet you posted shows.

---

<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 6, 2017, 4:45am UTC](https://discuss.elastic.co/t/logs-from-linux-machine-is-unreadable/56722/5 "2017-07-06T04:45:56Z")

</div>