OKM - KMA Fails To Start Services After Unexpected Reboot
(Doc ID 2808371.1)
Last updated on JULY 11, 2022
Applies to:
Oracle Key Manager - Version 3.1 to 3.3 [Release 3.0]Information in this document applies to any platform.
Symptoms
KMA fails to start services after unexpected reboot. ELOM showed all healthy as well as no service lights on KMA.
A follow-up reboot of the KMA was successful.
The messages file log shows:
SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
EVENT-TIME: Wed Aug 25 20:11:34 UTC 2021
PLATFORM: ORCL,Netra-SPARC-T4-1, CSN: AK00315544, HOSTNAME: kma2
SOURCE: software-diagnosis, REV: 0.1
EVENT-ID: 661ec284-5ded-4732-8857-e6bb488d2b04
DESC: A service failed - a start, stop or refresh method failed.
AUTO-RESPONSE: The service has been placed into the maintenance state.
IMPACT: svc:/ldoms/ldmd:default is unavailable.
REC-ACTION: Run 'svcs -xv svc:/ldoms/ldmd:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted. Please refer to the associated reference document at http://support.oracle.com/msg/SMF-8000-YX for the latest service procedures and policies regarding this diagnosis.
The KMA is a T4-1 server running OKM 3.3
Changes
No known change
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |