-> [80] Jan 19, 2024 12:37:51.310 AM org.forgerock.openidm.health.HealthService$4 run SEVERE: OpenIDM failure during startup, ACTIVE_NOT_READY: Not all modules started [] [org.apache.felix.scr, org.forgerock.openidm.repo-opendj] []

[edward.johnson]

Hello,

I’ve been researching this issue further and I found a support ticket where this issue was resolved after increasing the servicestartmax timeout from 45 to 60 seconds. Can you try on your end?
openidm.healthservice.servicestartmax=60000 or 120000.

It is also possible that you might have an issue with the repo.ds.json file from your …/openidm/conf directory or this file may be in a corrupted state.
Please review and verify your repository configuration was performed per the IDM Install Guide: Select a repository :: IDM 7.4.1

Also as a reference, I’ve included this IDM Performance article located in the Community Site. (Please review Step 6:Repository)

Getting the Most Performance From Your IDM Deployment

IDM is a highly configurable product, capable of solving a large number of provisioning-related business problems. There are features available to store arbitrary data structures, sync with external systems, validate data, track usage, gather data directly from users, and more. As with anything, however, features come with a cost. Having things enabled that you don't really need will slow your system down. For that reason, it's important to review your IDM configuration to make sure that you ha…

If the issue continues after testing and reviewing as suggested above please let us know the following:

1. Is your new IDM instance being installed as an upgrade? If so, what is the old version you are upgrading from?
2. What type of repository is in use?

Warm Regards,
Ed