topic Re: Nuxeo LTS 2023 Local Install. in Nuxeo Forum

Nuxeo LTS 2023 Local Install.

Sudarshan_Ghate — Wed, 02 Apr 2025 00:22:53 GMT

Hello,

I am trying to install Nuxeo LTS2023 locally on my machine using the ZIP distribution. I am able to start the instance but as soon as I login, to the instance, I start seeing errors in the server.log. Here is what I see in the server.log.

2025-04-01T19:59:42,646 INFO [main] [org.nuxeo.runtime.osgi.OSGiRuntimeService] Nuxeo Platform Started
======================================================================
= Component Loading Warnings:
* In-Memory type for log config "default" is ONLY for testing purpose. Use Kafka for production.
* In-Memory type for log config "bulk" is ONLY for testing purpose. Use Kafka for production.
* In-Memory type for log config "audit" is ONLY for testing purpose. Use Kafka for production.
* In-Memory type for log config "pubsub" is ONLY for testing purpose. Use Kafka for production.
* Elasticsearch embedded configuration is ONLY for testing purpose. You need to create a dedicated Elasticsearch cluster for production.
======================================================================
= Component Loading Status: Pending: 0 / Missing: 0 / Unstarted: 0 / Total: 562
======================================================================
2025-04-01T20:02:09,719 ERROR [http-nio-0.0.0.0-8080-exec-6] [org.nuxeo.runtime.transaction.TransactionHelper] Could not mark transaction as rollback only
java.lang.IllegalStateException: No transaction associated with current thread

I am not sure what is missing ?

Thank you,

Re: Nuxeo LTS 2023 Local Install.

Josh-F-Hyland — Wed, 02 Apr 2025 00:42:02 GMT

Is it causing any problems at runtime? Only the last 2 lines of your log are errors, the rest is normal. Are you saying to get this error only after login, or every time you interact with WebUI? Or something else? Which OS?

Re: Nuxeo LTS 2023 Local Install.

Sudarshan_Ghate — Wed, 02 Apr 2025 01:04:47 GMT

It is Windows 10. LTS 2023.

The following is from mp-list.

hotfix started nuxeo-2023-HF28 (id: nuxeo-2023-HF28-1.0.0)
addon started nuxeo-web-ui (id: nuxeo-web-ui-3.1.17)

It happens as soon as I try to login.

I have attached the server.log (Unfortunately I had to PDF it). I have not loaded any of my Studio components so I think this is as basic as it gets.

Thank you

Re: Nuxeo LTS 2023 Local Install.

Sudarshan_Ghate — Wed, 02 Apr 2025 01:54:15 GMT

Additional info:

java -version produces the following

JAVA_HOME=C:\Program Files\Zulu\zulu-17

Thanks

Re: Nuxeo LTS 2023 Local Install.

Josh-F-Hyland — Wed, 02 Apr 2025 16:17:25 GMT

That's the complete output from "mp-list"? If so that's really strange. You should see all 28 hotfixes installed, not just one. You might want to remove HF28 and run "mp-hotfix". Hot fixes are not cumulative, you have to install all of them (but this is normally automatic via dependency management).

My understanding is that launching on Windows requires running "nuxeoctl console" and not "nuxeoctl start" (or at least it seems to work better). I would actually recommend using WSL to be honest. It's easier to manage in general.

Re: Nuxeo LTS 2023 Local Install.

Sudarshan_Ghate — Wed, 02 Apr 2025 16:46:18 GMT

No, I just showed you the last two lines to indicate that I am most up to date on all the Hotfixes. Here is complete screenshot.

I see the same behavior regardless of whether I try the "nuxeoctl console" or "nuxeoctl start".

Thanks,

Re: Nuxeo LTS 2023 Local Install.

Josh-F-Hyland — Wed, 02 Apr 2025 17:01:16 GMT

Understood. The logs are inconsistent so I'm not sure what's going on. E.g. in the PDF from your other post you have:

2025-04-01T20:54:08,340 ERROR [opensearch[nuxeoNode][generic][T#1]]
[org.opensearch.monitor.fs.FsHealthService] health check of
[C:\Nuxeo2023\nxserver\data\elasticsearch\nodes\0] failed, took [1067764ms] which is above
the healthy threshold of [1m]

I can say this doesn't look familiar 😞 You might try extracting a fresh copy of the zip. I have found that the embedded components (e.g. ElasticSearch, H2) can get corrupted relatively easily as you iterate through a first time install. You can delete the content in nxserver/data (keep your CLID file) but it may be faster/simpler to just use a fresh copy. If that doesn't work I think you'll need to contact Support to dig further.