Nagios Support Forum

If you can give me a more concrete example pf what you're trying to accomplish, I'll see if i can help

That's actually a good point. The processes can fall victim to the system out of memory killer. There should be evidence of that in the system logs if it happened.

Nothing yet that we can confirm, but despite that it is blipping on the radar.

Thanks! I'll have the doc team have a look at it.

Same question what version of Log Server and what precisely do you mean by things not showing up in the console?

That's exactly the best way to fix it. I'll have a look into what's going on during the upgrade that caused that step to not happen. The changelog issue if you're interested will be NLS#810.

I'm pleased to announce that we have released Nagios Log Server 2026R1.0.3 this morning; the upgrade issue is resolved.

I've got a bunch of questions for you: You mentioned a cluster. How many instances do you have in it? Is OpenSearch running on all of them? If not, what happens when you run systemctl start opensearch on the ones that aren't running? How is the disc space situation on your instances? I'm wondering i...

OK there's a few other things that end up getting done in the fixed upgrade. it will fi up the jvm.options file as well. The fix will be in the 2026R1.0.3 release of Nagios Log Server. For anyone else who comes across this before 1.0.3 is released, feel free to remove that line from the jvm.options ...

Our internal issue number for this is 801. Please monitor the changelog for a line item for NLS#801 in the forthcoming releases. In the meantime you can work around the problem by copying /tmp/nagioslogserver/subcomponents/opensearch/mods/opensearch/jvm.options to /usr/local/nagioslogserver/opensear...