-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: OpenIDM 2.1.0
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:Sprint 31
Two issues found:
1- OpenIDM failure during startup as reported in the server.log (see below). What is the root cause of the failure?
2- False status reporting of OpenIDM. The failure is reported at 6:28:26 AM in the server.log file. At 06:28:49, we checked the status of OpenIDM, it showed as running and state as "ACTIVE_READY". Refer to install_openidm.log.
Server.log
OpenIDM version "2.1.0" (revision: 1952)
Nov 20, 2014 6:28:26 AM org.forgerock.openidm.info.impl.HealthService$4 run
SEVERE: OpenIDM failure during startup, ACTIVE_NOT_READY: Required services not all started [org.forgerock.openidm.scheduler]
OpenIDM failure during startup, ACTIVE_NOT_READY: Required services not all started [org.forgerock.openidm.scheduler]
OpenIDM ready
Install_openidm.log. It shows that the server started properly:
2014-11-20:06:28:07+00:00: INFO: Starting OpenIDM...
2014-11-20:06:28:18+00:00: openidm (pid 23420) is running...
2014-11-20:06:28:49+00:00:
2014-11-20:06:28:49+00:00: INFO: OpenIDM started successfully
OpenDJ access log was checked around that time. OpenDJ was up and running and responding to requests.