The following is a list of issues known to exist at the time of this release:
Defect ID |
Known Issue |
FAIO-232 |
IC only collects one single record for Btrfs partitions mapped to the same physical device. |
IC-4275 |
Some metrics (bytes read/written, reads/writes) cannot be collected for ZFS disk. |
IC-4047 |
The "sqlserv.exe process" and "Memory Top Consumers" metrics collected by the Windows Agent are incorrect. |
IC-3873 |
On the All Hosts dashboard, metrics of Logical Disks are not accurate. |
IC-3617 |
The alarm view of the rule that was copied from the Record Severity could not be shown correctly. |
IC-2841 |
Half of processors (16/31) do not have Utilization metric. |
IC-2644 |
DellUnixAgent logs 'No begin line' when configured to monitor Solaris® on Foglight Agent Manager 5.8.1. |
IC-2370 |
On the Infrastructure Environment dashboard, Uptime always displays "Not Available" for Solaris® zones. |
IC-2058 |
Different cpu usage between Top CPU Consumers table and "topas" output on command line. |
IC-1684 |
Network metrics may be unavailable when monitoring Solaris® LDOMs. |
IC-1572 |
UnixAgent generates the Workaround: This is a basic attribute of Java® processes that use a large amount of memory on Solaris®. The workarounds are either to reduce the amount of memory used by FglAM (perhaps by moving agents to other FglAM instances) or by increasing the swap space available to the Solaris® system. The root problem is described in the following Oracle® report: JDK-5049299 : (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion. Please note that the fix for this issue provided in this report is only for Solaris 10 and later). This is generally only an issue for agents monitoring the local system, but can also occur when agents run on the system in question, but are monitoring a remote system. They may still need to execute commands on the host system. |
IC-1478 |
The Linux® data collector incorrectly identifies HP Smart Array physical disk as a logical disk. |
IC-1440 |
Research if HP-UX agent might submit incorrect value for run queue length: includes active processes not just queued. |
IC-1439 |
The Linux® agent submits incorrect value for run queue length; it includes active processes and not all blocked processes. |
IC-1304 |
When parsing |
IC-1253 |
Replace or augment the Event Log rule with a multi-severity rule. |
IC-1163 |
When a UnixAgent monitors an AIX® system remotely, the remote monitor running quest_perfstat.bin fails with a timeout, and the following message is logged:
|
IC-1103 |
LinuxCollector on local host: |
IC-1097 |
Network(receiveRate, sendRate, transferRate, utilization) can not be collected successfully while use non-native collector for AIX®, HP-UX agents. |
IC-1093 |
The WindowsAgent does not remove invalid characters in log data before transmitting it. |
IC-1049 |
While monitoring AIX® or HP-UX with the native collector, changing the user name of the credential used for monitoring generates an error related to the quest_perfstat.bin file. Workaround: Before making changes to the credential, stop data collection on any AIX or HP-UX agent that are currently using those credentials. Failing to stop data collection causes the collector to generate an error indicating that it cannot execute a binary in the remote host's tmp directory. To enable the agent to resume data collection, delete the offending binary from the remote host machine. |
IC-904 |
Mounted ISOs not reliably detected as read only. |
IC-851 |
Selecting a severity level on a tile in the Infrastructure Environment dashboard filters the list of hosts to only that severity. If a host's severity level changes, the host remains in the list even if you refresh the page. Workaround: If you leave the Infrastructure Environment dashboard and return, the filters are updated. |
IC-811 |
The user installing or upgrading a cartridge will sometimes get an error when accessing views installed with the cartridge. This only happens if users go from the Cartridge Inventory dashboard directly to a Dashboard of the newly installed or updated cartridge (for example, the Infrastructure Environment dashboard does not render on first access after an upgrade). Workaround: Refreshing the browser can often correct this problem. If this doesn't solve the problem, logging out and logging back in will clear the issue. |
IC-747 |
Output from interactive shell during an SSH connection may cause errors when parsing command execution results. |
IC-561 |
All Foglight for Infrastructure agents use the collection interval to calculate rate metrics. This is incorrect because a stop/start triggers a recollection before the interval expires. |
Defect ID |
Known Issue |
IC-3617 |
Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround. |
IC-2529 |
Foglight Log Monitor does not support the AIX® and Solaris® (SPARC®) platform with Foglight for Infrastructure 5.8.1. |
IC-1901 |
The Log Monitor page does not auto-refresh on Foglight Management Server version 5.6.5 to 5.6.10. |
Defect ID |
Known Issue |
AGENT-3716 |
PowerVMVirtualManager is not submitted when the PowerVM agent is running in an upgraded environment. For more details, see Troubleshooting Foglight for PowerVM. |
AGENT-3232 |
The metrics in pop-up view of the dependency node should use the specific dependency time range, not the system time range. |
AGENT-3218 |
The "PowerVM VIOS State Inspect" alarm does not display in the alarm table as expected when using a Firefox® 18.0 browser. The "PowerVM Server Connect State" alarm has been cleared, but the warning icon of the specific server still exists when using a Firefox 18.0 browser. |
The following is a list of issues known to exist at the time of this release:
Defect ID |
Known Issue |
FAIO-232 |
IC only collects one single record for Btrfs partitions mapped to the same physical device. |
IC-4275 |
Some metrics (bytes read/written, reads/writes) cannot be collected for ZFS disk. |
IC-4047 |
The "sqlserv.exe process" and "Memory Top Consumers" metrics collected by the Windows Agent are incorrect. |
IC-3873 |
On the All Hosts dashboard, metrics of Logical Disks are not accurate. |
IC-3617 |
The alarm view of the rule that was copied from the Record Severity could not be shown correctly. |
IC-2841 |
Half of processors (16/31) do not have Utilization metric. |
IC-2644 |
DellUnixAgent logs 'No begin line' when configured to monitor Solaris® on Foglight Agent Manager 5.8.1. |
IC-2370 |
On the Infrastructure Environment dashboard, Uptime always displays "Not Available" for Solaris® zones. |
IC-2058 |
Different cpu usage between Top CPU Consumers table and "topas" output on command line. |
IC-1684 |
Network metrics may be unavailable when monitoring Solaris® LDOMs. |
IC-1572 |
UnixAgent generates the Workaround: This is a basic attribute of Java® processes that use a large amount of memory on Solaris®. The workarounds are either to reduce the amount of memory used by FglAM (perhaps by moving agents to other FglAM instances) or by increasing the swap space available to the Solaris® system. The root problem is described in the following Oracle® report: JDK-5049299 : (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion. Please note that the fix for this issue provided in this report is only for Solaris 10 and later). This is generally only an issue for agents monitoring the local system, but can also occur when agents run on the system in question, but are monitoring a remote system. They may still need to execute commands on the host system. |
IC-1478 |
The Linux® data collector incorrectly identifies HP Smart Array physical disk as a logical disk. |
IC-1440 |
Research if HP-UX agent might submit incorrect value for run queue length: includes active processes not just queued. |
IC-1439 |
The Linux® agent submits incorrect value for run queue length; it includes active processes and not all blocked processes. |
IC-1304 |
When parsing |
IC-1253 |
Replace or augment the Event Log rule with a multi-severity rule. |
IC-1163 |
When a UnixAgent monitors an AIX® system remotely, the remote monitor running quest_perfstat.bin fails with a timeout, and the following message is logged:
|
IC-1103 |
LinuxCollector on local host: |
IC-1097 |
Network(receiveRate, sendRate, transferRate, utilization) can not be collected successfully while use non-native collector for AIX®, HP-UX agents. |
IC-1093 |
The WindowsAgent does not remove invalid characters in log data before transmitting it. |
IC-1049 |
While monitoring AIX® or HP-UX with the native collector, changing the user name of the credential used for monitoring generates an error related to the quest_perfstat.bin file. Workaround: Before making changes to the credential, stop data collection on any AIX or HP-UX agent that are currently using those credentials. Failing to stop data collection causes the collector to generate an error indicating that it cannot execute a binary in the remote host's tmp directory. To enable the agent to resume data collection, delete the offending binary from the remote host machine. |
IC-904 |
Mounted ISOs not reliably detected as read only. |
IC-851 |
Selecting a severity level on a tile in the Infrastructure Environment dashboard filters the list of hosts to only that severity. If a host's severity level changes, the host remains in the list even if you refresh the page. Workaround: If you leave the Infrastructure Environment dashboard and return, the filters are updated. |
IC-811 |
The user installing or upgrading a cartridge will sometimes get an error when accessing views installed with the cartridge. This only happens if users go from the Cartridge Inventory dashboard directly to a Dashboard of the newly installed or updated cartridge (for example, the Infrastructure Environment dashboard does not render on first access after an upgrade). Workaround: Refreshing the browser can often correct this problem. If this doesn't solve the problem, logging out and logging back in will clear the issue. |
IC-747 |
Output from interactive shell during an SSH connection may cause errors when parsing command execution results. |
IC-561 |
All Foglight for Infrastructure agents use the collection interval to calculate rate metrics. This is incorrect because a stop/start triggers a recollection before the interval expires. |
Defect ID |
Known Issue |
IC-3617 |
Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround. |
IC-2529 |
Foglight Log Monitor does not support the AIX® and Solaris® (SPARC®) platform with Foglight for Infrastructure 5.8.1. |
IC-1901 |
The Log Monitor page does not auto-refresh on Foglight Management Server version 5.6.5 to 5.6.10. |
Defect ID |
Known Issue |
AGENT-3716 |
PowerVMVirtualManager is not submitted when the PowerVM agent is running in an upgraded environment. For more details, see Troubleshooting Foglight for PowerVM. |
AGENT-3232 |
The metrics in pop-up view of the dependency node should use the specific dependency time range, not the system time range. |
AGENT-3218 |
The "PowerVM VIOS State Inspect" alarm does not display in the alarm table as expected when using a Firefox® 18.0 browser. The "PowerVM Server Connect State" alarm has been cleared, but the warning icon of the specific server still exists when using a Firefox 18.0 browser. |
The following is a list of issues known to exist at the time of this release:
Defect ID |
Known Issue |
FAIO-232 |
IC only collects one single record for Btrfs partitions mapped to the same physical device. |
IC-4275 |
Some metrics (bytes read/written, reads/writes) cannot be collected for ZFS disk. |
IC-4047 |
The "sqlserv.exe process" and "Memory Top Consumers" metrics collected by the Windows Agent are incorrect. |
IC-3873 |
On the All Hosts dashboard, metrics of Logical Disks are not accurate. |
IC-3617 |
The alarm view of the rule that was copied from the Record Severity could not be shown correctly. |
IC-2841 |
Half of processors (16/31) do not have Utilization metric. |
IC-2644 |
DellUnixAgent logs 'No begin line' when configured to monitor Solaris® on Foglight Agent Manager 5.8.1. |
IC-2370 |
On the Infrastructure Environment dashboard, Uptime always displays "Not Available" for Solaris® zones. |
IC-2058 |
Different cpu usage between Top CPU Consumers table and "topas" output on command line. |
IC-1684 |
Network metrics may be unavailable when monitoring Solaris® LDOMs. |
IC-1572 |
UnixAgent generates the Workaround: This is a basic attribute of Java® processes that use a large amount of memory on Solaris®. The workarounds are either to reduce the amount of memory used by FglAM (perhaps by moving agents to other FglAM instances) or by increasing the swap space available to the Solaris® system. The root problem is described in the following Oracle® report: JDK-5049299 : (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion. Please note that the fix for this issue provided in this report is only for Solaris 10 and later). This is generally only an issue for agents monitoring the local system, but can also occur when agents run on the system in question, but are monitoring a remote system. They may still need to execute commands on the host system. |
IC-1478 |
The Linux® data collector incorrectly identifies HP Smart Array physical disk as a logical disk. |
IC-1440 |
Research if HP-UX agent might submit incorrect value for run queue length: includes active processes not just queued. |
IC-1439 |
The Linux® agent submits incorrect value for run queue length; it includes active processes and not all blocked processes. |
IC-1304 |
When parsing |
IC-1253 |
Replace or augment the Event Log rule with a multi-severity rule. |
IC-1163 |
When a UnixAgent monitors an AIX® system remotely, the remote monitor running quest_perfstat.bin fails with a timeout, and the following message is logged:
|
IC-1103 |
LinuxCollector on local host: |
IC-1097 |
Network(receiveRate, sendRate, transferRate, utilization) can not be collected successfully while use non-native collector for AIX®, HP-UX agents. |
IC-1093 |
The WindowsAgent does not remove invalid characters in log data before transmitting it. |
IC-1049 |
While monitoring AIX® or HP-UX with the native collector, changing the user name of the credential used for monitoring generates an error related to the quest_perfstat.bin file. Workaround: Before making changes to the credential, stop data collection on any AIX or HP-UX agent that are currently using those credentials. Failing to stop data collection causes the collector to generate an error indicating that it cannot execute a binary in the remote host's tmp directory. To enable the agent to resume data collection, delete the offending binary from the remote host machine. |
IC-904 |
Mounted ISOs not reliably detected as read only. |
IC-851 |
Selecting a severity level on a tile in the Infrastructure Environment dashboard filters the list of hosts to only that severity. If a host's severity level changes, the host remains in the list even if you refresh the page. Workaround: If you leave the Infrastructure Environment dashboard and return, the filters are updated. |
IC-811 |
The user installing or upgrading a cartridge will sometimes get an error when accessing views installed with the cartridge. This only happens if users go from the Cartridge Inventory dashboard directly to a Dashboard of the newly installed or updated cartridge (for example, the Infrastructure Environment dashboard does not render on first access after an upgrade). Workaround: Refreshing the browser can often correct this problem. If this doesn't solve the problem, logging out and logging back in will clear the issue. |
IC-747 |
Output from interactive shell during an SSH connection may cause errors when parsing command execution results. |
IC-561 |
All Foglight for Infrastructure agents use the collection interval to calculate rate metrics. This is incorrect because a stop/start triggers a recollection before the interval expires. |
Defect ID |
Known Issue |
IC-3617 |
Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround. |
IC-2529 |
Foglight Log Monitor does not support the AIX® and Solaris® (SPARC®) platform with Foglight for Infrastructure 5.8.1. |
IC-1901 |
The Log Monitor page does not auto-refresh on Foglight Management Server version 5.6.5 to 5.6.10. |
Defect ID |
Known Issue |
AGENT-3716 |
PowerVMVirtualManager is not submitted when the PowerVM agent is running in an upgraded environment. For more details, see Troubleshooting Foglight for PowerVM. |
AGENT-3232 |
The metrics in pop-up view of the dependency node should use the specific dependency time range, not the system time range. |
AGENT-3218 |
The "PowerVM VIOS State Inspect" alarm does not display in the alarm table as expected when using a Firefox® 18.0 browser. The "PowerVM Server Connect State" alarm has been cleared, but the warning icon of the specific server still exists when using a Firefox 18.0 browser. |
The following is a list of issues known to exist at the time of this release:
Defect ID |
Known Issue |
FAIO-232 |
IC only collects one single record for Btrfs partitions mapped to the same physical device. |
IC-4275 |
Some metrics (bytes read/written, reads/writes) cannot be collected for ZFS disk. |
IC-4047 |
The "sqlserv.exe process" and "Memory Top Consumers" metrics collected by the Windows Agent are incorrect. |
IC-3873 |
On the All Hosts dashboard, metrics of Logical Disks are not accurate. |
IC-3617 |
The alarm view of the rule that was copied from the Record Severity could not be shown correctly. |
IC-2841 |
Half of processors (16/31) do not have Utilization metric. |
IC-2644 |
DellUnixAgent logs 'No begin line' when configured to monitor Solaris® on Foglight Agent Manager 5.8.1. |
IC-2370 |
On the Infrastructure Environment dashboard, Uptime always displays "Not Available" for Solaris® zones. |
IC-2058 |
Different cpu usage between Top CPU Consumers table and "topas" output on command line. |
IC-1684 |
Network metrics may be unavailable when monitoring Solaris® LDOMs. |
IC-1572 |
UnixAgent generates the Workaround: This is a basic attribute of Java® processes that use a large amount of memory on Solaris®. The workarounds are either to reduce the amount of memory used by FglAM (perhaps by moving agents to other FglAM instances) or by increasing the swap space available to the Solaris® system. The root problem is described in the following Oracle® report: JDK-5049299 : (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion. Please note that the fix for this issue provided in this report is only for Solaris 10 and later). This is generally only an issue for agents monitoring the local system, but can also occur when agents run on the system in question, but are monitoring a remote system. They may still need to execute commands on the host system. |
IC-1478 |
The Linux® data collector incorrectly identifies HP Smart Array physical disk as a logical disk. |
IC-1440 |
Research if HP-UX agent might submit incorrect value for run queue length: includes active processes not just queued. |
IC-1439 |
The Linux® agent submits incorrect value for run queue length; it includes active processes and not all blocked processes. |
IC-1304 |
When parsing |
IC-1253 |
Replace or augment the Event Log rule with a multi-severity rule. |
IC-1163 |
When a UnixAgent monitors an AIX® system remotely, the remote monitor running quest_perfstat.bin fails with a timeout, and the following message is logged:
|
IC-1103 |
LinuxCollector on local host: |
IC-1097 |
Network(receiveRate, sendRate, transferRate, utilization) can not be collected successfully while use non-native collector for AIX®, HP-UX agents. |
IC-1093 |
The WindowsAgent does not remove invalid characters in log data before transmitting it. |
IC-1049 |
While monitoring AIX® or HP-UX with the native collector, changing the user name of the credential used for monitoring generates an error related to the quest_perfstat.bin file. Workaround: Before making changes to the credential, stop data collection on any AIX or HP-UX agent that are currently using those credentials. Failing to stop data collection causes the collector to generate an error indicating that it cannot execute a binary in the remote host's tmp directory. To enable the agent to resume data collection, delete the offending binary from the remote host machine. |
IC-904 |
Mounted ISOs not reliably detected as read only. |
IC-851 |
Selecting a severity level on a tile in the Infrastructure Environment dashboard filters the list of hosts to only that severity. If a host's severity level changes, the host remains in the list even if you refresh the page. Workaround: If you leave the Infrastructure Environment dashboard and return, the filters are updated. |
IC-811 |
The user installing or upgrading a cartridge will sometimes get an error when accessing views installed with the cartridge. This only happens if users go from the Cartridge Inventory dashboard directly to a Dashboard of the newly installed or updated cartridge (for example, the Infrastructure Environment dashboard does not render on first access after an upgrade). Workaround: Refreshing the browser can often correct this problem. If this doesn't solve the problem, logging out and logging back in will clear the issue. |
IC-747 |
Output from interactive shell during an SSH connection may cause errors when parsing command execution results. |
IC-561 |
All Foglight for Infrastructure agents use the collection interval to calculate rate metrics. This is incorrect because a stop/start triggers a recollection before the interval expires. |
Defect ID |
Known Issue |
IC-3617 |
Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround. |
IC-2529 |
Foglight Log Monitor does not support the AIX® and Solaris® (SPARC®) platform with Foglight for Infrastructure 5.8.1. |
IC-1901 |
The Log Monitor page does not auto-refresh on Foglight Management Server version 5.6.5 to 5.6.10. |
Defect ID |
Known Issue |
AGENT-3716 |
PowerVMVirtualManager is not submitted when the PowerVM agent is running in an upgraded environment. For more details, see Troubleshooting Foglight for PowerVM. |
AGENT-3232 |
The metrics in pop-up view of the dependency node should use the specific dependency time range, not the system time range. |
AGENT-3218 |
The "PowerVM VIOS State Inspect" alarm does not display in the alarm table as expected when using a Firefox® 18.0 browser. The "PowerVM Server Connect State" alarm has been cleared, but the warning icon of the specific server still exists when using a Firefox 18.0 browser. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center