Guess that's why they call it a beta Per first-event
[07:07:33 @tester:/usr/share/logstash$] bin/logstash -e 'input { stdin { } } output { stdout {} }'
ArgumentError: Path "/usr/share/logstash/data" is not a directory or not writable.
initialize at /usr/share/logstash/logstash-core/lib/logstash/settings.rb:372
call at org/jruby/RubyProc.java:281
validate at /usr/share/logstash/logstash-core/lib/logstash/settings.rb:174
initialize at /usr/share/logstash/logstash-core/lib/logstash/settings.rb:127
initialize at /usr/share/logstash/logstash-core/lib/logstash/settings.rb:368
LogStash at /usr/share/logstash/logstash-core/lib/logstash/environment.rb:18
(root) at /usr/share/logstash/logstash-core/lib/logstash/environment.rb:9
require at org/jruby/RubyKernel.java:1040
(root) at /usr/share/logstash/logstash-core/lib/logstash/runner.rb:1
require at org/jruby/RubyKernel.java:1040
(root) at /usr/share/logstash/lib/bootstrap/environment.rb:67
so let's try as user logstash:
[07:09:22 @tester:/usr/share/logstash$] sudo -u logstash bin/logstash -e 'input { stdin { } } output { stdout {} }'
INFO: Logstash has a new settings file which defines start up time settings. This file is typically located in $LS_HOME/config or /etc/logstash. If you installed Logstash through a package and are starting it manually please specify the location to this settings file by passing in "--path.settings=/path/.." in the command line options
ERROR: Failed to load settings file from "path.settings". Aborting... path.setting=/usr/share/logstash/config, exception=Errno::ENOENT, message=>No such file or directory - /usr/share/logstash/config/logstash.yml
Ok...how about with path info?
[07:08:40 @tester:/usr/share/logstash$] sudo -u logstash bin/logstash --path.settings=/etc/logstash -e 'input { stdin { } } output { stdout {} }'
[07:09:22 @tester:/usr/share/logstash$]
it starts finally, but then exits without waiting for input. Even all the below debug commands come up with empty responses:
[07:18:26 @tester:/usr/share/logstash$] sudo -u logstash bin/logstash --path.settings=/etc/logstash --log.level=trace --config.debug
[07:19:59 @tester:/usr/share/logstash$] sudo -u logstash bin/logstash --path.settings=/etc/logstash --log.level=debug --config.debug
[07:21:36 @tester:/usr/share/logstash$] sudo -u logstash bin/logstash --path.settings=/etc/logstash --log.level=debug -t
[07:23:05 @tester:/usr/share/logstash$] sudo -u logstash bin/logstash --path.settings=/etc/logstash --log.level=debug -t -f /home/logstash-test.conf
Looks like I won't bet doing any more testing this weekend. This is with Ubuntu 16.04 64 bit using oracle-java8-installer 8u101+8u101arm-1~webupd8~2