HP Web-Based Enterprise Services 4.5 Webes Configuration Information Not Restored, Workaround

Page 18

Overall WEBES Release Notes

1.6 WEBES Known Issues

Socket close problem: <local>:40790387440747720

EXCEPTION java.net.SocketException: Socket closed

EXCEPTION java.io.IOException: Broken pipe

at java.net.SocketOutputStream.socketWrite(Native Method)

1.6.1.5 WEBES Configuration Information Not Restored

In some cases, WEBES configuration information such as contact names, email addresses, notification enablements, and managed entity XML data may not be restored on an upgrade to WEBES, either through:

1.Uninstalling an older version of WEBES and later installing a newer version, even if you choose to save the WEBES information during WEBES uninstallation or

2.Upgrading WEBES while an older version is installed.

The WEBES team is investigating this problem. We intend to fix such cases in future releases of WEBES.

Workaround

1.On reinstallation of WEBES, re-enter the data when prompted.

2.After upgrading WEBES, change any necessary configuration items as described in the SEA User’s Guide and the CCAT User’s Guide. WEBES upgrades are mostly silent and do not prompt the user for configuration information.

1.6.1.6 WEBES Output Log Files Grow Without Bound

The WEBES Director and WCCProxy text output log files in the specific/webes/logs and specific/wccproxy/logs directories (see SEA User’s Guide section 2.5, “Log Files”) grow without bound. The processes append text logging information to those files and do not as yet control their size.

Normally, this is not a problem since WEBES processes write very little to these log files when there are no internal WEBES errors to report. However, if an error situation arises that causes WEBES to log a great deal of information into the logs, the log files could (in the worst case) fill up the system’s disk space.

Also, if you have changed the logging level to produce more debug output (see SEA User’s Guide section 2.5, “Log Files”), the log file sizes can grow significantly even under normal operation.

On OpenVMS and Windows, a new copy of the Director log file is created each time the Director is started. A copy of the previous Director log file is retained, while older logs, if any, are deleted. On the UNIX variants, the log files are appended with each Director start and are never deleted.

A future WEBES version will monitor and limit the sizes of these log files.

Rev. 9/8/06

1–10 Web-Based Enterprise Services Release Notes

Image 18
Contents Web-Based Enterprise Services Release Notes Software VersionIi Web-Based Enterprise Services Release Notes Web-Based Enterprise Services Release Notes Page Contents Contents System Event AnalyzerComputer Crash Analysis Tool Further Information Overall Webes Release Notes Summary Hardware RequirementsOverall Webes Release Notes Summary Operating System Requirements Overall Webes Release Notes Operating System RequirementsTest Environment Overall Webes Release Notes Test EnvironmentWindows RedHat Linux not Patched New in this ReleaseOverall Webes Release Notes 1.5 New in this Release OpenVMSMiscellaneous Overall Webes Release Notes New in this ReleaseIntegrity Servers Virtual Library System VLS Overall Webes Release Notes 1.5 New in this Release Installing Webes on Unsupported Platforms Webes Known IssuesGeneral Webes Issues Overall Webes Release Notes Webes Known IssuesError During Reading of Obligation Information Webes Installation Issue on ISEE-OSEM HostIntermittent Socket Errors Webes Configuration Information Not Restored Webes Output Log Files Grow Without BoundWorkaround Webes Temporary Files Use Disk Space Backward CompatibilityWorkarounds Director Process Stopping When Out of Memory Upgrade Requires Reinitialized LogDirector Process Not Responding Webes Uninstall Affects Isee Client WCCProxy Errors When the Director or WCCProxy is Restarted Too SoonService Cockpit Compatibility Upgrading Versions Older Than Two ReleasesErrors From desta siclqsap on Commands Changing Time Zone Causes Incorrect Report TimeWindows Webes Issues ClassNotFoundExceptions in Director LogWebes Installation Appears to Hang Installation Prompts When File Fails to DeleteWebes Configuration is Not Migrated for Windows Itanium AdditionCcat Not Available on Windows Itanium Installation Internal Error Uninstall of Previous Webes May HangDesta msg -chgport Command Path Update Required on Terminal Server InstallationWindows Itanium Webes Removal Leaves Files Behind Linux Webes Issues Segmentation Fault Error MessageDirector May Require Restart OpenVMS Webes Issues Set ODS-5 Attributes Before Issuing Webes CLI CommandsJfex Errors Cannot Get Local Host NameNew OpenVMS Patch Removal Feature Continuous CPU Usage After Daylight Savings Time ChangeUpgrade Requires Same Node as Install Alternate Boot Start and Stop MethodsCannot Get Smtp Notification on OpenVMS Run the following commands to stop the Smtp debug logging Further Information Overall Webes Release Notes Further InformationOverall Webes Release Notes 1.7 Further Information System Event Analyzer Supported Products System Event Analyzer SummarySystem Event Analyzer Supported Products KZPSC/KZPAC/KZPBA/KZPCM/KZPSA/KZPCC/KSPEASEA Known Issues General SEA IssuesSystem Event Analyzer SEA Known Issues File Not Found Error In Desta Log File Serial Number Prevents Rules from WorkingFields Contain Unavailable Duplicate Callouts with both DECevent and Webes Installed Transferring Files with FTPInsert the following code at the beginning of the file Ca Command Changed to wsea SEA Command Line Interface IssuesSEA Problem Reports Not Received by Osem Entering CommandsWindows interprets it as With either of the following paths SEA Web Interface Issues $ wsea n analyze svctoolscommoncommon.ca.examples*.zpdEnabling Text Entry in Other Logs Pane Node Name Change Causes Connection or Notification FailureNull-Pointer Errors from Large Log Files High Volume of Events Hangs InterfaceNull-Pointer Errors Cannot Activate a Running NodeTime-out Issue JavaScript ErrorsJavaScript Error When Viewing Director Settings Multiple Sessions using Mozilla and NetscapeServices Fail to Start TipRun the following commands for all platforms LinuxMultiple Java Installs May Affect Web Interface Windows SEA Issues Old SEA Example File Names Migrated But InaccessibleSEA EVA Collections Too Big for Isee to Send to HP Execute the following command Windows Event Log May Not Grow to Configured Size Incomplete Uninstall of Older VersionXP Internet Explorer Does Not Have Java Webes Commands Not Recognized Test Command Generates ErrorWebes Directory Tree Missing or Access Denied Hewlett-Packard Service Tools Entry on Start Menu is EmptyNapp Error Description Newly Added EVA Not Listed in SEA Web InterfaceHP-UX SEA Issues Resuming from Standby Loses Network ResourcesNo Binary Event Log Linux SEA Issues 6.1 C/C++ Runtime Libraries Version 6.1.1 or Later RequiredAdding Managed Entities Corrupts Director OpenVMS SEA Issues Insufficient Privilege or File Protection Violation Webes Commands Return Error Activating Image Slow Response Generating Other Logs ListExclude Node Names from Filespecs CAAgent Processes Created But Not DisappearingSystem Event Analyzer Further Information System Event Analyzer 2.4 Further Information Page Computer Crash Analysis Tool Ccat Known Issues General Ccat IssuesComputer Crash Analysis Tool Summary Computer Crash Analysis Tool Ccat Known Issues Windows Ccat IssuesCLI Commands Not Recognized Ccat IVP File Not FoundOpenVMS Ccat Issues Inability To Execute CLI CommandsComputer Crash Analysis Tool Further Information Computer Crash Analysis Tool 3.4 Further Information