Overall WEBES Release Notes
1.6 WEBES Known Issues
Workaround
If you run out of disk space, check the WEBES output log files. If the logging level has not been increased from WARNING to INFO or DEBUG, follow these steps:
1.Stop the Director and WCCProxy (see SEA User’s Guide section 2.3, “Processes”).
2.If the reason for the problem is not evident from the log files and you cannot resolve it, zip and send all the files in the specific/webes/logs and specific/wccproxy/logs directories to WEBES support.
3.Delete all the files in these directories.
4.Restart the Director and WCCProxy. If the log files continue to grow quickly with errors, then stop the Director and WCCProxy until you receive an answer from WEBES support.
1.6.1.7 WEBES Temporary Files Use Disk Space
At times, WEBES can write many or large temporary files to its installed directory tree, when it is working. The number and sizes of these files depend on the binary event log files and crash data files being processed by SEA and CCAT, respectively.
Workarounds:
1.To ensure that orphan temporary files no longer needed by WEBES are removed:
a.Stop the Director and WCCProxy (see SEA User’s Guide section 2.3, “Processes”).
b.Delete any files in the WEBES installed directory tree within any directory named “temp”, such as specific/ca/temp.
c.Restart the Director and WCCProxy.
2.To reduce the amount of SEA automatic analysis being performed on the system, perform the steps under #1 above. Before restarting the Director and WCCProxy, clean the system’s binary event log as described in WEBES Install Guide section (for the specific operating system) “Archiving and Cleaning the Error Log”.
3.Do not leave SEA Web interface sessions running when they are not in use. Closing the Web browser that is connected to your SEA Web interface allows cleaning up of temporary files after sometime.
Future WEBES releases will manage and limit their temporary file storage needs.
1.6.1.8 Backward Compatibility
Connections between systems that are running different versions of WEBES (including different dot releases or Service Paks) may produce unpredictable results. This can happen if, for example, you are running your locally installed SEA, and then use it to add and analyze a remote node that has another version installed.
Rev. 9/8/06