Hello there,

Please look in the /opt/HP/BSM/log/configserver logs as I think there will be an error message in configserver_all.log. 

You could always install a new GW - same version and hotfix version and then run up the configuratoin wizard.  Once the GW has been configured, start the new GW and see if this helps.

All the best.

Hello Duncan,

We installed a new gateway on a fresh server and the output was the same, services stuck on process oprAS, have you faced any similarities with this error? The longest we've let it run was about 1 hour and a half. Is it possible to take even more than that?

Greetings.

Hello Annam,

Can you please run opr-jmsUtil on the new GW to see if it can connect to the bus:

/opt/HP/BSM/opr/support/opr-jmsUtil.sh

Make sure there is no Firewall blocking things between the DPS and GW.

Are DPS services fully up and running, including the HAC services?

Best regards,

Tobias

Hello Tobias, sorry for the late response,

We had to do a rollback again and this is the new status:

opr-jmsUtil run just fine it shows the bus server (DPS)

DPS services are up (Nanny) meanwhile HAC services show empty.

I tried checking the HAC services on the JMX Hac-Manager using "listAllAssignments" and they're shown running:

Tried removing and re-adding all the services, and re-starting the GW to no avail, oprAS is still hanging and firewall is disabled.

Hello,

Sorry for getting back to you today.  This is a general HAC status for a DPS (there is no WDE), so it's not going to show the status of oprAS on a gateway. 

As mentioned earlier, I think the log files will be most helpful:

/opt/HP/BSM/log/jboss7_boot.log - this is the log file for oprAS starting.

/opt/HP/BSM/log/jboss/*.log - look files ending .log (files ending in .log are the most recent).  Check the log file against a running server and see if they are the same.

/opt/HP/BSM/log/*_boot.log - these are the JVM startup log files.  Check the log file against a running server and see if they are the same.

/opt/HP/BSM/log/configserver/* - look for all recent files.  All the files in this directory are show the GW being configured.  The GW needs to be configured before it can connect to other GWs DPSs.

If the GW is still not starting, please open a service request with Opentext Support.

When you open a service request please upload loggrabbers from all systems as this will save some time.  This is how you do this:

On Linux – run:
/opt/HP/BSM/tools/LogGrabber/saveLogs.sh

available options:
-d,--default grabs files after default number of days
specified in grabber-conf.xml
-g,--grabFilesAfter <arg> grab files after specific date
date format: yyyy-MM-dd
-h,--help display help message
[INFO ] No logs assembled.
[INFO ] LogGrabber finished successfully.
[INFO ] Run time was: 0


# /opt/HP/BSM/tools/LogGrabber/saveLogs.sh
.....................................................................................................
.....................................................................................................

In this case, my server is a single server so the file name is Single_servername_2025.02.28.10.42.27.logs.zip.  The DPS loggrabber starts with "DPS" and GW starts "GW".

# ll Single*
-rw-r--r-- 1 root root 70729570 Feb 28 10:45 Single_servername_2025.02.28.10.42.27.logs.zip

I hope you get this resolved quickly with the help of Opentext Support.

Thanks.

Hi Annam,

For OBM24 there is a HF related to Apache issue. Please check these articles https://docs.microfocus.com/doc/386/24.2/fixedissues https://kmviewer.saas.microfocus.com/#/OCTCR19G2119830 

Info-
OBM 2023.05 Apache creates temporary files, based on the original Apache files with the same name.

After Apache starts and creates these files, Apache changes the permissions of these files to READ only. With Read only access, it fails to over-write them and gets permission denied upon starting OBM. This results in OBM’s gateways unable to start up and stuck at Opr-AS.

Regards,

Harbey Páez

Hello Duncan, sorry for the late reply,

In the end, we did a fresh installation of an OBM Single Server to avoid any possible issues between the DPS and GW,

I did open a support case before posting on this forum, but sadly, we couldn't find the root cause. I'll save your answer for future reference if this ever happens again.

Thank you.

Hi Harbey,

This is an interesting issue, even after we installed the 24.4 version we got the same error and decided to do a fresh reinstall. I'll take a look on the release log of 24.4 and 24.2.

Thank you for your comment.