Environment
Novell Access Manager 3.1 Linux Access Gateway
Situation
Randomly, after upgrading from Access Manager 3.1 SP1 to 3.1 SP2, the SLES 9 based Linux Access Gateway (LAG) might
crash when you apply changes the server. The LAG will often report the 'Server not responding' status within the Admin Console and users cannot access the LAG protected resources for a few seconds (until the services come back up again with the auto restart).
The issue happens because of an open issue in underlying SLES9 OS, which is fixed with SLES11 LAG build.
crash when you apply changes the server. The LAG will often report the 'Server not responding' status within the Admin Console and users cannot access the LAG protected resources for a few seconds (until the services come back up again with the auto restart).
The issue happens because of an open issue in underlying SLES9 OS, which is fixed with SLES11 LAG build.
Resolution
To workaround this issue, download and install the following: patch file from SLES 9 channel:
glibc-2.3.3-98.111.i586.rpm (patch 12527)
For more information on dowloading and updating the patch, see “Installing or Updating the Security Patches on the SLES 9 Linux Access Gateway Appliance†in the Novell Access Manager.
This problem will NOT be an issue with the SLES11 based LAG shipping with 3.1 SP2.
glibc-2.3.3-98.111.i586.rpm (patch 12527)
For more information on dowloading and updating the patch, see “Installing or Updating the Security Patches on the SLES 9 Linux Access Gateway Appliance†in the Novell Access Manager.
This problem will NOT be an issue with the SLES11 based LAG shipping with 3.1 SP2.