Symantec MONITOR PACKS FOR SERVERS 7.0 - SP2 S, Руководство по выпуску

Страница: 8 / 10

Table 1-2
Fixed Issues in this Release (continued)
Internal ID Description Issue
1806935 The metrics, rules, and policies that belong to the default
monitor packs are not restored when you attempt to
reimport the pack manually.
To workaround this issue: uninstall the monitor packs and
then install them again.
Monitor packs cannot be re-imported
after you delete a monitor pack that
was previously imported
Known Issues in this Release
The following are known issues for this release. If additional information about
an issue is available, click the Article ID link.
Table 1-3
Known issues in this Release
Internal ID Description Issue
1978268 When you restart the Altiris Monitor Agent service in the
Services list in Windows, a timeout message can appear.
After some time the service stops and you can start it again. A timeout message can appear when
you restart the Monitor Agent service
on a Windows computer.
1679274 Apache 2.2.11 is installed into:
/usr/local/apache2
. The
log is installed into:
/usr/local/apache2/logs/access_log
. However, the
provided Apache 2 Server Log Solaris metric only uses the
following custom path:
/var/apache2/logs/access_log
. This path is only
correct for the original Apache server that is provided by
Sun. On Apache 2.2.11 this metric cannot be evaluated and
triggered.
If you have a custom installation of Apache 2.2.11 on a
monitored computer, then you must clone the original
metrics and then update them to use the correct log path.
Metric Apache 2 Server Log Solaris
Metric - log custom path is not
compatible with Apache 2.2.11
1702790 ESX Extended pack will not function on ESX servers that
are running in maintenance mode. The Extended Host Monitor Pack does
not support servers in maintenance
mode
Monitor Pack for Servers 7.0 SP2 Release Notes
Known Issues in this Release
8