Lag upgrade to Access Manager 3.1 SP3 failed

  • 7008203
  • 25-Mar-2011
  • 26-Apr-2012

Environment

Novell Access Manager 3.1 Linux Access Gateway
Novell Access Management 3.1 Support Pack 2 IR3A applied

Situation

The upgrade from IR3A to SP3 for the admin console and the IDP component worked fine.
When the LAG was upgraded it ended with a failure and the LAG components didn't come up anymore.

Following was seen in the ics_dyn:
 
vxe-UTIL: init.
MAIN: Loaded /opt/novell/lib/vxe-util.so.1 at 0x9c7b1000
MAIN: Loaded /opt/novell/lib/nwutil.so.1 at 0xb5efb000
** vxe evtinfraStart **
** vxe evtinfraStart succeeded **
MAIN: Loaded /opt/novell/lib/evtinfra.so.1 at 0xb5ef7000
MAIN: Loaded /opt/novell/lib/prxcfg.so.1 at 0xb5ef3000
MAIN: Cannot load /opt/novell/lib/proxy.so.1
MAIN: Error: volcomm.so.1: cannot open shared object file: No such file or directory
MAIN: Cannot load /opt/novell/lib/datastream.so.1
MAIN: Error: volcomm.so.1: cannot open shared object file: No such file or directory
MAIN: Cannot load /opt/novell/lib/vcpcnmgr.so.1
MAIN: Error: volcomm.so.1: cannot open shared object file: No such file or directory
MAIN: Cannot load /opt/novell/lib/authorization.so.1
MAIN: Error: volcomm.so.1: cannot open shared object file: No such file or directory
MAIN: Cannot load /opt/novell/lib/idinjection.so.1
MAIN: Error: volcomm.so.1: cannot open shared object file: No such file or directory
MAIN: Loaded /opt/novell/lib/protsearch.so.1 at 0xb5eee000
MAIN: Cannot load /opt/novell/lib/pgzip.so.1

Resolution

The libvcpsvmgr.so.1 that was present on the LAG box in the /chroot/lag/opt/novell/lib directory was different then the one that shipped originally with the IR3A upgrade.
By moving and renaming the module libvcpsvmgr.so.1 that was on the box and the replacement with the  original one that comes with SP2IRA patch the upgrade went fine.

Additional Information

Reported to engineering.
This was a very specific case where the original module was replaced by a different module because of an applied engineering build.
When exact same is seen in the ics_dyn and upgrade scenario was from SP2IR3A to SP3 the mentioned steps under resolution can be used to fix the issue.