Troubleshooting the Server: Clusters

This topic covers some common issues you might face when creating Lotus^® Expeditor Server clusters.

Add-node command failure

When adding the initial node to the cell or when adding the clone node to the cell, the add node command fails occasionally. The addNode_out.log files currently only list the following:

add-node:
[wea-log-msg] 1/23/06 4:42 PM   INFO   add-node   
[wea-log-msg] CWPSF7001I Adding node fosswed2Node01 to cell

[wea-log-msg] 1/23/06 4:43 PM   ERROR   add-node   
[wea-log-msg] CWPSF7003E Failed to add node fosswed2Node01 to cell

You can find the accurate error information in the following file:

C:\Program Files\IBM\WebSphere\AppServer\profiles\default\logs\addNode.log

failAddNodeBecauseClocksNotInSync

The error message failAddNodeBecauseClocksNotInSync indicates that the Node and Dmgr clocks are more than 5 minutes apart. To synchronize the clocks with the GSA servers, do the following:

For Linux^®, type:
```
ntpdate internet_time_server_host
```
For Windows^®:
1. Click the clock.
2. Select the Internet Time tab.
3. Type the following:
```
internet_time_server_host
```
4. Click Update

unknownHostException shorthostname

The node must be able to connect to the Dmgr using the short name. If you are getting the error message, unknownHostException shorthostname, the Dmgr and node may be on different domains. You must include the other domain in the search path.

If you are using a Linux platform, add the domain to the /etc/resolv.conf file using the following syntax:

search raleigh.ibm.com rtp.raleigh.ibm.com

In Windows, add the domain to the search path in the TCP/IP properties.

Error when creating databases using the createDBs script

Verify that the database administrator passed to the script is a member of the DB2^® administrators group.

Troubleshooting Lotus Expeditor Server clusters

Add-node command failure

failAddNodeBecauseClocksNotInSync

unknownHostException shorthostname

Error when creating databases using the createDBs script