windows-shipper-self-monitor stops after a few seconds

[fandrei]

I've installed the windows-shipper-self-monitor service, and after working a few seconds it terminates. Event log contains the following warning messages:

Child process [3312 - java -Xmx256m -jar "C:\temp\self-monitor\logstash.jar" agent -f "config.conf" -v] terminated with 1

Any ideas?

[dpb587]

Are there any log files in C:\temp\self-monitor\?

[fandrei]

windows-shipper-service.err.log contains this:

{:timestamp=>"2013-09-23T21:39:10.377000+0700", :message=>"Read config", :level=>:info}
{:timestamp=>"2013-09-23T21:39:10.549000+0700", :message=>"Start thread", :level=>:info}
{:timestamp=>"2013-09-23T21:39:10.876000+0700", :message=>"Failure loading plugin from config: 'input { wmi { ... } }' - is that really a valid input plugin? (check for typos!)", :level=>:fatal}
Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (LoadError) no such file to load -- logstash/inputs/wmi
    at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1027)
    at Kernel.require(jar:file:/C:/temp/self-monitor/logstash.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/custom_require.rb:36)
    at Kernel.require(file:/C:/temp/self-monitor/logstash.jar!/logstash/JRUBY-6970.rb:13)
    at RUBY.tryload(file:/C:/temp/self-monitor/logstash.jar!/logstash/config/file.rb:62)
    at RUBY.parse(file:/C:/temp/self-monitor/logstash.jar!/logstash/config/file.rb:47)
    at RUBY.each(file:/C:/temp/self-monitor/logstash.jar!/logstash/config/file.rb:91)
    at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
    at RUBY.each(file:/C:/temp/self-monitor/logstash.jar!/logstash/config/file.rb:90)
    at org.jruby.RubyHash.each(org/jruby/RubyHash.java:1257)
    at RUBY.each(file:/C:/temp/self-monitor/logstash.jar!/logstash/config/file.rb:83)
    at RUBY.parse(file:/C:/temp/self-monitor/logstash.jar!/logstash/config/file.rb:39)
    at RUBY.parse_config(file:/C:/temp/self-monitor/logstash.jar!/logstash/agent.rb:323)
    at RUBY.run_with_config(file:/C:/temp/self-monitor/logstash.jar!/logstash/agent.rb:427)
    at org.jruby.ext.thread.Mutex.synchronize(org/jruby/ext/thread/Mutex.java:149)
    at RUBY.run_with_config(file:/C:/temp/self-monitor/logstash.jar!/logstash/agent.rb:426)
    at RUBY.run(file:/C:/temp/self-monitor/logstash.jar!/logstash/agent.rb:373)
    at org.jruby.RubyProc.call(org/jruby/RubyProc.java:249)
    at RUBY.initialize(jar:file:/C:/temp/self-monitor/logstash.jar!/gems/stud-0.0.17/lib/stud/task.rb:12)

[dpb587]

I think maybe @mrdavidlaing was somehow using logstash-2.1 for the self-monitor shipper, because I don't see wmi as a supported input in the 1.1.13 docs.

[dpb587]

Rather, 2.1 => 1.2 docs

[mrdavidlaing]

@fandrei, @dpb587 -> my bad - I manually downloaded using logstash-1.2 for the self-monitor shipper and didn't update the build scripts.

[fandrei]

Interesting, that build scripts download logstash-1.1.13-pr19b5(patched) on every build.

[fandrei]

Building with logstash-1.2 seems to solve this problem; it's necessary to fix the provision file.

[fandrei]

@mrdavidlaing, I've applied a fix. plz change if it's correct

[mrdavidlaing]

@fandrei -

1. Please push changes into a new branch and create a Pull Request rather than committing directly to master. @dpb587 is the only one who should be merging changes into master, since he controls the scheduling of releases. I've reverted your commit from the master branch.
2. We still need to be able to build a shippers using logstash-1.1.13-pr19b5(patched) [which contains fixes for #126 and #174]
3. For windows-shipper-self-monitor we need to be able to build a shipper that uses logstash-1.2. I think we should go for a new config option in the settings.yml that enables overriding the logstash download url from its default of logstash-1.1.13-pr19b5(patched).

Sorry I don't have time to provide some code for 3. Could you have a go at implementing the settings.yml idea please?

[mrdavidlaing]

@fandrei did you have any luck with implementing the a new config option in the settings.yml ?

The way to submit a PR is nicely documented at https://github.com/cityindex/logsearch-development-flow/blob/master/CONTRIBUTING.md

[fandrei]

@mrdavidlaing as far as I understand we need to move to logstash 1.2 to resolve this (what is another issue that's already created)

[mrdavidlaing]

@fandrei, @dpb587 has already created a patched logstash v1.2 build; and #215 starts the work to update the shipper build scripts to use this.

Please could you try building the windows-shipper-self-monitor using the #215 branch, and see if that resolves the issue.

[sopel]

Closed as Won't Fix in favor of a heartbeat style monitoring of the shipper itself as discussed via https://github.com/cityindex/logsearch-config/issues/41.