Upgraded from SOI to CU4/CU5 and CA SOI Store Indexer service is not going up. Checking the SAM_Store_Indexer.log the error I see is the following:
INFO | jvm 1 | 2023/01/02 11:25:00 | Initializing JsafeJCE version 5.0
INFO | jvm 1 | 2023/01/02 11:25:00 | Exception in FakeX509TrustManager:com.rsa.cryptoj.f.vq: Could not perform unpadding: invalid pad byte.
INFO | jvm 1 | 2023/01/02 11:25:00 | Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@x: defining beans [persistenceSetting,persistenceFactory,solrSetting,bossFetcher,searchEngineIndexer,indexer,jobForIndexer,trigger,org.springframework.scheduling.quartz.SchedulerFactoryBean#0]; root of factory hierarchy
INFO | jvm 1 | 2023/01/02 11:25:00 | WrapperSimpleApp:
INFO | jvm 1 | 2023/01/02 11:25:00 | WrapperSimpleApp Error: Encountered an error running main:
INFO | jvm 1 | 2023/01/02 11:25:00 | WrapperSimpleApp Error: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobForIndexer' defined in class path resource [indexerContext.xml]: Invocation of init method failed; nested exception is java.lang.InstantiationError: org.quartz.JobDetail
...
INFO | jvm 1 | 2023/01/02 11:25:00 | WrapperSimpleApp Error: Caused by: java.lang.InstantiationError: org.quartz.JobDetail
...
INFO | jvm 1 | 2023/01/02 11:25:00 | WrapperManager Debug: Pausing for 1.000ms to allow a clean shutdown...
INFO | jvm 1 | 2023/01/02 11:25:00 | WrapperManager Debug: Stopped checking for control events.
DEBUG | wrapperp | 2023/01/02 11:25:00 | read a packet STOP : 1
DEBUG | wrapper | 2023/01/02 11:25:00 | JVM requested a shutdown. (1)
DEBUG | wrapper | 2023/01/02 11:25:00 | wrapperStopProcess(1, FALSE) called.
Release : 4.2
The engineering team has provided a fix attached to the KB
1. Stop SOI Services
2. Move the below files/folders to a backup location:
a. On UI Server machines
<SOI Install Folder>\indexer\sor.indexer.jar
3. Copy the new files from the extracted zip file as below:
a. On UI Server machines
<SOI Install Folder>\indexer\sor.indexer.jar
4. Start SOI Services
5. Verify the issue once the Services are up and running
in some cases, the CU4/CU5 upgrade didn't clean up the old libraries under <SOI Install directory>\indexer\lib
the total number of jar files in CU4 should be 171
the total number of jar files in CU5 should be 172
The engineering team has provided the attached file (cleanupPreCU4IndexerFiles) to remove the old libraries and resolve the issue.
- open the command line and go to the \CA\SOI\indexer\lib
- then copy/paste the script (attached to the KB).
- restart the indexer service and let me know the results.