Sun Opensso Server Failed To Restart After Server Reboot when using a remote config store (Doc ID 1426069.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle OpenSSO - Version 8.0 and later
Information in this document applies to any platform.
The customer is running OpenSSO 8 U2, on Linux with a NAS. All the config store data is on the NAS and Sun OpenSSO
is reading/writing from the NAS. Merck is an issue when the server (Linux in our case) is rebooted without bring down opensso.

Problem is that when the linux server is rebooted (without bring down OpenSSO), Federation/OpenSSO is not coming up after the
server reboot. It seems like because it wasn’t cleanly shutdown that some lock files and/or left files in an unstable state. There is a way
to work around this by copying the config store/OpenSSO directories on the NAS.

Here's the issue:

Per the docs: http://docs.oracle.com/cd/E19681-01/820-3320/gfsfq/index.html

The OpenSSO configuration data store must be deployed on a local file system. It is not supported on an NFS-mounted file system.
There still is a way to address this.


Symptoms



All the config store data is on  the NAS (NFS mount)  and Sun OpenSSO is reading/writing from
the NAS. The customer has  an issue when the server (Linux in our case) is rebooted without bring
down opensso.

Problem is that when the linux server is rebooted (without bring down OpenSSO),
Federation/OpenSSO is not coming up after the server reboot.  It seems like because it wasn’t
cleanly shutdown that some lock files and/or left files in an unstable state. There is a way
to work around this by copying the config store/OpenSSO directories on the NAS.

Here's the issue:

Per the docs: http://docs.oracle.com/cd/E19681-01/820-3320/gfsfq/index.html

The OpenSSO configuration data store must be deployed on a local file system. It is not supported on an NFS-mounted file system.

Changes

The customer should be able to recover from this issue by removing the lock files
   Assuming their path is the same as it is in the documented path:
rm  /nas/exception-dmz/pr/writeable/federation.companyvip.com/config/opends/lock/*
rm /nas/exception-dmz/pr/writeable/federation.companyvip.com/config/opends/db/userRoot/je.lck

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms