Environment
NetIQ Access Manager 4.3
RedHat 7.3
systemd
Situation
Nam Identity Server (IDP was working fine, but customer had scheduled a restart. After the restart could not login to IDP.
Looking at Admin Console (AC) the IDP showed it was in a halt state in the health.
Checking status of novell-jcc service we see:
# rcnovell-jcc status
Checking for service Novell Access Manager Server Communications
JCCServer is stopped
Manually starting novell-jcc service resolves the issue:
rcnovell-jcc start
The problem is the need to have novel-jcc start automatically without manually restarting after a reboot.
The novell-idp and novell-jcc services are not starting up correctly after a reboot
Resolution
Reported to engineering to address in the code in future release. (As of time of this writing current code is NAM 4.3.2 and not fixed yet)
In the interim, manually make the following change:
Add: "After=network.target local-fs.target " to /etc/systemd/system/novell-jcc.service
Original:
-------------------------------------------------------------------------
[Unit]
Description=Novell jcc
[Service]
Type=oneshot
ExecStart=/etc/init.d/novell-jcc start
ExecStop=/etc/init.d/novell-jcc stop
RemainAfterExit=yes
Modified:
-------------------------------------------------------------------------
[Unit]
Description=Novell jcc
#To address service not restarting after reboot: Bug 1048394
After=network.target local-fs.target
[Service]
Type=oneshot
ExecStart=/etc/init.d/novell-jcc start
ExecStop=/etc/init.d/novell-jcc stop
RemainAfterExit=yes
===============================================
This can also be a problem on Access Gateway Service.
Perform the same change on Access Gateways.
Cause
novell-jcc service tried to start before networking was available.
Additional Information
May want to make this same change on other novell-*.services that are present under /etc/systemd/system/* although my testing seems to indicate only novell-jcc has been an issue.
As an example: novell-idp.service, novell-mag.service etc.