Quest® Foglight Agent Manager 5.6.2.6

Released with Foglight Management Server 5.6.5

Release Notes

October 2012


Contents

Welcome to Foglight

Foglight Agent Manager

Read this First

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information

 


Welcome to Foglight

Quest Software's Foglight® solution simplifies application performance monitoring and reduces the skills and effort required to manage applications, the user experience, and the supporting infrastructure.

Unlike other solutions, Foglight uses a single code base, and has a model-driven design that couples fast deployment and accelerated time-to-value. It offers the modular flexibility required to deliver a range of capabilities and sophistication to meet the needs of any organization—from those still focused on technology-centric monitoring to those that have completed the transition to application-centric or transactional monitoring.

Foglight performs equally well in physical, virtual, and mixed infrastructure environments, providing visibility into issues affecting the application and end-user experience.  Intuitive workflows help you quickly move from the symptom to the root cause in the application, database, infrastructure, or network to resolve issues, reducing mean time to resolution. Predefined and drag-and-drop dashboards provide insight that is tailored to each stakeholder. By offering comprehensive visibility into your monitored environment, Foglight helps ensure that cross-functional teams collaborate on and prioritize issues that matter most to the business.

 


Foglight Agent Manager

Foglight agents require the Foglight Agent Manager (FglAM) to manage their life-cycles and centralize communications with the Foglight Management Server.

For information about the supported platforms for the Agent Manager, see the System Requirements and Platform Support Guide.

These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.6.2.6 release of the Agent Manager. Review all sections before starting the installation.

 


Read this First

Important: If you are upgrading only the Agent Manager on a version 5.6.2 or 5.6.3 Management Server, you may encounter a known issue in the Management Server that prevents successful deployment of the Agent Manager 5.6.2.6 cartridge file. This issue has been resolved in the version 5.6.4 Management Server. If you do not want to upgrade your Management Server, you must use one of the following methods to upgrade to Agent Manager version 5.6.2.6:

For more information about upgrading, see the Upgrade and Compatibility section.

 


New in this Release

This release does not include any new features. It was made to accompany the 5.6.5 release of the Management Server.

Release Notes for the Agent Manager Development Kit are now provided in a separate document: Foglight Agent Manager 5.6.2.6 Development Kit Release Notes.

 


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Agent Manager Core

Defect ID

Resolved Issue

FAM-4375 Initial tests for Windows Server 2012 completed. Testing continues and support will be confirmed after the release.
FAM-4334 The Agent Manager was updated to the latest Java 1.6 JRE release for security fixes.
FAM-4331 Agent threads were in some cases returned to the pool in a bad state.
FAM-4257 The DNSResolverService logged an InterruptedException as an ERROR instead of VERBOSE or DEBUG.
FAM-4232 The agentproperties.cache file was rewritten to disk on a 30s schedule, even if the properties were unchanged.
FAM-4177 The Agent Manager ICMP service failed to start if one of the selected ports was already in use.
FAM-4113 The Agent Manager failed to deploy packages, indicating the installation was still in progress.
FAM-3067 Agent Manager DNS caching never expired looked-up addresses.

Remote Connections and Credentials

Defect ID

Resolved Issue

FAM-4338 The WMI native implementation spawned timer threads that were not cancelled.
FAM-4328 A NullPointerException was thrown when monitoring a host that did not exist.
FAM-4326 A java.lang.ClassCastException was thrown when calling executMethod on a custom WMI provider.
FAM-4322 Memory leak: SSHConnectionPool was leaking SSHGanymedConnectionImpls.
FAM-4315 Fixed the krb5.config template and generation to adhere to the krb5.conf spec even though WinRMConnections could still be established.
FAM-4208 Added a Core Credential validator scheme wininfo to test connections with either WinRM or WMI.
FAM-4207 Connected the WinRM test credential class to the CredentialConnectionTestListener.
FAM-4204 A WinRM request could not be processed when various values contained certain invalid XML characters that had not escaped.
FAM-4147 A WinRM connection failed with the Negotiate authentication scheme, when the Agent Manager was installed on an AIX machine.

Legacy Agent Support (JFogbank)

Defect ID

Resolved Issue

FAM-4084 The PeopleSoft agent in some cases failed to activate if edits were made to the primary agent properties while the agent was modifying the secondary properties.

 


Known Issues

The following is a list of issues known to exist at the time of this release.

Agent Manager Core

Defect ID

Known Issue

FAM-4418 Fast mode collectors defined with a CRON schedule never terminate.
FAM-4366 Erroneously duplicated Agent Manager installs are currently not detected.
FAM-4345 Attempts to retrieve a support bundle using the browser interface or the command line on a Solaris 11 sparc system fail.
FAM-4298 When the setuid_launcher is owned by the root, the upgrade process fails.
FAM-4278 The Agent Manager uncaught exception handler should not log ThreadDeath exceptions.
FAM-4273 HPUX: The system info file in the support bundle is empty.
FAM-4216 FglAM Upgrade process does not migrate changes from vm.config.
FAM-4197 Locked agents can cause the support bundle to fail.
FAM-4177 The Agent Manager ICMP service fails to start if one of the ports selected is already in use.
FAM-4116 When starting up, the Agent Manager attempts to load the entire message data cache, even it does not fit into memory.
FAM-4085 Agent names are not scanned for invalid characters, to prevent attempts to use them in log file names.
FAM-4042 Solaris: When monitoring the local system,  the Agent Manager requires extra swap space to be made available so that it can execute commands.
FAM-3974 When agent deployment fails due to an agent type that is defined in an existing package and a new package, a NullPointerException occurs.
FAM-3773 The Agent Manager may crash when opening or reading a socket if the VM memory is full.
FAM-3753 The Quartz library does not rethrow ThreadDeath exceptions.
FAM-3729 An Agent Manager with an out-of-process (OOP) agent reports an error:
Could not transmit a message directly to the downstream at 127.0.0.1.
FAM-3667 On Windows hosts, the Agent Manager may crash when a memory leak occurs in the native Hyper-V host detection code.
FAM-3629 When scheduling collections using a CRON expression, the system attempts to derive a collection interval when submitting topology data.
FAM-3560 The system needs to re-implement logging of the encryption algorithm when connecting to an HTTPS upstream.
FAM-3361 The Agent Manager's file transfer utility starts in an unexpected directory: $FGLAM/client/X.Y.Z-build.
FAM-3270 A message schema validation failure in the Agent Manager is reported as a message schema version mismatch in the Management Server.
FAM-2945 Migrate Agent Manager installations on Windows that use the old service name, FoglightAgentManager, to installations using the new name, AgentManager.
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 undeployed from the Agent Manager. Currently, this is only possible using a manual procedure.

FAM-2315 When a laptop wakes up from sleep mode with the Agent Manager running, an OutOfMemoryError results: Unable to create new native thread. The Agent Manager must be restarted.
FAM-2258 The Agent Manager's message cache causes network traffic when the Agent Manager is installed in an NFS directory.
FAM-2144 Editing the display name and host UUID on an installed Agent Manager breaks existing agent instances.
FAM-2132 Structured data collection: If a user deletes a row from the Collection Frequency secondary agent property, the property cannot be restored properly due to hidden fields.
FAM-2102 Agent Manager installation in directories with non-latin-1 characters is not supported.
FAM-1996 Windows clients experience an automatic Activation/Deactivation cycle when deploying an agent package.
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.

FAM-1455 When starting fglam.exe -b, a benign Did not receive notification warning and Could not start FglAM (FoglightAgentManager) service error appears.
FAM-1331 The agent log files intermittently display the failed sudo attempts in stderr.
FAM-507 The Management Server browser interface reports agent creation as successful, even if it fails due to remote client unavailability.
FAM-312 The XML file written by the Agent Manager includes a benign unused reference to an old namespace in the output.
FAM-301 If SPAR/GAR deployment fails, extracted files are left behind. This is benign.

Foglight Management Server FglAM Adapter

Defect ID

Known Issue

FAM-4122 Obsolete empty fglam-PLATFORM.car cartridges (used to name the .car files) are left behind after upgrade with the -all cart option.
FAM-4081 A scheduled process in the adapter to monitor remote host connection state progress may re-initialize the state position if current polling intervals are long.
FAM-4016 Timestamp topology properties are not handled correctly by the CDT.
FAM-3873 The adapter lifecycle update script that deletes duplicate agents aborts if there are more than two duplicates of the same agent type.
FAM-3829 A race condition that can occur when the Management Server restarts can cause an Allocate exception for the FglAMServlet if the Agent Manager HTTP request arrives before the Management Server adapter is fully activated.
FAM-3814 The adapter is unable to create agents after un-deploying and re-deploying the agent package.
FAM-3731 Agents are set to NOT_COLLECTING_DATA when the Agent Manager restarts.
FAM-3727 If an Agent Manager is stopped and restarted several times in quick succession, some agents can end up in the wrong state.
FAM-3616 An agent that is deleted from the Management Server while the hosting Agent Manager is not connected may be restored when the Agent Manager reconnects.
FAM-2615 The adapter is unable to upgrade Agent Managers connected through a concentrator until all directly connected Agent Managers are upgraded.

Remote Connections and Credentials

Defect ID

Known Issue

FAM-3995 The Agent Manager may experience intermittent failures with an EXCEPTION_ACCESS_VIOLATION error in the Jacob native COM implementation.
FAM-3885 The Remote Connection services do not default to a global timeout value if no other timeout value is specified.
FAM-3884 An Agent Manager installed on a Linux platform cannot establish a WMI connection to Windows Server 2008, Windows 7, or Windows Vista with a local user of the Administrator group.
FAM-3864 An Agent Manager installed on a Linux platform cannot establish a WMI connection to a monitored Windows host when the Windows Firewall is enabled.
FAM-3845 An Agent Manager installed on an AIX platform cannot establish a WinRM HTTP connection to a monitored Windows host using the Negotiate authentication scheme.

Installer

Defect ID

Known Issue

FAM-4067 If the fglam-init-script-installer.sh script was generated with a version of the Agent Manager earlier than 5.6.2.4, it does not work correctly on Linux systems that use upstart to manage init scripts.
Workaround: After upgrading to Agent Manager version 5.6.2.4, regenerate the script by running: fglam --config.
FAM-3950 The --help documentation for the installer does not correctly indicate that TMPDIR can be used to specify the directory the installer unpacks in and runs from.
FAM-3930 Symantec Endpoint Protection 12 reports false positive virus warnings for Agent Manager installers.

When downloading a Windows Agent Manager installer (32- or 64-bit) from the Management Server, Symantec Endpoint Protection version 12 may report a Download Insight failure with the signature WS.Reputation.1. This is not an actual virus signature; rather, it is simply a reputation system which rejects downloads of new executables that have not been seen by many Symantec Endpoint Protection users. This warning may be safely ignored.
Workaround: To proceed with the download, click More under the Activity box, and then click Allow This File.

Running the 32-bit Windows installer may cause Symantec Endpoint Protection to also report a false positive detection with the signature Bloodhound.Sonar.9. Again, this is not an actual virus signature, but rather a heuristic which is triggering incorrectly. With default settings, Symantec Endpoint Protection will not allow the Agent Manager installation to proceed; the installer will abort with the message Configuration Failed.
Workaround: Open Symantec Endpoint Protection, and click Change Settings on the left. Under Proactive Threat Protection, click Configure Settings, and under Sonar, enable the checkbox Prompt Before Terminating a Process.
FAM-3907 The error message that occurs when the silent installer cannot create a required directory is misleading/unclear.
FAM-3645 Failures in the operating system's NFS file-locking process can result in the Agent Manager not starting, or starting and then immediately shutting down.
FAM-3502 The Agent Manger installation parameter --noservice is ignored during a silent installation when an Agent Manager service is already installed on the host.
FAM-3123 The unbranded Agent Manager Windows service name is too generic.
FAM-1189 High Availability peer detection only works if the primary Management Server is used; it does not work if the secondary Management Server is used.
FAM-970 When you download the Agent Manager installers from the Components for Download dashboard using Internet Explorer, an Internet Explorer - Security Warning appears, indicating that the publisher is unknown.
FAM-818 If you interrupt the Agent Manager installation process, complete:100% is still displayed.

Legacy Agent Support (JFogbank)

Defect ID

Known Issue

FAM-4084 When the PeopleSoft agent is launched for the first time, it detects the processes that need to be monitored, and populates its own secondary ASP with rows for each process. If the user modifies the agent's primary ASP while this procedure is in progress, the agent can fail to launch.
Workaround: Wait until the agent has completed the procedure of populating the secondary ASP before making any modifications to the primary ASP.
FAM-1486

When a large legacy Foglight 4-based agent package is used for the first time in an Agent Manager installation, if you create multiple agent instances simultaneously, an error occurs: UndeclaredThrowableException "Failed to acquire the agent lock".

Workaround: The first time you create an agent instance after installing the package, create only a single instance. After that instance is complete, you can create multiple instances simultaneously.

FAM-1411 When sudo is not configured to allow root launch without a password for an agent that requests it, the sudo process (labeled fog4_launcher) persists for five minutes until it times out.
FAM-1365 When a DB2 agent is installed in two different Agent Manager instances on the same host, auto-discovery logs the message:
WARN An agent named DB2_DB2 could not be found
.
FAM-598 The system is unable to start data collection for a JFogbank agent with a space in the instance name.

Script Agent Support (JCollector)

Defect ID

Known Issue

FAM-3915

Script agents that call Windows PowerShell scripts can hang if they are not provided with stdin on the command-line.

Workaround: Provide the script file as stdin when using a batch script agent to invoke a PowerShell script. For example:

@echo off
type yourpowershellscript.ps1 | powershell -ExecutionPolicy RemoteSigned -NoProfile -NonInteractive -command -
FAM-3471 A Null Pointer Exception occurs when you start or stop data collection for the script agent.
FAM-1525 Script agents do not run properly if they are deployed with incorrect line endings for the target host.

Common

Defect ID

Known Issue

COM-1276 Using multiple --add-debug-level options leads to a FATAL log message even though the help text says they are allowed.
COM-1267 A script used to pull selected entries from the Windows event log for the Agent Manager support bundle does not exist on Windows 7 or Windows Server 2008. 
COM-1263 The temp directory detection code should determine if a directory exists before attempting to create a temporary file in it.
COM-1262 The command-line option -r for the Agent Harness is stripped out on Windows OS.
COM-1208 The command-line thread dump fails on Windows Server 2008 R2 with the message: Could not create outgoing pipe ... Access is denied.

 


Third Party Known Issues

The following is a list of third party issues known to exist at the time of this release.

Defect ID

Known Issue

FAM-3930 Symantec Endpoint Protection 12 reports false positive virus warnings for Agent Manager installers.

When downloading a Windows Agent Manager installer (32- or 64-bit) from the Management Server, Symantec Endpoint Protection version 12 may report a Download Insight failure with the signature WS.Reputation.1. This is not an actual virus signature; rather, it is simply a reputation system which rejects downloads of new executables that have not been seen by many Symantec Endpoint Protection users. This warning may be safely ignored.
Workaround: To proceed with the download, click More under the Activity box, and then click Allow This File.

Running the 32-bit Windows installer may cause Symantec Endpoint Protection to also report a false positive detection with the signature Bloodhound.Sonar.9. Again, this is not an actual virus signature, but rather a heuristic which is triggering incorrectly. With default settings, Symantec Endpoint Protection will not allow the Agent Manager installation to proceed; the installer will abort with the message Configuration Failed.
Workaround: Open Symantec Endpoint Protection, and click Change Settings on the left. Under Proactive Threat Protection, click Configure Settings, and under Sonar, enable the checkbox Prompt Before Terminating a Process.

 


Upgrade and Compatibility

The 5.6.2.6 Foglight Agent Manager cartridge requires Foglight Management Server 5.6.2 or later. The 5.6.2.6 Agent Manager cartridge is compatible with all previously released versions of the Agent Manager client application.

Important: If you are upgrading only the Agent Manager on a version 5.6.2 or 5.6.3 Management Server, you may encounter a known issue in the Management Server that prevents successful deployment of the Agent Manager 5.6.2.6 cartridge file. This issue has been resolved in the version 5.6.4 Management Server. If you do not want to upgrade your Management Server, you must use one of the following methods to upgrade to Agent Manager version 5.6.2.6:

For more information about upgrading the Agent Manager, see the Upgrade Guide.

 


System Requirements

AIX support requires the recommended patch levels from IBM. For example, AIX 5.3 should be patched to at least TL8. Any version prior to TL8 is not supported. Version TL9 SP1 is recommended.

For detailed information about system requirements, see the System Requirements and Platform Support Guide.

Platform-specific Identification

The Agent Manager determines a unique ID for each system on which it runs, and includes that ID with the data submission from each agent. On some Linux systems, however, the Agent Manager may be unable to determine a unique system ID. In such cases, the Agent Manager does not return any system ID in the data submission.

Final Platform Support Notice

Support for the following operating systems will be discontinued in an upcoming Foglight release:

These operating systems are supported in this release, as documented in the System Requirements and Platform Support Guide. We hope that this notice of planned support changes helps customers plan their upgrades. Please contact Quest Support if you have any questions or concerns about this change.

 


Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: The Management Server and Agent Manager client will be enabled for Global Operations, but not localized to any particular locale. Legacy Foglight 4 agents will continue to be limited to the locales supported under Foglight 4. Consult the Global Operations statement for each agent to determine its own capabilities and limitations. The Agent Manager currently requires installation in a directory path with only ASCII characters.

 


Getting Started

Contents of the Release Package

Foglight Agent Manager 5.6.2.6 is distributed with Foglight Management Server 5.6.5.

For information about what is included in the Foglight 5.6.5 release package, see the Foglight Release Notes.

Installation Instructions

Refer to the Foglight Agent Manager Installation Guide for installation and configuration instructions.

 


For More Information

Get the latest product information, find helpful resources, test the product betas, and join a discussion with the Foglight Quest team and other community members. Join the Foglight Community at http://communities.quest.com/community/foglight.

 

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web http://www.quest.com

Refer to our Web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at http://www.quest.com/support.

From our Support Portal, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures.
The guide is available at http://www.quest.com/support.

 


© 2012 Quest Software, Inc. ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

www.quest.com

Email: legal@quest.com

Refer to our Web site for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

 

Third Party Contributions

Foglight contains some third party components. For a complete list, see the License Credits page in Foglight online help.

 

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.