# Issue in Logstash after Upgrade

**URL:** https://discuss.elastic.co/t/issue-in-logstash-after-upgrade/123421
**Category:** Logstash
**Created:** [March 11, 2018, 10:36am UTC](https://discuss.elastic.co/t/issue-in-logstash-after-upgrade/123421 "2018-03-11T10:36:24Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [March 11, 2018, 9:42pm UTC](https://discuss.elastic.co/t/issue-in-logstash-after-upgrade/123421/2 "2018-03-11T21:42:38Z")

</div>

I found a relevant issue on github, with comments that should provide a path forward:

> Ports in range 1 to 1024 are privileged and only root user can listen on it.
> 
> Options:
> 
> - run logstash as root (not a good idea)
> - use setcap to grant java permission to use privileged ports
> - use iptables or a proxy to forward port 514 to an unprivileged port.
> 
> -- [logstash will not open a listening port. · Issue #1587 · elastic/logstash · GitHub](https://github.com/elastic/logstash/issues/1587#issuecomment-50939823)

This blog post is specifically about using `setcap` to set capabilities for Java (although it references Java 7, and Logstash currently requires Java 8, so you may need to adjust it slightly):

> **[Oracle Blogs](https://blogs.oracle.com/)**
>
> Oracle Blogs

---

_[View the full topic](https://discuss.elastic.co/t/issue-in-logstash-after-upgrade/123421)._