Just downloaded elastic search version 8.13.2 and ran the elasticsearch.bat. it return with this error. Elasticsearch died while starting up, with exit code 1

[2024-04-18T16:13:57,555][INFO ][o.e.n.NativeAccess ] [DCAP919WAS905DB] Using [jdk] native provider and native methods for [Windows]
[2024-04-18T16:13:57,937][ERROR][o.e.b.Elasticsearch ] [DCAP919WAS905DB] fatal exception while booting Elasticsearch
java.lang.IllegalStateException: jar hell!
class: com.ibm.db2.jcc.licenses.DB2J
jar1: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cisuz.jar
jar2: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cu.jar
at org.elasticsearch.jdk.JarHell.checkClass(JarHell.java:315) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:233) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:84) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:182) ~[elasticsearch-8.13.2.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) ~[elasticsearch-8.13.2.jar:?]
[2024-04-18T16:22:59,617][INFO ][o.e.n.NativeAccess ] [DCAP919WAS905DB] Using [jdk] native provider and native methods for [Windows]
[2024-04-18T16:23:00,026][ERROR][o.e.b.Elasticsearch ] [DCAP919WAS905DB] fatal exception while booting Elasticsearch
java.lang.IllegalStateException: jar hell!
class: com.ibm.db2.jcc.licenses.DB2J
jar1: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cisuz.jar
jar2: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cu.jar
at org.elasticsearch.jdk.JarHell.checkClass(JarHell.java:315) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:233) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:84) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:182) ~[elasticsearch-8.13.2.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) ~[elasticsearch-8.13.2.jar:?]
[2024-04-18T16:30:54,623][INFO ][o.e.n.NativeAccess ] [DCAP919WAS905DB] Using [jdk] native provider and native methods for [Windows]
[2024-04-18T16:30:54,959][ERROR][o.e.b.Elasticsearch ] [DCAP919WAS905DB] fatal exception while booting Elasticsearch
java.lang.IllegalStateException: jar hell!
class: com.ibm.db2.jcc.licenses.DB2J
jar1: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cisuz.jar
jar2: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cu.jar
at org.elasticsearch.jdk.JarHell.checkClass(JarHell.java:315) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:233) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:84) ~[elasticsearch-core-8.13.2.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:182) ~[elasticsearch-8.13.2.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) ~[elasticsearch-8.13.2.jar:?]

Jar Hell is about Jar conflicts

Thanks and I can see that but those jar file is needed for my db2 server

Why do you need this in the Elasticsearch JVM?

To run Elasticsearch in parallel with another product that leverage elasticsearch and kibana for Dashboard.

It appears that Elasticsearch has conflict co-located with a system that has DB2 installed.

Do not modify the classpath of the Elasticsearch JVM.

I am not modifying any classpath. I ran the installer and this is the error I get.
I can see kibana is up and running.
When I try to install Elasticsearch it threw that error.

Kibana is ready to go.
see below.
\u001b[97m\u001b[1m\u001b[96mi\u001b[39m\u001b[97m Kibana has not been configured.\u001b[22m\u001b[39m
Go to \u001b[96m\u001b[4mhttp://localhost:5601/?code=756496\u001b[24m\u001b[39m to get started.

=====================

Here is Elasticsearch when starting up.

C:\Kibana\elasticsearch-8.13.2\bin>elasticsearch.bat
Aborting auto configuration because the node keystore contains password settings already
Apr 18, 2024 4:30:53 PM sun.util.locale.provider.LocaleProviderAdapter
WARNING: COMPAT locale provider will be removed in a future release
[2024-04-18T16:30:54,623][INFO ][o.e.n.NativeAccess ] [DCAP919WAS905DB] Using [jdk] native provider and native methods for [Windows]
[2024-04-18T16:30:54,959][ERROR][o.e.b.Elasticsearch ] [DCAP919WAS905DB] fatal exception while booting Elasticsearchjava.lang.IllegalStateException: jar hell!
class: com.ibm.db2.jcc.licenses.DB2J
jar1: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cisuz.jar
jar2: C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cu.jar
at org.elasticsearch.base@8.13.2/org.elasticsearch.jdk.JarHell.checkClass(JarHell.java:315)
at org.elasticsearch.base@8.13.2/org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:233)
at org.elasticsearch.base@8.13.2/org.elasticsearch.jdk.JarHell.checkJarHell(JarHell.java:84)
at org.elasticsearch.server@8.13.2/org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:182)
at org.elasticsearch.server@8.13.2/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73)

See logs for more details.

ERROR: Elasticsearch did not exit normally - check the logs at C:\Kibana\elasticsearch-8.13.2\logs\elasticsearch.log

ERROR: Elasticsearch died while starting up, with exit code 1

am not modifying any classpath. I ran the installer and this is the error I get.
I can see kibana is up and running.
When I try to install Elasticsearch it threw that error.

Kibana is ready to go.
see below.

Go to \u001b[96m\u001b[4mhttp://localhost:5601/?code=756496\u001b[24m\u001b[39m to get started.

The issue is with elasticsearch.

it threw the

ERROR: Elasticsearch did not exit normally - check the logs at C:\Kibana\elasticsearch-8.13.2\logs\elasticsearch.log

ERROR: Elasticsearch died while starting up, with exit code 1

This is not part of the Elasticsearch jvm or distribution

C:\PROGRA~1\IBM\SQLLIB~1\java\db2jcc_license_cisuz.jar

This is from IBM DB2. I think there is a co-location issue.
Thanks I think I have what I need.

Probably. Not sure why ES is not starting with the embedded JVM and with this JAR.
May be look at your env variables.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.