Error trying to start omniEvents.service during REDHAWK 3.0.0 install

Question

Going through the Redhawk 3.0.0 installation steps involving omniORB (manual), I'm seeing an error when trying to start the omniEvents service. Specifically:

Job for omniEvents.service failed because the control process exited with error code. 
See "systemctl status omniEvents.service" and "journalctl -xe" for details.

The results of systemctl status omniEvents.service is:

● omniEvents.service - OmniEvents Service
   Loaded: loaded (/usr/lib/systemd/system/omniEvents.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2022-04-14 15:24:02 EDT; 40s ago
  Process: 58373 ExecStartPre=/bin/bash -c i=20; while ((i-- > 0)) && ! nameclt list > /dev/null 2>&1; do sleep 0.25; done; nameclt list > /dev/null 2>&1 (code=exited, status=1/FAILURE)
  Process: 58370 ExecStartPre=/bin/chown -R omniORB $LOGDIR (code=exited, status=0/SUCCESS)
  Process: 58367 ExecStartPre=/bin/mkdir -p $LOGDIR (code=exited, status=0/SUCCESS)

Apr 14 15:23:57 d6rs-wsredhk-mc.metron.local systemd[1]: Starting OmniEvents Service...
Apr 14 15:24:02 d6rs-wsredhk-mc.metron.local systemd[1]: omniEvents.service: control process exited, code=exited status=1
Apr 14 15:24:02 d6rs-wsredhk-mc.metron.local systemd[1]: Failed to start OmniEvents Service.
Apr 14 15:24:02 d6rs-wsredhk-mc.metron.local systemd[1]: Unit omniEvents.service entered failed state.
Apr 14 15:24:02 d6rs-wsredhk-mc.metron.local systemd[1]: omniEvents.service failed.

and the results of journalctl -xe contain

-- Unit omniEvents.service has begun starting up.
Apr 14 15:32:03 <my_hostname> systemd[1]: omniEvents.service: control process exited, code=exited status=1
Apr 14 15:32:03 <my_hostname> systemd[1]: Failed to start OmniEvents Service.
-- Subject: Unit omniEvents.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Has anyone resolved this issue during their own installation?