Sometimes, the Webui is stuck after Elements Management System is deployed. This article explains how to fix such issues. Please tail the below log file to understand the status of the deployment

 tail -f /tmp/systemStartup.log:

2024/11/19 02:48:43.419 Network Management Platform is now deploying ... [ 1 of 9 ]

2024/11/19 02:48:43.972 Network Management Platform Creating database table views

2024/11/19 02:48:44.622 Network Management Platform Creating database table index

2024/11/19 02:49:35.336 Network Management Platform Checking and performing database migration, this may take few minutes

2024/11/19 02:50:45.480 Network Management Platform loading device schema

2024/11/19 02:53:46.873 Network Management Platform

2024/11/19 02:53:59.690 Elements Management System is now deploying ... [ 2 of 9 ]

2024/11/19 02:54:13.580 Elements Management System

As per the above output, it is not moving forward after Elements Management System deployed

When we check the ear packages that need to be deployed under /usr/local/jboss/domain/configuration/domain.xml, it shows only cmp.ear and cems.ear packages in socket-binding-groups and server-groups

</socket-binding-groups>

 <deployments>

    <deployment name="cems.ear" runtime-name="cems.ear">

      <content sha1="bb60f7f10716c519c45e42fe0c4ea70c68f72600"/>

    </deployment>

    <deployment name="cmp.ear" runtime-name="cmp.ear">

      <content sha1="4272d369cb2cc46c37136650290defe192fddafa"/>

    </deployment>

  <server-groups>

    <server-group name="application" profile="full-ha">

      <socket-binding-group ref="full-ha-sockets"/>

    </server-group>

    <server-group name="platform" profile="full-ha">

      <socket-binding-group ref="full-ha-sockets"/>

      <deployments>

        <deployment name="cems.ear" runtime-name="cems.ear"/>

        <deployment name="cmp.ear" runtime-name="cmp.ear"/>

Please run the below command to get the sha1sum of each ear package:

 find /usr/local/jboss/standalone/deployments -name "*ear" | xargs sha1sum

4272d369cb2cc46c37136650290defe192fddafa /usr/local/jboss/standalone/deployments/00/cmp.ear

bb60f7f10716c519c45e42fe0c4ea70c68f72600 /usr/local/jboss/standalone/deployments/01/cems.ear

a445e9a35458d39f50a2b20e2586f2b5dedb1ab3 /usr/local/jboss/standalone/deployments/021/opennms.ear

de66398e4037120a967e716e45d6782ed1cae8ba /usr/local/jboss/standalone/deployments/999/appmgt.ear

To fix the issue, please follow the below steps:

• Stop the the below services

systemctl stop jmp-watchdog jboss jboss-dc

• Please add the remaining ear package name and respective sha1sum value to the socket-binding-groups and ear package name to the server-groups

Same format as mentioned above:

</socket-binding-groups>

 <deployments>

    <deployment name="cems.ear" runtime-name="cems.ear">

      <content sha1="bb60f7f10716c519c45e42fe0c4ea70c68f72600"/>

    </deployment>

    <deployment name="cmp.ear" runtime-name="cmp.ear">

      <content sha1="4272d369cb2cc46c37136650290defe192fddafa"/>

    </deployment>

• Start the services back using the below command:

systemctl start jmp-watchdog

Note: If it is a multinode deployment, please follow the same steps on all Jboss nodes