Home » Categories » Products » Nagios Log Server » Troubleshooting » Common Problems

Nagios Log Server - Logstash not running after upgrade to 2.0

Overview

After upgrading to Nagios Log Server 2.0, the logstash service doesn't remain running.

 

Diagnosis

The /var/log/logstash/logstash.log file will show a message similar to:

{:timestamp=>"2017-11-14T08:24:17.314000-0700", :message=>"Pipeline aborted due to error", :exception=>"LogStash::
ConfigurationError", :error=>"The setting `host` in plugin `elasticsearch` is obsolete and is no longer available. Please use the 'hosts' setting
 instead. You can specify multiple entries separated by comma in 'host:port' format. If you have any questions about this, you are invited to
visit https://discuss.elastic.co/c/logstash and ask.", :backtrace=>
["/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/config/mixin.rb:88:in `config_init'",
 "org/jruby/RubyHash.java:1342:in `each'",
"/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/config/mixin.rb:72:in `config_init'",
 "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/outputs/base.rb:79:in `initialize'",
 "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/output_delegator.rb:74:in `register'
", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/pipeline.rb:181:in `start_workers'
", "org/jruby/RubyArray.java:1613:in `each'",
"/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/pipeline.rb:181:in `start_workers'",
"/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/pipeline.rb:136:in `run'",
 "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/agent.rb:491:in `start_pipeline'"],
:level=>:error}

 


 

Problem

Logic in the initially released upgrade script didn't allow logstash config files to be rewritten correctly.

 

 

Solution

The upgrade script has been updated and a new download of the 2.0 software resolves the problem.

It can also be resolved by running the following command in a terminal session as the root user:

/usr/bin/php /var/www/html/nagioslogserver/www/index.php configure/write_configs_for_node

 

This command needs to be executed on each instance in your Nagios Log Server Cluster.

 

 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/

5 (1)
Article Rating (1 Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Nagios Log Server - Understanding and Troubleshooting Yellow Cluster Health
Viewed 3748 times since Mon, Feb 15, 2016
Installation errors on customized corporate builds of CentOS or RHEL
Viewed 3295 times since Tue, Jan 26, 2016
Nagios Log Server - Troubleshooting SELinux and rsyslog
Viewed 2248 times since Wed, Mar 30, 2016
Nagios Log Server - Logs Not Searchable or Not Coming In
Viewed 5143 times since Tue, Jan 27, 2015
Nagios Log Server - Troubleshooting Commands
Viewed 1504 times since Mon, Feb 11, 2019
Web Browser Reports 330 Error Content Encoding
Viewed 1483 times since Tue, Mar 7, 2017
Nagios Log Server - License Key Not Accepted
Viewed 1510 times since Wed, Apr 12, 2017
Nagios Log Server - Resetting nagiosadmin Password
Viewed 3421 times since Tue, Aug 9, 2016
Nagios Log Server - Newline Character Added When Adding A Filter To A Search
Viewed 1335 times since Wed, Apr 27, 2016
Nagios Log Server - Understanding and Troubleshooting Red Cluster Health
Viewed 2602 times since Mon, Apr 6, 2015