32-bit 5.7.x FglAMs on 64-bit hosts won't upgrade to 5.8.x (152033)

32-bit 5.7.x FglAMs on 64-bit hosts won't upgrade to 5.8.x

Error messages like the following are reported in the FglAM log when the upgrade fails:
2015-03-31 15:11:00.894 INFO    [IncomingMessage[6]-39080] com.quest.glue.upgrade.UpgradeImpl - A failure was detected during the upgrade. Rolling back any newly added files.
2015-03-31 15:11:01.082 VERBOSE [IncomingMessage[6]-39080] com.quest.glue.core.GlueUpgradeLock - Releasing the upgrade lock C:\Quest_Software\Foglight_Agent_Manager\upgrade.lock
2015-03-31 15:11:01.082 ERROR   [IncomingMessage[6]-39080] com.quest.common.util15.ConcurrentListenerManager - An unexpected error occurred which may cause undesired behavior. You may want to contact customer support if you see this error again: Listener callback for "com.quest.glue.core.comms.handlers.UpgradeClientHandler" threw exception; ignoring
java.lang.NoClassDefFoundError: com/quest/glue/common/util/ErrorRestartHandler
at com.quest.glue.upgrade.UpgradeImpl.upgrade(UpgradeImpl.java:110)
at com.quest.glue.core.upgrade.Upgrader.executeUpgrade(Upgrader.java:86)

FAM-6226:  FglAM attempts to update 32-bit installs on 64-bit operating systems to 64-bit FglAMs. It should not

If the following line appears in the common\jvminfo.txt file in the FglAM support bundle and the FglAM is not running on AIX or Solaris Sparc then the FglAM is eligible to be upgraded from the JMX console with the steps below.

    sun.arch.data.model=32

Following are the steps to upgrade the FglAM from the JMX console.

1. Get the UUID of the FglAM From the JMX console.
   a).  Log into the JMX console (http:\\vro-shr-fog01.vbms.vba.va.gov:8080\jmx-console ) as the "foglight" user.
   b).  Search for the "service=AgentProtocolHandler" link under the FglAM heading, and click on the link.
   c).  Click the "Invoke" button under the "listConnectedHosts()" method.
   d).  The FglAM UUID is in the second column.  The Host Display Name is in the third column.
   
   Platform :: FglAM UUID :: Host Display Name :: Version :: Build-Id
2. Click the "Back to Mbean View" button.
3. Upgrade the host from the JMX console.
   a).  Find the "upgradeHost()" method.
   b).  Enter the following values in the p1, p2, and p3 fields:
   p1:  The FglAM UUID found in step 1  (FglAM UUID)
   p2:  windows                                     (OS name)
   p3:  ia32                                           (OS Architecture)  *
   
   * The value for the OS Architecture should be ia32 except for Solaris hosts and AIX. For Solaris, use sparc. For AIX you will have to reinstall manually because 32-bit support was dropped for the AIX platform.
   c).  The JMX console will return either "true" or "false" regarding whether the upgrade was successful.  More details on a failure will be available from the FMS and FglAM log files.
   There have been instances reported where the jmx-console returns a false after attempting to upgrade and FglAM but after 5 minutes or so the FglAM is listed as upgraded from the Agent Managers dashboard.
4. Check the Agent Managers dashboard to see if the version listed for the FglAM is 5.8.1.
   
   STATUS:  Fixed in the V5.8.1 FglAM.  The problem won't occur when upgrading a 32-bit V5.8.1 FglAM to a later version.  The problem will occur when attempting to upgrade a lower version of a 32-bit FglAM on a 64-bit host to V5.8.1.
   
   The latest version of the FglAM can be downloaded here.

1. Extract the CAR file from the attached FglAM-Override-DataModel-For-Upgrade-1_0_0.zip.
2. Install FglAM-Override-DataModel-For-Upgrade-1_0_0.car in the Administration | Cartridges | Cartridge Inventory dashboard.
3. Deploy the 'FglAM-Override-DataModel-For-Upgrade-1_0_0' agent package to the desired FglAM client to be upgraded. 
4. Perform the FglAM upgrade.
5. Undeploy 'FglAM-Override-DataModel-For-Upgrade-1_0_0' agent package once the FglAM upgrade is complete.

FAM-6226

FglAM-Override-DataModel-For-Upgrade-1_0_0.car

32-bit FglAMs on 64-bit hosts often have FTR agents running from them because the FTR Agent must run from a 32-bit FglAM.