HP Web-Based Enterprise Services 4.5 manual Linux Webes Issues, Director May Require Restart

Overall WEBES Release Notes

1.6 WEBES Known Issues

Workaround

•Define system PATH variable with some value (not null) before installing.

•Manually add WCCProxy path to PATH after installation.

1.6.2.14Windows Itanium Installation may interrupt if PATH variable is 256 characters or longer

In case of Windows Itatium, if the system PATH variable is 256 characters or longer then during the WCCProxy installation an error dialog box pops up “Failed to get PATH”. The reason behind is that, post installation the PATH variables only contains WEBES path.WCCProxy path is not added. As a result of this, WCCProxy commands like “wccproxy status” do not work.

Workaround:

•Remove junk entries from PATH.

•Manually add WCCProxy path to PATH after installation.

1.6.3 Linux WEBES Issues

These issues apply to WEBES on Red Hat Linux:

1.6.3.1 Director May Require Restart

If the system is configured to restart in graphical user interface mode (run level 5), the desta Director may not always automatically restart. For run level 5, always restart the Director manually after any type of system restart:

#desta start

Linux systems that restart in command-line mode (run level 3) correctly restart the desta Director automatically whenever the system restarts.

1.6.3.2 Segmentation Fault Error Message

If you had installed an ISEE Client containing WCCProxy 1.0, when installing WEBES you may see the following error message when the WCCProxy is stopped (so that it can be replaced with the newer version bundled in WEBES):

Stopping the WCCProxy.

/usr/sbin/wccproxy: line 122: 10052 Segmentation fault

Rev. 9/8/06

Web-Based Enterprise Services Release Notes 1–21