user manual

Overall WEBES Release Notes
1.6 WEBES Known Issues
Rev. 9/8/06
1–12 Web-Based Enterprise Services Release Notes
Running a local copy of WEBES for analysis only on that local system does not present a
problem. Likewise, connecting directly to a remote system via the CLI or web URL (for
example, without having WEBES installed on your local system) is okay.
To avoid a compatibility issue, make sure that the exact same version of WEBES is installed
on all systems that will connect to one another, as within a given site or enterprise. In any
clustered environment, it is especially important to have the same version (including dot
release or Service Pak) installed on every node. Backward compatibility will be introduced in
a future WEBES release.
1.6.1.9 Director Process Not Responding
If one of the WEBES components is not responding or giving an error, it may be that the
Director process is not responding. To correct this problem, see the Director chapter in the
WEBES User Guide. It includes a section on troubleshooting an unresponsive Director
process.
1.6.1.10 Director Process Stopping When Out of Memory
If the Director hangs or terminates unexpectedly, check the Director log files (see the WEBES
User Guide for more information on log files). If the log files contain errors mentioning “out
of memory” conditions, one of the following conditions may apply:
• Your system has run out of memory or paging space.
• The Director process has reached its Java memory limits. These limits are set during
WEBES installation, but may be overridden by a user.
If the Java memory limits are responsible for the problem, you can raise the memory limits
applied to the Director process and its subprocesses. After the limits have been increased, you
can restart the Director and perform the actions that caused the out of memory error. The limits
can be set as high as necessary, and are only constrained by the memory and paging space
available on the system. Refer to the WEBES User Guide for details on adjusting the memory
limits.
1.6.1.11 Upgrade Requires Reinitialized Log
If you are running SEA (formerly Compaq Analyze), reinitialize the system error log as
described in the platform-specific sections of the WEBES Installation Guide before
performing a WEBES upgrade.
Otherwise, up to seven days of repeat (previously seen) problem reports may appear. This
behavior occurs because of an issue where SEA re-scans the entire log after the upgrade.
Normally, SEA scans the entire log only after a fresh installation.