The following is a list of issues addressed and enhancements implemented in this Foglight Agent Manager release.
Defect ID |
Resolved Issue |
FAM-7254 | Agent in ext FglAM did not collect data without any error logs after the Agent Manager started for a few hours. |
FAM-7241 | "Too many open files" error was reported by many FglAMs running on Solaris. |
FAM-7239 | Fixed issue where FglAM picked up IPv6 address as the host name. |
FAM-7214 | Fixed issue where some FglAM commands caused FglAM crash. |
FAM-7207 | The Agent Manager dashboard loads slowly when loading more than 800 FglAMs. |
FAM-7177 | Unexpected NullPointerException results in broken agents. |
FAM-7175 | Fixed issue where some FglAMs incorrectly shown as not upgradable. |
FAM-7173 | Supported "diffie-hellman-group-exchange-sha256" in SSH connection. |
FAM-7145 | Support more MAC algorithms, including hmac-sha2-512, hmac-sha2-256, and hmac-ripemd160. |
FAM-7134 | Inconsistent agentPackage version results in broken peers. |
FAM-7086 | Output of "fglam --status" does not match what is documented. |
FAM-7079 | Fixed issue where the file log scanner stopped scanning logs. |
FAM-6996 | Fixed the "Too many open files" error occurred when stopping and starting data collection for the JMX agent. |
FAM-6977 |
System Lockbox failure may happen when moving agents. |
FAM-6968 |
Foglight Agent Manager generated a NumberFormatException exception while executing activity of WindowsEventLog. |
FAM-6930 | Fixed issue where the Agent Manager encounters a "Permission denied" error when user attempts to upgrade the jre file. |
The following is a list of issues known to exist at the time of this release.
Defect ID |
Known Issue |
FAM-7210 | The Agent Manager version number is incorrect on the Script Console dashboard, after being upgraded to 5.8.5.5.2 from 5.8.5.5.1. |
FAM-7209 | FglAM-Adapter-Devkit-6.1.3 is missing after the Agent Manager is upgraded from 5.8.5.4.1 to 5.8.5.4.2. |
FAM-7193 | FglAM running on Linux/Solaris fails to connect to the target host through link-local IPv6 WMI, if multiple network interfaces exist in the target host. Workaround: 1. Log into the target host. 2. Execute the dos command->ipconfig/all command, to check how many tunnel interfaces which contain IPv6 address. 3. If only Tunnel adapter Teredo Tunneling Pseudo-Interface and Ethernet adapter Local Area Connection exist in the target host, uninstall/disable Teredo Tunneling Pseudo-Interface, and then check if the WMI connection can be established. |
FAM-7183 | Adapter should alert upon FglAM failover and when cluster members are in the BROKEN state. |
FAM-7169 | WinRMCommandShell returns empty output when using BAT scripts. |
FAM-7116 | WMI connection cannot be established successfully when using the IPv6 address to monitor the target host. Workaround: 1. Set the agent's target host address and credential resource mapping to the long form, for example: fc00:0:0:0:0:0:a1e:9804. 2. Check if the WMI connection can be established. If not, change the agent's target host address from long form to compressed form (fc00::a1e:9804). If this solution still does not work, check the workaround in FAM-7193. |
FAM-7072 | Installer fails to exit and FglAM cannot report to FMS. |
FAM-7023 | Agents will be broken (FMS deletes them), after changing FglAM host name, IP, or display name. The agents will be recreated when the FglAM starts with the original FglAM display name. |
FAM-6998 |
Cannot deploy multiple HA-aware gars to a standby host at one time.
|
FAM-6942 | HA failover fails and the value of mState on standby peers changes to MISSING_LOCKBOX in JMX console. Workaround: If the failure of HA failover is caused by MISSING_LOCKBOX (Check the HA partitions info by navigating to JMX console > HAManager > diagnosticSnapshotAsString()), perform either of the following options to resolve this issue: 1. On the navigation panel, under Dashboards, click Administration > Credentials > Manage Lockboxes. In the Manage Lockboxes dashboard, release the missed lockboxes to the MISSING_LOCKBOX FglAM client. If you cannot find the missed lockboxes, perform step 2. 2. On the FglAM client that has the MISSING_LOCKBOX status, navigate to <fglam_home>\state\<state_name>\credentials. Clean up all files under this directory, and then restart the FglAM. After the restart completes, release all lockboxes as Primary in the Administration > Credentials > Manage Lockboxes dashboard. |
FAM-6940 | There are duplicate IP addresses for different FglAM instances (running on Linux) in the Agent Managers dashboard, if the FglAM servers are cloned virtual machines. Workaround 1:
Workaround 3: If you have cloned the servers, do not start up the FglAM. Set system.id.enabled = false for all FglAM instances in the <fglam_home>/state/<state_name>/config/client.config file, and then start the FglAM for the first time. |
FAM-6934 |
Agent is not listed under "agents" property of FglAMClientInstance or Host object after moved. |
FAM-6838 |
The Agent Manager fails to connect to the Management Server while using the default HTTPS SSL certificate. Workaround: Install a newer certificate on the Management Server. |
FAM-6688 | Support is required for installing and running Agent Manager on a system with SELinux enabled. |
FAM-6439 |
Upgrades from 5.7.4 to 5.8.1 or 5.8.2 may result in an error during the upgrade process. Workaround: If you are currently running a 5.7.4 install and you want to upgrade, then you must upgrade to version 5.8.5 or later. |
FAM-6228 |
The Agent Manager fails to start up after an upgrade. |
FAM-5854 |
Foglight Log Monitor does not support UNC (Universal Naming Convention) paths. Workaround: The following workaround applies when monitoring local log files. Monitoring remote log files is not supported.
|
FAM-5832 |
Installing and configuring multiple Foglight Agent Manager instances on a single physical host can cause some topology churn in the Host model representing the Agent Manager. Workaround: By default, the Agent Manager submits performance metrics about itself. If multiple Agent Manager instances are running on the same physical host, disable the performance monitoring self-metric submission for each Agent Manager Instance by completing the following steps:
Additionally, an Agent that submits a Host object representing the monitoring host (for example, an Agent Manager instance that is running and hosting an agent instance) as part of its monitored collection causes a Host topology churn when these agent types are deployed to additional Agent Manager instances running on the same physical host. |
FAM-5600 |
The Agent Manager vm.config file migration fails under multi-state installs. Workaround: The legacy vm.config file is replaced with two new configuration files: client.config and baseline.jvmargs.config. Locate these files within the upgraded Agent Manager state instance. As these file instances may already contain transferred values from the legacy vm.config, review each of the settings in both of these files in order to ensure that these configuration options apply to the Agent Manager state instance that they are being copied into.
|
FAM-5355 |
OutOfMemoryError: The Agent Manager cannot create new native thread. It shuts down when the open file descriptor limit is too low. |
FAM-5264 |
The Agent Manager running on Solaris may fail to run local or external commands during startup or through the SSHLocalConnectionImpl class. |
FAM-4955 |
Parentheses can cause a command execution to fail while using a LocalWindowsCommandShell connection. Workaround: If parentheses are used for grouping commands (and not in an echo context), use spaces to separate them from the other tokens in the command. For example, instead of this command: if 3 gtr 2 (echo "3>2") else (echo "3 leq 2") Use the following: if 3 gtr 2 ( echo "3>2" ) else ( echo "3 leq 2" ) |
FAM-2850 |
Slave processes exist for all installed out-of-process (OOP) agent packages, even if no agent instances are running. Workaround: OOP packages which are not running any agent instances may be un-deployed from the Agent Manager. Currently, this is only possible using a manual procedure. |
FAM-1972 |
The deployed agent scratch directory created for JFogbank-type agents is not deleted during an upgrade. Workaround: The orphaned directory is benign, and can be manually deleted after the upgrade is complete. |
This release of the Foglight Agent Manager does not include any third party known issues.
The 5.9.2 Foglight Agent Manager cartridge requires Foglight Management Server 5.7.5.5 or later. The cartridge is compatible with all previously released versions of the Agent Manager client application.
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 5.9.2 Agent Manager cartridge or upgrading the Foglight Management Server to version 5.7.5.5 or later. After all of the legacy hosts are running version 5.6.7, and the Foglight Management Server is upgraded to version 5.7.5.5 or later, you can start upgrading your hosts to version 5.9.2.
The following is a list of Foglight product versions and platforms compatible with this release.
Product Name |
Product Version |
Platform |
Foglight Management Server | 5.7.5.5 and later | All platforms supported by these versions of the Foglight Management Server |
Foglight Agent Manager Development Kit | 5.9.2 | All platforms supported by these versions of the Foglight Agent Manager Development Kit |
For more information about upgrading the Management Server and the Agent Manager, see the Foglight Upgrade Guide.
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center