Logstash giving HUP error

Senz79 · September 15, 2016, 5:15am

Hello

I am trying to run LOGSTASH on Windows but i am constantly getting the below error

"The signal HUP is in use by the JVM and will not work correctly on this platform"

I have tried all means to resolve the issue

Path escape
port in use

I am using logstash 2.4.0

Please help

Thanks

magnusbaeck · September 15, 2016, 5:36am

That's harmless, ignore. See https://github.com/elastic/logstash/issues/5239.

Senz79 · September 15, 2016, 5:43am

Thanks for replying ... the link still do not have any resolution. Can you help me in resolving the same

Regards

magnusbaeck · September 15, 2016, 5:46am

I suppose there isn't any resolution available. As I said, ignore it.

Senz79 · September 15, 2016, 5:47am

Ok . But still my logstash service won't start.

D:\Tools\ELK\logstash-2.4.0\bin>logstash agent -f test.conf
Settings: Default pipeline workers: 4
←[31mPipeline aborted due to error {:exception=>"ArgumentError", :backtrace=>["D
:/Tools/ELK/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-input-file-2.2.
5/lib/logstash/inputs/file.rb:187:in register'", "org/jruby/RubyArray.java:1613 :ineach'", "D:/Tools/ELK/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-
input-file-2.2.5/lib/logstash/inputs/file.rb:185:in register'", "D:/Tools/ELK/l ogstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash /pipeline.rb:330:instart_inputs'", "org/jruby/RubyArray.java:1613:in each'", "D:/Tools/ELK/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-ja va/lib/logstash/pipeline.rb:329:instart_inputs'", "D:/Tools/ELK/logstash-2.4.0
/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:
180:in start_workers'", "D:/Tools/ELK/logstash-2.4.0/vendor/bundle/jruby/1.9/ge ms/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:136:inrun'", "D:/Tools/EL
K/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logst
ash/agent.rb:491:in `start_pipeline'"], :level=>:error}←[0m
stopping pipeline {:id=>"main"}
The signal HUP is in use by the JVM and will not work correctly on this platform

D:\Tools\ELK\logstash-2.4.0\bin>

magnusbaeck · September 15, 2016, 6:04am

Yes, but that's because you have a relative path in your file input configuration:

github.com

logstash-plugins/logstash-input-file/blob/v2.2.5/lib/logstash/inputs/file.rb#L187


  :discover_interval => @discover_interval,
  :sincedb_write_interval => @sincedb_write_interval,
  :delimiter => @delimiter,
  :ignore_older => @ignore_older,
  :close_older => @close_older,
  :max_open_files => @max_open_files
}


@path.each do |path|
  if Pathname.new(path).relative?
    raise ArgumentError.new("File paths must be absolute, relative path specified: #{path}")
  end
end


if @sincedb_path.nil?
  if ENV["SINCEDB_DIR"].nil? && ENV["HOME"].nil?
    @logger.error("No SINCEDB_DIR or HOME environment variable set, I don't know where " \
                  "to keep track of the files I'm watching. Either set " \
                  "HOME or SINCEDB_DIR in your environment, or set sincedb_path in " \
                  "in your Logstash config for the file input with " \
                  "path '#{@path.inspect}'")

magnusbaeck · September 15, 2016, 6:12am

I've raised an issue to improve the error message.

Senz79 · September 15, 2016, 6:14am

Thanks a lot for the support. The below link helped me to resolve the issue

theuntergeek · October 5, 2016, 1:17pm

This message is not fatal to Logstash. If you are having configuration errors, they are not what is generating these messages. The HUP message is actually from JRuby.