Identity Manager OSP service fails to start.

  • Document ID:7024836
  • Creation Date:22-Sep-2020
  • Modified Date:22-Sep-2020
    • Micro Focus Products:
      Identity Manager
      Identity Manager Roles Based Provisioning Module

Environment

Identity Manager 4.7
Identity Applications 4.7

Situation

Access to the IDM User Application was failing with the browser error

{"Fault":{"Code":{"Value":"Sender","Subcode":{"Value":"XDAS_OUT_ENTITY_NON_EXISTANT"}},"Reason":{"Text":"Main Not found."}}}

Checking the tomcat log at /opt/netiq/idm/apps/tomcat/logs/catalina.out showed no connection and no unexpected error.
However, the osp log at /opt/netiq/idm/tomcat/logs/osp-idm.<todaysdate>.log had the error.

Preamble: [OSP]
Priority Level: SEVERE
Java: internal.osp.framework.OSPTenant.startService() [1212] thread=localhost-startStop-1
Time: 2020-09-21T13:05:33.057+1000
Log Data: Error starting service: auth
java.lang.NullPointerException
internal.osp.common.imagepool.ImagePool: ImagePool.java: sync: 530
internal.osp.common.imagepool.ImagePool: ImagePool.java: remove: 184
internal.osp.framework.image.OSPImagePool: OSPImagePool.java: add: 196
internal.osp.oidp.service.configuration.ConfigurationManager: ConfigurationManager.java: loadImagePool: 1,659
internal.osp.oidp.service.configuration.ConfigurationManager: ConfigurationManager.java: initialize: 365
internal.osp.oidp.service.NIDPAuthenticationFederationService: NIDPAuthenticationFederationService.java: initialize: 152
internal.osp.oidp.service.NIDPAuthenticationService: NIDPAuthenticationService.java: handleStart: 417
internal.osp.framework.OSPService: OSPService.java: start: 121
internal.osp.framework.OSPTenant: OSPTenant.java: startService: 1,195
internal.osp.framework.OSPTenant: OSPTenant.java: startTenant: 606
internal.osp.framework.OSPContext: OSPContext.java: start: 1,021
internal.osp.framework.OSPContext: OSPContext.java: start: 847
internal.osp.framework.OSPContext: OSPContext.java: set: 568
internal.osp.framework.servlet.OSPServletContext: OSPServletContext.java: <init>: 117
internal.osp.framework.servlet.OSPContextListener: OSPContextListener.java: getContext: 72
internal.osp.framework.servlet.OSPContextListener: OSPContextListener.java: contextInitialized: 114
org.apache.catalina.core.StandardContext: StandardContext.java: listenerStart: 4,770
org.apache.catalina.core.StandardContext: StandardContext.java: startInternal: 5,236
org.apache.catalina.util.LifecycleBase: LifecycleBase.java: start: 150
org.apache.catalina.core.ContainerBase: ContainerBase.java: addChildInternal: 754
org.apache.catalina.core.ContainerBase: ContainerBase.java: addChild: 730
org.apache.catalina.core.StandardHost: StandardHost.java: addChild: 734
org.apache.catalina.startup.HostConfig: HostConfig.java: deployWAR: 980
org.apache.catalina.startup.HostConfig$DeployWar: HostConfig.java: run: 1,851
java.util.concurrent.Executors$RunnableAdapter: Executors.java: call: 511
java.util.concurrent.FutureTask: FutureTask.java: run: 266
java.util.concurrent.ThreadPoolExecutor: ThreadPoolExecutor.java: runWorker: 1,149
java.util.concurrent.ThreadPoolExecutor$Worker: ThreadPoolExecutor.java: run: 624
java.lang.Thread: Thread.java: run: 748

Resolution

Logging for the osp log was increased by modifying
/opt/netiq/idm/apps/tomcat/bin/setenv.sh
changing the property -Dcom.netiq.idm.osp.logging.level=ALL
and restarting the netiq-tomcat.service.

This more detailed log revealed no other issues. Everything before the nullpointer exception was fine and no issues could be found with the configuration.

Suspecting some sort of corruption, it was decided to force a redeploy of the OSP application.
  •   systemctl stop netiq.tomcat.service
  •   delete the /opt/netiq/idm/apps/tomcat/webapps/osp folder
  •   delete the /opt/netiq/idm/apps/tomcat/temp/permindex folder
  •   delete the /opt/netiq/idm/apps/tomcat/work/catalina folder
  •   systemctl start netiq.tomcat.service
The OSP application then started without error and there were no further issues.



Cause

We suspect there was a corruption in the OSP web archive deployment folder.