How to Setup a Clustered Node

Related Documentation: • Cluster Manager How-to

Last Updated for InterWorx version 2.1.0

• Fully configured Cluster Manager
• Node must be running InterWorx-CP 2.1.0 or greater
• Node must have 1 IP address
• Node must be on the same physical network segment as the Cluster Manager
• Node must not have any SiteWorx accounts
• InterWorx-CP server must be running CentOS 4 or above

The purpose of this how-to is to walk you through the process of setting up a new node on an InterWorx-CP cluster.

1. Click on the Clustering menu if it is not already expanded.
2. Click on the ♦    Setup item.
3. You should now be looking at the Cluster Management :: Setup controls in the main content area.
4. Click the Setup button under InterWorx-CP Clustered Server to begin the process
5. Copy the API key text blob to your local clipboard as you will need the copied API key for the next step
6. Proceed to the Adding Clustered Node to Cluster Manager step

1. Click on the Clustering menu if it is not already expanded.
2. Click on the ♦    Nodes item.
3. You should now be looking at the Cluster Management :: Node Management controls in the main content area.
4. Enter the hostname or IP address of the Node you are adding to the hostname field.
5. Enter the API key from the previous procedure into the Node API Key field.
6. It is recommended that you test your setup using the Test button. Doing a pre-addition test weeds out 90% of Node addition errors that can occur.
7. After a successful test run (denoted by the message: >> Node passed all pre-cluster tests) press the Add button to complete the node addition.
8. The add will return with either: >> Node added successfully or an error regarding what happened. Please check the troubleshooting guide below for general solutions to common errors.

• Both boxes must be on the same physical network segment. If you get the error: >> not on same physical network segment please check that the boxes are in fact on the same segment. Boxes with similar IP addresses may not be on the same segment depending on how your IP network is architected.
• Clustered Nodes must be running a version of InterWorx-CP which is 2.1.0 or greater, please verify that all nodes have at least InterWorx-CP 2.1.0.
• If you use a hostname for the Node instead of an IP address be sure that the hostname is resolable from the Cluster Manager itself. It is not enough that you can resolve it from your local PC. Login to the Cluster Manager and verify that you can “ping” the hostname from the Manager.
• Clustered Nodes must be clear of all SiteWorx accounts before adding, if you get an error regarding the new Node not being empty just delete all SiteWorx accounts from the Node before proceeding.
• If the Node addition fails for any reason, it is often helpful to look at the InterWorx-CP logfile located at /usr/local/interworx/var/log/iworx.log. You can often grep this file for the term “node” to get a list of what happened during Node addition. This goes for both the Cluster Manager and the Node being added.

• >> Node already exists - There is a Node already known to the Cluster Manager that has the same hostname or IP address. Verify that you haven’t added the same Node twice to the Cluster Manager.
• >> Invalid node hostname - The hostname provided doesn’t appear to be valid nor does it resolve to an IP address. Verify that it’s the hostname you meant and that it’s resolvable to an IP from the Cluster Manager.
• >> Could not resolve hostname - The hostname given isn’t resolvable to an IP address from the Cluster Manager. Verify that it’s resolvable to an IP from the Cluster Manager before proceeding.
• >> Node not on same physical network segment - The new Node isn’t on the same physical network segment. This error is inferred from your IP configuration on the Cluster Manager (IP address, netmask etc) so it may either be that your IP configuration is incorrect or that in fact the boxes aren’t on the same segment.
• >> API Failure - This may be due to the Node not being InterWorx-CP 2.1.0 or above.
• >> Node is already clustered - The Node that you’re trying to add is already setup for clustering either with this Cluster Manager or another. You must un-cluster the Node before proceeding to re-cluster it on the current Manager.
• >> Node already has SiteWorx accounts present - The node has SiteWorx accounts present on the box. You must remove the accounts before proceeding with clustering.