Access Manager "Server not responding" errors in health check

  • 3692853
  • 02-Jul-2007
  • 26-Apr-2012

Environment



Novell Access Management 3 Linux Novell Identity Server
Novell Access Management 3 SSLVPN Server
Novell Access Management 3 Java Agents
Novell Access Management 3 Linux Access Gateway
Novell Access Management 3 Novell Access Gateway
Access Manager 3 IR2 patch applied
Problem did NOT occur on systems with IR1 patch applied

Situation


On May 1, many customers that had a previously working Access Manager environment reported that the IDP server would not start successfully, that the Linux Access Gateway (LAG) would not service any requests, and that the health check for the LAG would report a""Server is not responding" error in the Service Provider health check.

Looking at the JCC log on the LAG to troubleshoot the "server not responding" error, one could see the following entries:

SEVERE: AM#100707003: No client found with ID idp-esp-F767FB7B1D63C5FE com.novell.jcc.servlet.DispatchServlet A

Resolution

Install Novell Access Manager 3 SP1 Release Candidate 1 which includes the fix for this problem.

In the case you need to make use of the "Novell Access Manager 3 Interim Release 2" build (out of support). Copy the NIDP.JAR file from "ftp.novell.com/outgoing/nidp.jar" to the NIDP server the LAG and NAG servers. After copying the new NIDP.JAR over to the following directories restart the servers.

On the NIDP server:

"/opt/novell/nids/lib/webapp/WEB-INF/lib/nidp.jar"


On the LAG server:

"/opt/novell/nesp/lib/webapp/WEB-INF/lib/nidp.jar"
"/chroot/lag/opt/novell/nesp/lib/webapp/WEB-INF/lib/nidp.jar"


On the NAG server:

"sys:/tomcat/4/webapps/nesp/WEB-INF/lib/nidp.jar"
  1. setup the miniftp server on the NAG from within the "Novell Access Gateway Console"
    using the command: "set miniftpserver address = x.x.x.x"

  2. use either bash or toolbox on the NAG to copy the NIDP.JAR
    from:"sys:/etc/proxy/appliance/config/user"
    to:"sys:/tomcat/4/webapps/nesp/WEB-INF/lib/nidp.jar"