OpenSearch doesn't start after Update

[Giosue]

When rebooting after updating Nagios Log Server from version 2026R1 to 2026R1.0.2, the OpenSearch service does not start and cannot be started manually because it keeps returning an error.

[jmichaelson]

What kind of error are you seeing from it? Can you share the contents of /usr/local/nagioslogserver/opensearch/logs/nagios_opensearch.log

[[email protected]]

Hi.

I assume, we have same problem.

if i try to run

/usr/local/nagioslogserver/opensearch/bin/opensearch --help

I have got error:

Exception in thread "main" java.lang.RuntimeException: starting java failed with [1]
output:
Error occurred during initialization of VM
agent library failed Agent_OnLoad: instrument
error:
Error opening zip file or JAR manifest missing : agent/opensearch-agent.jar
at org.opensearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:125)
at org.opensearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:87)
at org.opensearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:70)
at org.opensearch.tools.launchers.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:150)
at org.opensearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:108)


Best Regards

Karel Novák

[jmichaelson]

I want to try reproducing this myself. Could one of you provide before and after version numbers of Log Server, and which particular Linux distribution and version you're using?

[[email protected]]

We have Oracle Linux Server release 9.7 (derive from Red Hat Enterprise Linux release 9.7 (Plow) ), and update was from 2026R1.0.1 to 2026R1.0.2 version.

[jmichaelson]

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/opensearch/config/jvm.options

Replace /tmp with wherever you extracted the initial tarball.

e.g.,

cp /tmp/nagioslogserver/subcomponents/opensearch/mods/opensearch/jvm.options /usr/local/nagioslogserver/opensearch/config/jvm.options

and then

systemctl restart opensearch.service

[[email protected]]

Some update:

I try to copy jvm.options from latest instalation package, but it has no efect, because the file contain same error.

"21-:-javaagent:agent/opensearch-agent.jar"

I figure out the updater create backup file from old config with .bak extension in same directory /usr/local/nagioslogserver/opensearch/config.

So i tried to backup options file:

mv /usr/local/nagioslogserver/opensearch/config/jvm.options /usr/local/nagioslogserver/opensearch/config/jvm.options.bak1

re-use this old config file

cp /usr/local/nagioslogserver/opensearch/config/jvm.options.bak /usr/local/nagioslogserver/opensearch/config/jvm.options

and restart service.

systemctl restart opensearch.service

finally service successfully started.

BR

KNo

[Bulkasender]

Confirmed: The issue is in the line 21-:-javaagent:agent/opensearch-agent.jar in the new jvm.options. The path agent/opensearch-agent.jar is relative and doesn't exist in the OpenSearch working directory.

Working solution (as karel.novak posted):

Code: Select all

cp /usr/local/nagioslogserver/opensearch/config/jvm.options.bak /usr/local/nagioslogserver/opensearch/config/jvm.options
systemctl restart opensearch.service

Alternatively, manually comment out or remove the line containing javaagent:agent/opensearch-agent.jar from jvm.options.

Awaiting official fix in NLS#801.Solana fees

[bpennin]

The manually committing out of the following line worked for us:

Alternatively, manually comment out or remove the line containing javaagent:agent/opensearch-agent.jar from jvm.options.

Awaiting official fix in NLS#801.

[jmichaelson]

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 file. it'll get replaced and corrected with the 2026R1.0.3 release