Original Message:
Sent: Wed July 03, 2024 07:20 AM
From: Oktawian Powązka
Subject: After update ILMT to 9.2.36.0 does not start
SkyNet awakening?
Could be....
Anyhow, I think that this weird
mv behavior is somehow associated with particular RHEL release (8.9), as you've stated in the ticket:
Weve upgraded to 9.2.35 in March without a problem and later we had to upgrade our ILMT RHEL Server from 7.9 to 8.9This is the first upgrade of ILMT which happened after the release change of the RHEL server it is running on!
Wouldn`t that be affected by the fact that this is the mount point of the dedicated filesystem?
You are absolutely correct, I've got ahead of my self...forgetting that this path is a dedicated mount point.
Just move the current ILMT folder (/opt/ibm/LMT) content to somewhere else...
It doesn't really matter if the fresh installer is via BigFix or from command line...
By 'connect into the existing temadb database' I've meant to fill in the existing ILMT database name on the setup database page.
From the upgrade log I can see that yours ILMT database is called TEMADB
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Wed July 03, 2024 06:31 AM
From: Stephan Dietl
Subject: After update ILMT to 9.2.36.0 does not start
Hello @Oktawian Powązka!
Thanks for your quick response!
> It looks like that somehow mv command has got a mind on its own and placed the server subfolder under wlp rather than renaming into that name.
> I can't give you any logical explanation to this conundrum...
SkyNet awakening? ;)
> I can see that you've got a dedicated mount point '/opt/ibm/LMT' for ILMT server location, but such scenario has already been tested by us and other Customers.
> Anyhow, there is a pretty quick workaround to this whole mess:
> Rename (just to have it as a backup) the existing ILMT folder '/opt/ibm/LMT',
Wouldn`t that be affected by the fact that this is the mount point of the dedicated filesystem?
> Rename or delete the '/var/.com.zerog.registry.xml' file.
> run the fresh installer
Via BigFix?
> and connect into the existing temadb database (at the setup database page please point out the existing temadb location)
The one mentioned in /opt/ibm/LMT/wlp/usr/servers/server1/config/database.yml ? How to find out the location please?
Thanks!
With kind regards,
Steve
------------------------------
Stephan Dietl
Original Message:
Sent: Wed July 03, 2024 05:59 AM
From: Oktawian Powązka
Subject: After update ILMT to 9.2.36.0 does not start
Hello Stephan,
Just looked into it...
Pretty interesting behavior of the mv command:
dbg - com.ibm.license.mgmt.install.ia.util.ExecuteCmd.execute - Executing command: [mv] [-v] [/opt/ibm/LMT/server] [/opt/ibm/LMT/wlp]
dbg - com.ibm.license.mgmt.install.ia.util.ExecuteCmd.waitFor - timeot = 0 means wait indefinitely
dbg - com.ibm.license.mgmt.install.ia.util.ExecuteCmd.logResult - Command completed --------------------------
dbg - com.ibm.license.mgmt.install.ia.util.ExecuteCmd.logResult - return Code 0
dbg - com.ibm.license.mgmt.install.ia.util.ExecuteCmd.logResult - Stdout renamed '/opt/ibm/LMT/server' -> '/opt/ibm/LMT/wlp/server'
It looks like that somehow mv command has got a mind on its own and placed the server subfolder under wlp rather than renaming into that name.
I can't give you any logical explanation to this conundrum...
I can see that you've got a dedicated mount point '/opt/ibm/LMT' for ILMT server location, but such scenario has already been tested by us and other Customers.
Anyhow, there is a pretty quick workaround to this whole mess:
Rename (just to have it as a backup) the existing ILMT folder '/opt/ibm/LMT',
Rename or delete the '/var/.com.zerog.registry.xml' file.
run the fresh installer and connect into the existing temadb database (at the setup database page please point out the existing temadb location)
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Wed July 03, 2024 04:55 AM
From: Stephan Dietl
Subject: After update ILMT to 9.2.36.0 does not start
Hello @Oktawian Powązka !
> Due to the bigger amount of files which needs to be exchanged I'd strongly suggest to open support ticket to us....
I´ve now opened TS016642688 :) !
Thanks,
With kind regards,
Steve
------------------------------
Stephan Dietl
Original Message:
Sent: Wed July 03, 2024 03:00 AM
From: Oktawian Powązka
Subject: After update ILMT to 9.2.36.0 does not start
Hello again,
I was not able to reply to your private email...
Anyhow,
That path:
/opt/ibm/LMT/wlp/server/usr/servers/server1/server.xml
is definitely not correct...
It looks like some aftermath of the failed upgrade process.
To go further I'd need to look into the upgrade logs (If those are not available just send us the whole '/opt/ibm/LMT/resume' folder content).
At last,
Due to the bigger amount of files which needs to be exchanged I'd strongly suggest to open support ticket to us....
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Tue July 02, 2024 03:02 PM
From: Oktawian Powązka
Subject: After update ILMT to 9.2.36.0 does not start
Hello,
This one is not related...
Have you manually modified the server.xml after ILMT Installation/Upgrade ?
In particular the <featureManager> stanza ?
To go further I'd need to look into your server.xml + ffdc_24.07.02_14.11.52.0.log file.
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Tue July 02, 2024 02:51 PM
From: Stephan Dietl
Subject: After update ILMT to 9.2.36.0 does not start
Hello @Andrei Ionescu!
I´ve waited for 9.2.36.1 but after installing it (the fixlet had the status "fixed") the App on Port 9080 won´t start and I see the following message in the tema.log, is this related? Thanks!
[7/2/24 14:11:52:125 UTC] 00003b00 com.ibm.ws.kernel.feature.internal.FeatureManager E CWWKF0004E: An unknown exception occurred while installing or removing features. Exception: java.lang.IllegalStateException: Method called outside of provisioining operation or without a registered service at com.ibm.ws.kernel.feature.internal.subsystem.SubsystemFeatureDefinitionImpl.getConstituents(SubsystemFeatureDefinitionImpl.java:294) at com.ibm.ws.kernel.feature.internal.FeatureResolverImpl.processSelected(FeatureResolverImpl.java:383) at com.ibm.ws.kernel.feature.internal.FeatureResolverImpl.processRoots(FeatureResolverImpl.java:322) at com.ibm.ws.kernel.feature.internal.FeatureResolverImpl.processCurrentPermutation(FeatureResolverImpl.java:296) at com.ibm.ws.kernel.feature.internal.FeatureResolverImpl.doResolveFeatures(FeatureResolverImpl.java:259) at com.ibm.ws.kernel.feature.internal.FeatureResolverImpl.resolveFeatures(FeatureResolverImpl.java:182) at com.ibm.ws.kernel.feature.internal.FeatureResolverImpl.resolveFeatures(FeatureResolverImpl.java:114) at com.ibm.ws.kernel.feature.internal.FeatureManager.callFeatureResolver(FeatureManager.java:1321) at com.ibm.ws.kernel.feature.internal.FeatureManager.resolveFeatures(FeatureManager.java:1305) at com.ibm.ws.kernel.feature.internal.FeatureManager.updateFeatures(FeatureManager.java:1430) at com.ibm.ws.kernel.feature.internal.FeatureManager.update(FeatureManager.java:777) at com.ibm.ws.kernel.feature.internal.FeatureManager.processFeatureChanges(FeatureManager.java:890) at com.ibm.ws.kernel.feature.internal.FeatureManager$1.run(FeatureManager.java:677) at com.ibm.ws.threading.internal.ExecutorServiceImpl$RunnableWrapper.run(ExecutorServiceImpl.java:280) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.lang.Thread.run(Thread.java:825)[7/2/24 14:11:52:133 UTC] 00003f05 com.ibm.ws.tcpchannel.internal.TCPChannel I CWWKO0220I: TCP Channel defaultHttpEndpoint has stopped listening for requests on host localhost (IPv4: 127.0.0.1) port 9080.[7/2/24 14:11:52:135 UTC] 0000412a com.ibm.ws.tcpchannel.internal.TCPPort I CWWKO0219I: TCP Channel tema-ssl has been started and is now listening for requests on host * (IPv6) port 9081.[7/2/24 14:11:52:206 UTC] 00003b00 com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "java.lang.IllegalStateException: Method called outside of provisioining operation or without a registered service com.ibm.ws.kernel.feature.internal.FeatureManager checkInstallStatus" at ffdc_24.07.02_14.11.52.0.log[7/2/24 14:11:52:208 UTC] 00003b00 com.ibm.ws.kernel.feature.internal.FeatureManager A CWWKF0012I: The server installed the following features: [].[7/2/24 14:11:52:208 UTC] 00003b00 com.ibm.ws.kernel.feature.internal.FeatureManager A CWWKF0008I: Feature update completed in 0.086 seconds.
------------------------------
Stephan Dietl
Original Message:
Sent: Tue July 02, 2024 06:48 AM
From: Andrei Ionescu
Subject: After update ILMT to 9.2.36.0 does not start
Hi Harald,
Yes, the fix is implemented in version 9.2.36.1.
Thank you.
------------------------------
Andrei Ionescu
IBM
Bucharest
Original Message:
Sent: Tue July 02, 2024 06:38 AM
From: Tooling42
Subject: After update ILMT to 9.2.36.0 does not start
Hi Andrei,
is the fix of https://www.ibm.com/support/pages/node/7158851 already implemented in version 9.2.36.1
in LMT-server-9.2.36.1-20240627-1047-windows-x86_64.zip?
Best regards
Harald
------------------------------
Tooling42
Original Message:
Sent: Mon July 01, 2024 09:59 AM
From: Andrei Ionescu
Subject: After update ILMT to 9.2.36.0 does not start
Hello,
Please check if you are affected by the following issue:
https://www.ibm.com/support/pages/node/7158851
Thank you.
------------------------------
Andrei Ionescu
IBM
Bucharest
Original Message:
Sent: Mon July 01, 2024 09:56 AM
From: Igor P. Merkù
Subject: After update ILMT to 9.2.36.0 does not start
Hi, just updated (through BigFix) ILMT to V9.2.36 but unfortunately does not work any more.
When calling the website of ILMT
https://ilmtsrv2.acegas.loc:9081/
an error comes back
Something went wrong.For more information, see the tema.log file.
In tema.log I find some msg, like to following:
[01/07/24 13.39.27:237 UTC] 0000005a com.ibm.ws.webcontainer.webapp I SRVE0292I: Messaggio servlet - [tema]:.DEBUG: due a previous initialization failure application instance can not be returned[01/07/24 13.39.27:237 UTC] 0000005a com.ibm.ws.webcontainer.webapp I SRVE0292I: Messaggio servlet - [tema]:.INFO: resetting rack response due exception: org.jruby.rack.RackInitializationException: uninitialized constant ReportSubscription::User from org/jruby/RubyModule.java:4331:in `const_missing'
Will continue searching, but did anyone encounter this problem and knows how to solve it?
Thanks for your help, Igor
------------------------------
Igor P. Merkù
------------------------------