404 Not found error received in Operations Bridge Manager (OBM) after login

  • Document ID:KM03632813
  • Creation Date:07-Apr-2020
  • Modified Date:07-Apr-2020
    • Micro Focus Products:
      operations bridge manager 2019.05

Summary

Right after adding the credentials to login OBM UI a 404 Not Found error is displayed, none of the OBM pages is accesible.

Error

404 Not found error:

image text

 

Errors in opr-webapp.log of the Gateway server, erros about Identification map is larger than te fuse and a lot of  CIs of type HP Operations Manager System reffering to the same OBM FQDN:

Error while trying to [addOrUpdate] on level [1]! Error appending ID 44d43b7d86dec77a9a231e7c8f44dfcc to identification map. Total size of map is larger than the limit 4000000 which defined in reconciliation.identification.map.fuse : operation DataInAddOrUpdateData

...

Caused by: com.hp.ucmdb.reconciliation.data.IdentificationMapTotalSizeException: [ErrorCode [63010] Identification map total size is larger than the defined fuse.{4000000}]

Can't append to identification map entry because size of the map is larger than the limit 4000000
Id to which attempting to append: 44d43b7d86dec77a9a231e7c8f44dfcc
Data attempting to append [2400] :
{operations_manager_system@4acedafbdfd2142b83407aec4fc43da4}@[(string-user_label:OBM_FQDN), (string-name:OBM_FQDN), (string-TenantOwner:System Default Tenant), (string-global_id:[Empty CMDB property value]), (string_list-TenantsUses:[System Default Tenant])]
{operations_manager_system@47d7f80653069725b8135d4b28fd4656}@[(string-user_label:OBM_FQDN), (string-name:OBM_FQDN), (string-TenantOwner:System Default Tenant), (string-global_id:[Empty CMDB property value]), (string_list-TenantsUses:[System Default Tenant])]
{operations_manager_system@42f6d415fec88fd4a4edba71dae5d383}@[(string-user_label:OBM_FQDN), (string-name:OBM_FQDN), (string-TenantOwner:System Default Tenant), (string-global_id:[Empty CMDB property value]), (string_list-TenantsUses:[System Default Tenant])]
 
 

Cause

This happens because there are a lot of CIs of type HP Operations Manager System reffering to the same OBM FQDN but with different IDs, there should be just one for the OBM server and others if there is an Integration with an OMU, OMW or other OBM server but not hundreds or thousands of it.

Having that big amount of CIs causes the jboss to not start properly, opr-web component doesn't start, in jboss7_boot.log this error appears:

INFO - Initializing Mojarra 2.1.28.SP11 for context '/opr-web'
[org.apache.catalina.core] (ServerService Thread Pool -- 47) ERROR - JBWEB001103: Error detected during context /opr-web start, will stop it
[org.jboss.msc.service.fail] (ServerService Thread Pool -- 47) ERROR - MSC000001: Failed to start service jboss.web.deployment.default-host./opr-web: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./opr-web: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
 
Also, when running opr-checker -opr shows that opr-web deployment failed:
 
-- Check_2_-_JBoss_Deployment ---
 
  Result_of_deployment_check_for_opr-web.war_is: FAILED

 

Fix

To check if this is the issue:

  • Access UCMDB/RTSM UI (should be able to connect directly to UCMDB on port 8443 even if JBoss is not up): https://OBM_FQDN:8443
  • Go to CI Type Manager
  • Select the CI type HP Operations Manager system and that should already show the count.

If the count is high (hundreds or thousands), delete the ones that do NOT have a connection to operations agent CI(s):

  • Go to Modeling Studio

  • Create a new Query

  • Add CI type HP Operations Agent and HP Operations Manager System, then create a Membership relationship:

    image text
  • Need to identify the HP Operations Manager System CIs that don't have the relationship so select the HP Operations Manager system of the query, then select the Cardinality tab and click Edit.

    Select Min:0 Max:0

    That should show hundreds ot thousands CIs that need to be deleted.

*Note: It could be that all CIs has a relationship with Operations Agents so the way to proceed is go to the CI Type Manager, right click over  CI type HP Operations Manager system and select Show CI Instances, that would list all the CIs. Select and delete all CIs but one, so there is just one CI for OBM.

Then restart OBM services, after the restart UI should work properly.