Problems installing NLS on RHEL8.9

[joubja9]

I have a 3 node cluster in my staging environment...
RHEL7.9
Nagios Log Server 2024R1.0.1

I am upgrading the RHEL7.9 to RHEL8.9. I did a new build of RHEL8.9, and then installed Nagios Log Server, attaching to the other 2 nodes in the cluster.

Installing the software and joining the cluster succeeds but there are a couple of issues.
1. Logstash does not start. It seems /usr/local/nagioslogserver/logstash/etc/conf.d/ is empty?

2. The system serves the homepage on http port 80 or https port 443... but, things like the "admin" page and others are only available via http port 80

Thanks in advance for any tips.

[jmichaelson]

This sounds very odd. That said, I'm going to suggest going to http://{ip address of server or host name}/nagioslogserver/configure/apply, and check if anything gets written to the conf.d directory as a reuslt.

[joubja9]

Thank you.

I get this on all servers in the cluster...

Code: Select all

Apply Configuration
The config is currently being applied. This may take a few minutes. Below is a list of all current instances and their status.

 The instance is likely offline, please check and try again.
 

The cluster status is green, the instances are green, and verified that Elasticsearch is running on all nodes, and Logstash is running on the 2 nodes that I haven't messed with yet.

[jmichaelson]

did the conf.d directory get populated after you did that?

[joubja9]

No. It did not. It's still empty.

[jmichaelson]

What happens (not to the conf.d directory) when you click verify config on that screen?

[joubja9]

There is no Verify on that page. But if I look in the left margin, there is "Per Instance" and that only shows node1 as online, with node2 and node3 as offline. If I click "Verify" on node03 anyway... it returns...


{:timestamp=>"2024-04-08T19:48:39.754000+0000", :message=>"An unexpected error occurred!", :error=>"No config files found: /usr/local/nagioslogserver/tmp/66144a109db17\nCan you make sure this path is a logstash config file?", :class=>"RuntimeError", :backtrace=>["/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/config/loader.rb:58:in `local_config'", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/config/loader.rb:37:in `load_config'", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/config/loader.rb:17:in `format_config'", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/agent.rb:185:in `execute'", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/runner.rb:94:in `run'", "org/jruby/RubyProc.java:281:in `call'", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.1-java/lib/logstash/runner.rb:99:in `run'", "org/jruby/RubyProc.java:281:in `call'", "/usr/local/nagioslogserver/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"], :level=>:warn}

[jmichaelson]

To be honest, I think this one might require using a support call. https://answerhub.nagios.com/support/s/