Access Gateway fails to start after upgrade to NAM 4.2

  • 7017006
  • 19-Nov-2015
  • 02-Dec-2015

Environment

NetIQ Access Manager 4.2
Upgrade from NAM 4.1

Situation

Administrator upgraded the Admin Console and Identity servers from 4.1 to 4.2, and users could access the Access Gateway protected resources successfully after authentication. The final part of the upgrade was the Access Gateways - running the upgrade script appeared to go fine with no visible errors on the server console. After the upgrade, no users could access the Access Gateway, getting connection level errors on the browser.

Looking at the rcnovell-apache2 status output showed that the Apache proxy had not started. The AG healthcheck reported the server as down, but also showed the following errors (also visible in the /var/opt/novell/nam/logs/mag/apache2/rcnovell-apache2.out file)

httpd: Syntax error on line 495 of /etc/opt/novell/apache2/conf/httpd.conf: Syntax error on line 14 of /etc/opt/novell/ag/ag_hook.conf: Cannot load /usr/lib64/liblog4cxx.so.10 into server: /usr/lib64/liblog4cxx.so.10: undefined symbol: SAL_LMutexRelease

Resolution

Verify that libsal library is loaded correctly in the /etc/opt/novell/ag/ag_hook.conf as shown below:

LoadFile /usr/lib64/libsal.so
LoadFile /usr/lib64/liblog4cxx.so.10

For some reason, the AG did not have the libsal.so file loaded after the upgrade.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.