StatusLogger error while starting Logstash 5, but indexting working

Elastic Stack Logstash
1

Hi,

When I start logstash using the command;

./logstash --path.settings=../config/ -f ../logstash.conf

I am getting the error;

ERROR StatusLogger Unable to access file://../config/log4j2.properties

But after sometime, the fetching of data from jdbc (that I have defined in conf file) completes and it indexes values to easticsearch. Why is this happening, and how can I fix this? I have set 0770 for all files in config folder.

2

I'm guessing this is just a failure to use a relative path with the file:// uri scheme...
can you try passing an absolute path to --path.settings instead of a relative one?

3

I tried that too.. same error then also.

4

Strange..I can replicate your issue with relative paths, but not with absolute paths:

/tmp/logstash-5.0.0/bin % ./logstash --path.settings=../config/ -f ../cfg
ERROR StatusLogger Unable to access file://../config/log4j2.properties
 java.net.UnknownHostException: ..
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
	at java.net.Socket.connect(Socket.java:589)
	at java.net.Socket.connect(Socket.java:538)
	at sun.net.ftp.impl.FtpClient.doConnect(FtpClient.java:957)
	at sun.net.ftp.impl.FtpClient.tryConnect(FtpClient.java:917)
	at sun.net.ftp.impl.FtpClient.connect(FtpClient.java:1012)
	at sun.net.ftp.impl.FtpClient.connect(FtpClient.java:998)
	at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:294)
	at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:393)
	at java.net.URL.openStream(URL.java:1038)
         ...
ERROR StatusLogger Unable to access file://../config/log4j2.properties
 java.net.UnknownHostException: ..
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
	at java.net.Socket.connect(Socket.java:589)
	at java.net.Socket.connect(Socket.java:538)
	at sun.net.ftp.impl.FtpClient.doConnect(FtpClient.java:957)
	at sun.net.ftp.impl.FtpClient.tryConnect(FtpClient.java:917)
	at sun.net.ftp.impl.FtpClient.connect(FtpClient.java:1012)
	at sun.net.ftp.impl.FtpClient.connect(FtpClient.java:998)
	at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:294)
	at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:393)
	at java.net.URL.openStream(URL.java:1038)
         ...
	at org.jruby.Ruby.runScript(Ruby.java:857)
	at org.jruby.Ruby.runScript(Ruby.java:850)
	at org.jruby.Ruby.runNormally(Ruby.java:729)
	at org.jruby.Ruby.runFromMain(Ruby.java:578)
	at org.jruby.Main.doRunFromMain(Main.java:393)
	at org.jruby.Main.internalRun(Main.java:288)
	at org.jruby.Main.run(Main.java:217)
	at org.jruby.Main.main(Main.java:197)
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Sending Logstash logs to /tmp/logstash-5.0.0/logs which is now configured via log4j2.properties.
11:12:31.239 [[main]-pipeline-manager] INFO  logstash.pipeline - Starting pipeline {"id"=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>500}
11:12:31.255 [[main]-pipeline-manager] INFO  logstash.pipeline - Pipeline main started
11:12:31.326 [Api Webserver] INFO  logstash.agent - Successfully started Logstash API endpoint {:port=>9600}
{
          "epoc" => 1478085151,
      "sequence" => 0,
    "@timestamp" => 2016-11-02T11:12:31.487Z,
      "@version" => "1",
          "host" => "Joaos-MBP-5.lan",
       "message" => "Hello world!"
}
11:12:34.279 [LogStash::Runner] WARN  logstash.agent - stopping pipeline {:id=>"main"}
/tmp/logstash-5.0.0/bin % 

/tmp/logstash-5.0.0/bin % ./logstash --path.settings=/tmp/logstash-5.0.0/config/ -f ../cfg
Sending Logstash logs to /tmp/logstash-5.0.0/logs which is now configured via log4j2.properties.
{
          "epoc" => 1478085180,
      "sequence" => 0,
    "@timestamp" => 2016-11-02T11:13:00.437Z,
      "@version" => "1",
          "host" => "Joaos-MBP-5.lan",
       "message" => "Hello world!"
}
5

hmm.. lemme recheck it again, whether the path is "correct" or not.