System Event Analyzer
2.3 SEA Known Issues
If WEBES is upgraded, or uninstalled (saving configuration data) and later installed, then the
recovered WCCPROXY.REG file in {installed directory}/specific/wccproxy/config containing
the old hostname can cause WEBES to send no notifications other than to the SEA Web interface. To correct this, after upgrading or installing WEBES, remove the following line from WCCPROXY.REG beginning with:
WCCProxy.owner=
Then stop both the Director and the WCCProxy, and restart both.
2.3.3.4 Cannot Activate a Running Node
If you cannot activate a node that is currently running, it may be too busy to respond. Click on the "Activate Node" entry in the navigation tree later, which may activate the node. If you suspect that the Director process is not running on that node, you can verify it by issuing the
command on that node.
2.3.3.5 High Volume of Events Hangs Interface
If you are viewing the Events tab on the
To clear the condition, click Refresh in your browser, or close the browser and
2.3.3.6 Frame Opens in New Window
If you click on different areas of the web interface quickly while it is updating, a frame may appear in a new window. Close the window and
2.3.3.7 Null-Pointer Errors
If a NullPointerException error occurs while using the web interface, click your browser's Refresh button. If you continue using SEA without refreshing, you may encounter additional errors or unexpected behavior.
2.3.3.7.1 Null-Pointer Errors from Large Log Files
In some cases, if you add an Other Log to the web interface for manual analysis and click on it to analyze it, a
Rev. 9/8/06
