Thank you that's very helpful.
I will start with dev-36 and look to get that solved first. Good point about the configuration file formatting, exactly how sensitive are these files to indentation?
For instance, your example code, nice indentation, assuming that's not tabs but spaces?
I am new to these formats - is more or less spaces in the indentation an issue, surely it is the parenthesis that open and close the statements?
I have been copying and pasting in-between local editors and web pages as building out our documentation set, entirely possibly bad characters could have got in.
I might have this wrong, my understanding is the paths below are the binary and configuration file locations for when running logstash as a service in the background which I have been starting with the command "sudo service logstash start'
/etc/init.d/logstash
/etc/logstash/conf.d/logstash.conf
When it comes to foreground testing, this is best done in the path below for both binary and config files
/opt/logstash/bin/logstash
eg
/opt/logstash/bin/logstash agent -f logstash-minimal.conf
Testing steps:
- 1st execution of Logstash
dev-36:/opt/logstash/bin$ ./logstash agent -f logstash.conf
Settings: Default pipeline workers: 16
Logstash startup completed
- Logstash did not return to the command line
- Opened another terminal to view all processes (ps -A) and could not locate Logstash
- ^Z to return to the command line
^Z
[3]+ Stopped ./logstash agent -f logstash.conf
- 2nd execution of logstash
dev-36:/opt/logstash/bin$ ./logstash agent -f logstash.conf
Settings: Default pipeline workers: 16
The error reported is:
Address already in use - bind - Address already in use
- Other terminal to view all processes (ps -A) and could not locate Logstash
/var/log/logstash/logstash.log did not appear to be updated after the above commands.
Is this the only location for the log file?
Is this log file used regardless of which Logstash binary and configuration file are executed?
What is/was the expected result from the foreground execution of Logstash?
ps on dev-36 (logstash not running)
ps -lu logstash
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
ps on dev-37 (logstash is running)
ps -lu logstash
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
4 S 995 32497 1 1 99 19 - 1761281 - ? 00:07:02 java
ps -u logstash l
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
4 995 32497 1 39 19 7045124 629028 - SNl ? 7:02 /usr/bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+
dev-36 sudo service logstash start
logstash starts and stops
dev-36 /var/logstash/conf.d/logstash.log
{:timestamp=>"2016-03-06T05:21:37.805000+0000", :message=>"Error: Expected one of #, input, filter, output at line 81, column 1 (byte 1426) after "}
{:timestamp=>"2016-03-06T05:21:37.811000+0000", :message=>"You may be interested in the '--configtest' flag which you can\nuse to validate logstash's configuration before you choose\nto restart a running system."}
I don't know what this is referring to?
..at line 81, column 1 (byte 1426) after "}
logstash.conf does not have 81 lines