Troubleshooting

This chapter describes troubleshooting tips for some of the problems that you may encounter while using the LocalDirector User Interface. It is divided into the following sections:

General Tips and Techniques

This section offers starting points for understanding changes in the behavior of the system. Check these items before calling your support representative.

All Windows systems installations require that you have the TEMP environment variable set to a valid directory. If you encounter installation problems, check that the system TEMP environment variable is properly set.

Windows 98 Uninstallation and Installation

If you uninstall and reinstall the LocalDirector User Interface client on a Windows 98 system and use the Microsoft Internet Explorer, you must reboot the client machine after the uninstallation, then install the LocalDirector User Interface client and reboot the client machine again.

General Environment

This section lists simple guidelines:

Test the version of a LocalDirector User Interface server by entering the gwserver -v command.
For best viewing capabilities on Windows systems, ensure that your Display Properties screen area is set to 1024 x 768 pixels.

If the LocalDirector User Interface Detaches from the LocalDirector

If the LocalDirector User Interface cannot synchronize with an attached LocalDirector, it detaches from the LocalDirector. In such instances, you must resolve the inability to synchronize, then reattach the LocalDirector to a LocalDirector User Interface configuration, as described in the chapter "LocalDirector User Interface Advanced Configurations."

Looking for Warning and Error Messages on Windows NT Systems

To view warning and error messages on Windows NT systems, check the Event Viewer. Click the Start button, go to the Programs submenu, then go to the Administrative Tools submenu, and select Event Viewer. The LocalDirector User Interface events are recorded as Application events, rather than System events (see the File menu). Filters can be used to single out specific LocalDirector User Interface errors or event types under the View menu.

Using Netscape Communicator with LocalDirector User Interface

If you have problems running Netscape Communicator with the LocalDirector User Interface, perform the following tasks, as necessary:

If you cannot access the LocalDirector User Interface from the client Netscape browser, check the proxy and security settings of the browser. See your network administrator for assistance, if necessary.
If you do not see installation instructions on the browser page when installing the LocalDirector User Interface client, open the Edit menu, choose the Preferences option, and select Fonts. If the Variable Width Font value is set to Times (Adobe), change this value to another font.

Standard Troubleshooting

During normal operation, the LocalDirector User Interface produces four types of messages: SNMP traps, Information, Warning, and Error. The following sections describe these messages and provide brief descriptions of possible courses of action in response to them.

Note For SNMP messages, the LocalDirector User Interface generates additional information (variable bindings) in the case of probe failure, warning, and recovery. These variable bindings contain the following information for the SNMP manager: Real name, IP address, Port number, Protocol, and Severity.

SNMP Traps

The LocalDirector User Interface supports the following SNMP traps:

warmStart
LocalDirector User Interface-specific traps

The LocalDirector User Interface-specific traps include:

lui-internalFault
lui-osFault
lui-runtimeFault
lui-invalidTFTPRequest
lui-probeFailure
lui-probeWarning
lui-probeRecovery
lui-configurationWarning
lui-TFTPshutdown
lui-probeConnectFailureWarning

Informational Messages

Informational messages provide information about the LocalDirector User Interface. You need not do anything in response to the occurrence of these messages. Table A-1 lists the LocalDirector User Interface informational messages.

Table A-1: Informational Messages

Message Description

LUI 3.1 Web Server started

The server has been started.

LUI 3.1 Web Server shutdown

The server was halted.

Password change successful

The password was changed successfully.

Probe execution halted by exception: {Msg}

The LocalDirector User Interface server has halted the probe execution, shown in Msg. This message indicates a problem with the LocalDirector User Interface product. If you receive this message, contact your LocalDirector User Interface support representative.

PROBE SUCCESS: Activating deactivated real server real server name due to success of probe probe name

A previously deactivated real server (one deactivated due to a failed probe) has been reactivated.

PROBE SUCCESS: Probe probe name succeeded in testing real server real server name

A probe run succeeded.

Shutdown of TFTP server requested

You have purposely shut down the TFTP server, where the TFTP server is the LocalDirector User Interface server itself.

TFTP connection aborted due to exception: {Msg}

The LocalDirector User Interface server has halted the TFTP connection, shown in Msg. This message indicates a problem with the LocalDirector User Interface product. If you receive this message, contact your LocalDirector User Interface support representative.

Message	Description
LUI 3.1 Web Server started	The server has been started.
LUI 3.1 Web Server shutdown	The server was halted.
Password change successful	The password was changed successfully.
Probe execution halted by exception: {Msg}	The LocalDirector User Interface server has halted the probe execution, shown in Msg. This message indicates a problem with the LocalDirector User Interface product. If you receive this message, contact your LocalDirector User Interface support representative.
PROBE SUCCESS: Activating deactivated real server real server name due to success of probe probe name	A previously deactivated real server (one deactivated due to a failed probe) has been reactivated.
PROBE SUCCESS: Probe probe name succeeded in testing real server real server name	A probe run succeeded.
Shutdown of TFTP server requested	You have purposely shut down the TFTP server, where the TFTP server is the LocalDirector User Interface server itself.
TFTP connection aborted due to exception: {Msg}	The LocalDirector User Interface server has halted the TFTP connection, shown in Msg. This message indicates a problem with the LocalDirector User Interface product. If you receive this message, contact your LocalDirector User Interface support representative.

Warning Messages

If you receive one of the following warning messages, read the accompanying description to try to resolve the problem. Contact your support representative for further information. Table A-2 lists the LocalDirector User Interface warning messages.

Table A-2: Warning Messages

Message Description

COULD NOT EXECUTE PROBE: probe probe name could not be executed while testing real server real server name

You may get this message if the LocalDirector User Interface probe cannot establish a connection with the real server host system. You should ensure that the connection is a valid one.

If the connection is valid, do not perform additional action in response to this message. It is expected that LocalDirector will handle this instance.

COULD NOT EXECUTE STEP: Step stepname of probe probename could not be executed while testing real server real server name

This message indicates that the probe step has failed and the LocalDirector User Interface has been set up to allow the probe to continue despite the step failure. Do not perform an action in response to this message. It is expected that LocalDirector will handle this instance.

Couldn't save the configuration of LocalDirector {LocalDirector name}. Error is {Msg}.

This message indicates that an attempt to execute a write memory command on the specified LocalDirector failed.

Check the detailed error message for information regarding the specific reason.

Error attempting to read the states of servers on LocalDirector {LocalDirector name}. Reason is: Timed out reading data from LocalDirector.

You may get this message if the client is unable to connect to the LocalDirector and the LocalDirector User Interface times out before a connection can be established.

Lost connection to LocalDirector over serial port port; this may cause lost synchronization with UI. Please do synchronization.

Synchronize LocalDirector User Interface with LocalDirector.

Password not valid

Enter correct password.

Step step name of Probe probe name failed while testing real server real server name

You may get this message if the probe has failed and the LocalDirector User Interface has been set up to allow probe failures.

Edit the probe and inspect the steps.

Use the messages in the Probe Details popup window to diagnose the problem with your Web server.

The LocalDirector version version is not supported.

The LocalDirector User Interface supports only LocalDirector version 3.1.x.

The port specified port is invalid. Defaulting to port default port.

Specify a valid port number.

The requested IP address ip is not valid for this machine.

Specify a valid IP address.

The requested network port port is unavailable.

Check the configuration to learn if another process is already running, using that port.

If you are running on a UNIX system, and you have specified a network port less than 1024, ensure that you are running as the root user.

Web Server could not listen on ip at port port, because it does not have permission to acquire the port.

If you are running on a UNIX system, and you are connected to a network port less than 1024, ensure that you are running as the root user.

Message	Description
COULD NOT EXECUTE PROBE: probe probe name could not be executed while testing real server real server name	You may get this message if the LocalDirector User Interface probe cannot establish a connection with the real server host system. You should ensure that the connection is a valid one. If the connection is valid, do not perform additional action in response to this message. It is expected that LocalDirector will handle this instance.
COULD NOT EXECUTE STEP: Step stepname of probe probename could not be executed while testing real server real server name	This message indicates that the probe step has failed and the LocalDirector User Interface has been set up to allow the probe to continue despite the step failure. Do not perform an action in response to this message. It is expected that LocalDirector will handle this instance.
Couldn't save the configuration of LocalDirector {LocalDirector name}. Error is {Msg}.	This message indicates that an attempt to execute a write memory command on the specified LocalDirector failed. Check the detailed error message for information regarding the specific reason.
Error attempting to read the states of servers on LocalDirector {LocalDirector name}. Reason is: Timed out reading data from LocalDirector.	You may get this message if the client is unable to connect to the LocalDirector and the LocalDirector User Interface times out before a connection can be established.
Lost connection to LocalDirector over serial port port; this may cause lost synchronization with UI. Please do synchronization.	Synchronize LocalDirector User Interface with LocalDirector.
Password not valid	Enter correct password.
Step step name of Probe probe name failed while testing real server real server name	You may get this message if the probe has failed and the LocalDirector User Interface has been set up to allow probe failures. Edit the probe and inspect the steps. Use the messages in the Probe Details popup window to diagnose the problem with your Web server.
The LocalDirector version version is not supported.	The LocalDirector User Interface supports only LocalDirector version 3.1.x.
The port specified port is invalid. Defaulting to port default port.	Specify a valid port number.
The requested IP address ip is not valid for this machine.	Specify a valid IP address.
The requested network port port is unavailable.	Check the configuration to learn if another process is already running, using that port. If you are running on a UNIX system, and you have specified a network port less than 1024, ensure that you are running as the root user.
Web Server could not listen on ip at port port, because it does not have permission to acquire the port.	If you are running on a UNIX system, and you are connected to a network port less than 1024, ensure that you are running as the root user.

Error Messages

Table A-3 lists the LocalDirector User Interface error messages.

Table A-3: Error Messages

Message Description

Can't connect to LocalDirector on host host (reason: {Msg})

This message indicates that the LocalDirector User Interface server could not connect to the LocalDirector via a Telnet connection.

Check the detailed error message for information regarding the specific reason.

Verify Telnet connectivity between the LocalDirector User Interface server and the LocalDirector.

Can't connect to LocalDirector using serial port {port} (reason: {Msg})

This message indicates that the LocalDirector User Interface server could not connect to the LocalDirector via a serial cable connection.

Check the detailed error message for information regarding the specific reason.

Verify serial cable connectivity between the LocalDirector User Interface server and the LocalDirector.

Can't send data to LocalDirector on host host (reason: {Msg})

This message indicates that the LocalDirector User Interface server could not communicate with the LocalDirector via a Telnet connection.

Check the detailed error message for information regarding the specific reason.

Verify Telnet connectivity between the LocalDirector User Interface server and the LocalDirector.

Can't send data to LocalDirector using serial port port (reason: {Msg})

This message indicates that the LocalDirector User Interface server could not communicate with the LocalDirector via a serial cable connection.

Check the detailed error message for information regarding the specific reason.

Verify serial cable connectivity between the LocalDirector User Interface server and the LocalDirector.

Could not connect to LUIServer on host {host} at port {port}.

This message indicates that the client has lost contact with the LocalDirector User Interface server.

Restart the LocalDirector User Interface server.

Could not connect to LocalDirector at address {address}. Timed out reading data from LocalDirector.

You may get this message if the client is unable to connect to the LocalDirector and the LocalDirector User Interface times out before a connection can be established.

Error attempting to read the states of servers on LocalDirector LocalDirector name. Reason is: The specified administrator password was not accepted by the LocalDirector.

This message indicates that the administrator password on LocalDirector User Interface is not the same as that for LocalDirector. Make these two passwords the same.

Error attempting to read the states of servers on LocalDirector LocalDirector name. Reason is: The specified telnet password was not accepted by the LocalDirector.

This message indicates that the Telnet password on LocalDirector User Interface is not the same as that for LocalDirector. Make these two passwords the same.

[INTERNAL ERROR] {Error}: {Msg}

Contact your support representative.

No network resources are available. Could not create a socket.

Contact your system administrator to increase system resources.

PROBE FAILURE: Deactivating real server real server name due to failure of probe probe name in step step name.

Check the probed real server.

Check server log messages for the real server.

Check the probe steps to ensure they are properly configured.

PROBE SCHEDULER ERROR: The real server real server name can not be put out of service: {Msg}

PROBE SCHEDULER ERROR: The real server real server name cannot be put in service: {Msg}

These messages indicate that an attempt by the LocalDirector User Interface to tell the LocalDirector to change the state of a real server after a probe success or failure failed.

Check the detailed error message for information regarding the specific reason.

Runtime Error: Msg

This message may indicate a LocalDirector User Interface internal error or system configuration problem.

Contact your support representative if you cannot remedy the problem.

The command line option Msg is invalid.

Respecify the gwserver command with the correct argument.

The network could not be initialized.

The process could not create a thread.

Contact your system administrator to increase system resources.

The process failed to resolve the address of the TFTP server host

This message indicates that the TFTP server host specified in the LUI server properties dialog could not be resolved to an IP address.

Check that the specified host name is valid and has a DNS entry accessible from the LUI server.

The process is out of memory.

Check your system configuration and free up system memory.

Timed out reading data from LocalDirector.

You may get this message if the LocalDirector is taking too long to respond.

Time out communicating with LocalDirector; this may cause lost synchronization with UI. Please do synchronization.

Synchronize LocalDirector User Interface with LocalDirector.

Unable to allocate socket for TFTP server: Msg

You may get this message if the TFTP server received a badly formed request.

Check the network cable connectivity.

Check the network for other program attempts to access the port to which the LocalDirector User Interface server is currently connected.

Unable to bind socket for TFTP server: Msg

You get this message if the TFTP server is listening on an unavailable IP address and port pair.

Change the IP address or port number.

Unable to create thread for TFTP server: {Msg}

You may get this message when the TFTP server is first started.

Contact your system administrator to increase system resources.

Unable to listen for connections on the selected port due to a network failure.

Contact your system administrator.

TFTP: error receiving request Msg

TFTP: received invalid datagram: packet too large.

TFTP: received invalid datagram: packet too small.

For these three messages, a client is making an improper request of the TFTP server.

Check the specified TFTP server port.

Check that the TFTP server port is receiving TFTP traffic. It should not receive non-TFTP traffic. For example, if you set the TFTP server to port 80, a Web browser trying to connect to that server, rather than a Web server, causes these TFTP errors.

Message	Description
Can't connect to LocalDirector on host host (reason: {Msg})	This message indicates that the LocalDirector User Interface server could not connect to the LocalDirector via a Telnet connection. Check the detailed error message for information regarding the specific reason. Verify Telnet connectivity between the LocalDirector User Interface server and the LocalDirector.
Can't connect to LocalDirector using serial port {port} (reason: {Msg})	This message indicates that the LocalDirector User Interface server could not connect to the LocalDirector via a serial cable connection. Check the detailed error message for information regarding the specific reason. Verify serial cable connectivity between the LocalDirector User Interface server and the LocalDirector.
Can't send data to LocalDirector on host host (reason: {Msg})	This message indicates that the LocalDirector User Interface server could not communicate with the LocalDirector via a Telnet connection. Check the detailed error message for information regarding the specific reason. Verify Telnet connectivity between the LocalDirector User Interface server and the LocalDirector.
Can't send data to LocalDirector using serial port port (reason: {Msg})	This message indicates that the LocalDirector User Interface server could not communicate with the LocalDirector via a serial cable connection. Check the detailed error message for information regarding the specific reason. Verify serial cable connectivity between the LocalDirector User Interface server and the LocalDirector.
Could not connect to LUIServer on host {host} at port {port}.	This message indicates that the client has lost contact with the LocalDirector User Interface server. Restart the LocalDirector User Interface server.
Could not connect to LocalDirector at address {address}. Timed out reading data from LocalDirector.	You may get this message if the client is unable to connect to the LocalDirector and the LocalDirector User Interface times out before a connection can be established.
Error attempting to read the states of servers on LocalDirector LocalDirector name. Reason is: The specified administrator password was not accepted by the LocalDirector.	This message indicates that the administrator password on LocalDirector User Interface is not the same as that for LocalDirector. Make these two passwords the same.
Error attempting to read the states of servers on LocalDirector LocalDirector name. Reason is: The specified telnet password was not accepted by the LocalDirector.	This message indicates that the Telnet password on LocalDirector User Interface is not the same as that for LocalDirector. Make these two passwords the same.
[INTERNAL ERROR] {Error}: {Msg}	Contact your support representative.
No network resources are available. Could not create a socket.	Contact your system administrator to increase system resources.
PROBE FAILURE: Deactivating real server real server name due to failure of probe probe name in step step name.	Check the probed real server. Check server log messages for the real server. Check the probe steps to ensure they are properly configured.
PROBE SCHEDULER ERROR: The real server real server name can not be put out of service: {Msg} PROBE SCHEDULER ERROR: The real server real server name cannot be put in service: {Msg}	These messages indicate that an attempt by the LocalDirector User Interface to tell the LocalDirector to change the state of a real server after a probe success or failure failed. Check the detailed error message for information regarding the specific reason.
Runtime Error: Msg	This message may indicate a LocalDirector User Interface internal error or system configuration problem. Contact your support representative if you cannot remedy the problem.
The command line option Msg is invalid.	Respecify the gwserver command with the correct argument.
The network could not be initialized. The process could not create a thread.	Contact your system administrator to increase system resources.
The process failed to resolve the address of the TFTP server host	This message indicates that the TFTP server host specified in the LUI server properties dialog could not be resolved to an IP address. Check that the specified host name is valid and has a DNS entry accessible from the LUI server.
The process is out of memory.	Check your system configuration and free up system memory.
Timed out reading data from LocalDirector.	You may get this message if the LocalDirector is taking too long to respond.
Time out communicating with LocalDirector; this may cause lost synchronization with UI. Please do synchronization.	Synchronize LocalDirector User Interface with LocalDirector.
Unable to allocate socket for TFTP server: Msg	You may get this message if the TFTP server received a badly formed request. Check the network cable connectivity. Check the network for other program attempts to access the port to which the LocalDirector User Interface server is currently connected.
Unable to bind socket for TFTP server: Msg	You get this message if the TFTP server is listening on an unavailable IP address and port pair. Change the IP address or port number.
Unable to create thread for TFTP server: {Msg}	You may get this message when the TFTP server is first started. Contact your system administrator to increase system resources.
Unable to listen for connections on the selected port due to a network failure.	Contact your system administrator.
TFTP: error receiving request Msg TFTP: received invalid datagram: packet too large. TFTP: received invalid datagram: packet too small.	For these three messages, a client is making an improper request of the TFTP server. Check the specified TFTP server port. Check that the TFTP server port is receiving TFTP traffic. It should not receive non-TFTP traffic. For example, if you set the TFTP server to port 80, a Web browser trying to connect to that server, rather than a Web server, causes these TFTP errors.

Table of Contents

Troubleshooting