Foglight 7.1.0 - Upgrade Guide


	NOTE: When existing installations of 32-bit FglAM instances on 64-bit operating systems are improperly updated to 64-bit installations, this causes the FglAM instances to fail when they are restarted. New 32-bit installations of FglAM 5.8.1 or later are not affected by this issue.

To upgrade an existing 32-bit FglAM installation on a 64-bit operating system:

Shut down the existing FglAM instance.

Install a “new” copy of FglAM, version 5.8.1 or later, on the same system.

Edit the “new” {{state/default/config/fglam.config.xml}} file, and replace the {{<config:id> ... </config:id>}} value with that obtained from the “existing” FglAM installation.

Edit the “new” {{state/default/config/fglam.config.xml}} file, and replace the {{<config:host-display-name> ... </config:host-display-name>}} value with that obtained from the “existing” FglAM installation.

Start the new FglAM installation and deploy to it all cartridges that we deployed to the old FglAM installation.

Agent Manager upgrade issues

Agent Manager upgrades for multiple state instances may fail in certain situations. A detailed description of this issue and a workaround is provided in FglAM vm.config file migration fails under multi-state installations.

Agent Manager upgrades from a 5.5.4.x legacy release require an intermediary upgrade to 5.6.7 prior to upgrading to 5.8.5 or later. To complete this intermediary upgrade, install one or more of the Agent Manager 5.6.7 platform-specific cartridges (as required), and upgrade the legacy hosts to this release before deploying the 7.1.0 Agent Manager cartridge or upgrading the Foglight Management Server to version 7.1.0.

After all of the legacy hosts are running version 5.6.7, and the Foglight Management Server is upgraded to version 7.1.0 or later, you can start upgrading your hosts to version 7.1.0.

You may encounter issues in the following situation when upgrading the Agent Manager: .


	NOTE: If you have previously added certificates to the JRE manually, and are upgrading from a version earlier than 5.6.2.2, see Certificate migration from version 5.6.2.1 or earlier.

FglAM vm.config file migration fails under multi-state installations

Description

When upgrading a multi-state Foglight Agent Managers that share “bin” directories, some of the agent managers become unresponsive as the states are running out of memory. “Out of memory” messages appear in the logs. In addition, error messages like the following appear in the agent manager log:

Foglight_Agent_Manager\state\default\config\client.config does not exist and will not be loaded.

Foglight_Agent_Manager\state\default\config\baseline.jvmargs.config does not exist and will not be loaded.

Workaround:

Locate the client.config and baseline.jvmargs.config files.

Two new files are deployed to the state config directory during a FglAM upgrade. Locate these files (client.config and baseline.jvmargs.config) within the FglAM state instance that was upgraded.

As these file instances may already contain transferred values from the legacy vm.config, you need to review each of the settings in both of these files in order to ensure that these configuration options apply to the FglAM state instance that they are being copied into.

Note that the vm.config settings were migrated.

The legacy vm.config file has be replaced with two new config files. The settings in this file have been split between the new client.config and the baseline.jvmargs.config files.

Migrate the vmparameter.x from vm.config to baseline.jvmargs.config.

Locate the vm.config file within the config state directory instance of FglAM. At the bottom of the file there is a section for defining vmparameter.x = ""; values. Copy over the vmparameter.x settings from the legacy vm.config here into the baseline.jvmargs.config file.

Validate the settings in client.config with vm.config values.

Review all of the options declared in the vm.config with those of the client.config you have copied over. The client.config is a super-set of properties from the vm.config (with the exception that the vmparameter values are no longer defined here). So each property that exists in the vm.config should also exist in the client.config. Ensure that each of the common config values in the client.config file matches the values in the vm.config. If they are different, then update the client.config to match.

Migrate the java.vm config option.

If the java.vm config option was set in the vm.config, then update the java.vm option in the new client.config. When transferring this value over, ensure that the path value is quoted and back-slashes escaped. For example:

Windows:

java.vm = "C:\\shared_java_vms\\1.5\\jre";

Unix:

java.vm = "/opt/shared_java_vms/1.5/jre";

Once migration is complete, and you have validated that all config settings are in their new locations, delete the vm.config file and restart the FglAM process.