# 100% CPU with Logstash 1.5.x

**URL:** <https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864>\
**Category:** Logstash\
**Created:** [August 21, 2015, 9:24pm UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864 "2015-08-21T21:24:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephen\_Meier](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@Stephen\_Meier](https://discuss.elastic.co/u/Stephen_Meier)\
**Post date:** [August 21, 2015, 9:24pm UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864/1 "2015-08-21T21:24:58Z")

</div>

good afternoon all.

I am running the RPM version of logstash on Centos 7. It was working great untill I started having errors. I upgraded to the 1.5.3 package. It relieved the other issue, but it is now running at 100% CPU it is a dual quad core Xeon with 48GB of ram. Would anyone know where to start looking?

Thanks,

---

<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:** [August 22, 2015, 8:55am UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864/2 "2015-08-22T08:55:12Z")

</div>

Posting your config would help 🙂

---

<div class="post-metadata">

**Author:** ![Stephen\_Meier](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@Stephen\_Meier](https://discuss.elastic.co/u/Stephen_Meier)\
**Post date:** [August 27, 2015, 9:21pm UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864/3 "2015-08-27T21:21:32Z")

</div>

Here it is

input {  
lumberjack {  
port =\> 5000  
type =\> "syslog"  
ssl\_certificate =\> "/etc/pki/tls/certs/logstash-forwarder.crt"  
ssl\_key =\> "/etc/pki/tls/private/logstash-forwarder.key"  
}

```
tcp {
type	=> 'powershell-json'
port	=> 3519
codec	=> json {
	charset => 'UTF-8'
}

}

tcp {
    type => "eventlog"
    port => 3515
    codec => json_lines
}

tcp {
    type => "iislog"
    port => 3516
    codec => json_lines

```

}  
udp {  
type =\> "Exchange"  
port =\> 5141  
}  
tcp {  
type =\> "apache"  
port =\> 3517  
}

udp {  
type =\> "loadbalancer"  
port =\> 3518  
}

file {  
path =\> "/upload/bluecoatlogs/SG\*.log"  
type =\> "bluecoat"  
start\_position =\> "beginning"  
}

}

output {

elasticsearch {  
protocol =\> "transport"  
host =\> localhost }

}

\*\*

---

<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:** [August 27, 2015, 9:39pm UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864/4 "2015-08-27T21:39:33Z")

</div>

What java version are you running?

---

<div class="post-metadata">

**Author:** ![Stephen\_Meier](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@Stephen\_Meier](https://discuss.elastic.co/u/Stephen_Meier)\
**Post date:** [November 14, 2015, 12:39am UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864/5 "2015-11-14T00:39:55Z")

</div>

It turns out that it was my configuration. It was reprocessing a very large file everytime that I would restart.

---

<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, 5:22am UTC](https://discuss.elastic.co/t/100-cpu-with-logstash-1-5-x/27864/6 "2017-07-06T05:22:49Z")

</div>