# Logstash CLI not working
**URL:** https://discuss.elastic.co/t/logstash-cli-not-working/73749
**Category:** Logstash
**Created:** [February 2, 2017, 7:59pm UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749 "2017-02-02T19:59:11Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@capsno1](https://discuss.elastic.co/u/capsno1)
#### Post date: [February 2, 2017, 7:59pm UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749/1 "2017-02-02T19:59:11Z")
I managed to install logstash recently but I am unable to use any cli commands.
I followed these instructions ([https://www.elastic.co/guide/en/logstash/current/installing-logstash.html](https://www.elastic.co/guide/en/logstash/current/installing-logstash.html)) using APT.
I had to start logstash using "sudo initctl start logstash"
When I type commands this is what I get:
server:/# bin/logstash -e 'input { stdin { } } output { stdout {} }'
-bash: bin/logstash: No such file or directory
server:/# logstash -e 'input { stdin { } } output { stdout {} }'
logstash: command not found
server:/# cd /opt/logstash/bin
-bash: cd: /opt/logstash/bin: No such file or directory
any help would be appreciated
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [February 3, 2017, 6:48am UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749/2 "2017-02-03T06:48:11Z")
The directory structure of Logstash's Debian packages has changed recently. You can use `dpkg-query -L logstash` to list the files installed by the package.
---
### Author:  [@capsno1](https://discuss.elastic.co/u/capsno1)
#### Post date: [February 3, 2017, 6:37pm UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749/3 "2017-02-03T18:37:31Z")
Thanks…..
Now I need to get around this error…
root@fgprd-oncommand-elasticlog-app001:/var/log/logstash# cat logstash.log
{:timestamp=\>"2017-02-03T12:58:35.212000-0500", :message=\>"An unexpected error occurred!", :error=\>#\, :class=\>"Errno::EACCES", :backtrace=\>["org/jruby/ext/socket/RubyTCPServer.java:124:in `initialize'", "org/jruby/RubyIO.java:853:in`new'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-3.0.4/lib/logstash/inputs/tcp.rb:244:in `new_server_socket'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-3.0.4/lib/logstash/inputs/tcp.rb:79:in`register'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:322:in `start_inputs'", "org/jruby/RubyArray.java:1613:in`each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:321:in `start_inputs'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:172:in`start\_workers'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:126:in `run'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/agent.rb:210:in`execute'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/runner.rb:90:in `run'", "org/jruby/RubyProc.java:281:in`call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/runner.rb:95:in `run'", "org/jruby/RubyProc.java:281:in`call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"], :level=\>:warn}
I can’t seem to get the service to open the 514 ports
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [February 6, 2017, 6:36am UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749/4 "2017-02-06T06:36:26Z")
No, that's because only root can bind to ports \<1024. That matter has been discussed here (and elsewhere) many times before.
---
### Author:  [@capsno1](https://discuss.elastic.co/u/capsno1)
#### Post date: [February 6, 2017, 9:14pm UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749/5 "2017-02-06T21:14:38Z")
I'm not sure if this is a fix or a workaround but I had to set the net\_bind\_service capabilities to the java binary.
setcap cap\_net\_bind\_service=+epi /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
This fixed my issue and logstash is running fine and the ports I named in the config file are now listening.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 6, 2017, 9:14pm UTC](https://discuss.elastic.co/t/logstash-cli-not-working/73749/6 "2017-03-06T21:14:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.