Unable to create cluster

Unable to create cluster

The customer is doing a new install and can not get the cluster working.

Customer gets the error: Unable to invoke insertIntoCluster

How can we delete the cluster by hand and start over?


Helped customer remove cluster by hand by:

1) Shut down the stoneware servers (loaders)
2) Delete /stoneware/config/defaultloaderdefaultprofile  (or whatever name it is based on the name of the loader and profile)
3) Backup the /stoneware/stonewareloader.xml file
4) Edit the /stoneware/stonewareloader.xml and remove the <service name="cluster"> </service> section, as well as the 2nd <loader> </loader> section.

Do the same thing on every other stoneware server that participated in the cluster.

Start webNetwork up and create the cluster on server #1
Once that is working, join the existing cluster on server #2

The customer originally made a mistake in ip addresses when creating the cluster and that confused things and required a manual delete of the cluster and then starting over.



UPDATE: do to a bug in the cluster join code you may have to follow the following steps :

Here are the steps we had to go through to re-create the cluster last time.

·         Create node 0 on server #1

·         Down Server #1, start up

·         Join server #2 into cluster.

·         It will fail saying cluster was not configured.

·         Go to Node 0 and FORCE REMOVE server #2

·         Go back to Server #2 and join cluster again

·         It will show that the cluster config LIKE it joined, but is has no host ID

·         Click LEAVE to leave the cluster

·         Go to Node 0 and FORCE REMOVE server #2

·         Down Server #2

·         Delete the cluster folder in the \config directory on Server #2

·         Start it back up

·         Join cluster and it will work.

·         Now do the same for Server #3

·         Join server #3 into cluster

·         It will fail saying cluster was not configured

·         Go to Node 0 and FORCE REMOVE server #3

·         Go back to Server #3 and join cluster again

·         It will show that the cluster config LIKE it joined, but is has not host ID

·         Click LEAVE to leave the cluster

·         Go to Node 0 and FORCE REMOVE server #3

·         Down Server #3

·         Delete the cluster folder in the \config directory on Server #3

·         Start it back up

·         Join cluster and it will work.

We used the short name for the cluster addresses, versus the FQDN or IP.

    Can't find the KB

    Unable to find the KB to address your issue ?  

      • Recent Articles

      • Change Reset Password Button Text

        Change the text of the "Reset Password" button on the UW Login Page How to change the text of the Reset Password button on the Login Page. Login to webNetwork and open webAdmin on your Relay Central Server Expand Customization Center Expand Tenants ...

      • Remove Reset Password Button From Login Page

        Remove the Reset Password Button from the Login Page How to remove the Reset Password button from the Unified Workspace login page. Login to webNetwork and open webAdmin on your Relay Central Server Expand Customization Center Expand Tenants Expand ...

      • Lenovo Unified Workspace End-of-Life Questions and Answers

        As of January 31st 2024, Lenovo Unified Workspace (formerly Stoneware WebNetwork) is no longer supported. This means that we no longer provide licenses, downloads, updates, patches, or technical assistance for this product. If you have any questions ...

      • How do I determine my Unified Workspace license expiration date?

        The best method for determining the licensing information including the expiration date of your Unified Workspace license: Login to your 8090 management console on each server This may take remoting into each LUW server and relay, opening a browser, ...

      • Lenovo Unified Workspace 7.0.2.13 Released

        Highlights of Unified Workspace 7.0.2.13 Before you install: Please view the installation notes here. 7.0.2.13 requires a 7.0 license file. Below is a list of enhancements and fixes released in Unified Workspace 7.0.2.13 Fixed external storage ...

      • Related Articles

      • How to Create a Cluster.

        After 6.3.0.232 we have added features to our clustering services that allow for rolling upgrades, and faster clustering startups for larger customers. If Clustering is currently enabled you will want to use the instructions here for removing the ...

      • Time Sync causing Cluster Issues

        Issue: The customer is having issues with the cluster going out of sync causing various issues. Examples: webRDP giving and Unknown Error Users unable to authenticate UW just running slowly in general Customer will rebuild the cluster, only to have ...

      • Cluster Traffic

        Clustering is used to maintain the state of the user’s session information so that multiple relays can share the same session information. When a user logs in, their session id is sent to each node of the cluster. A session id is 36 characters. There ...

      • Unable to select swExternal-users context for Registration

        Unable to select swExternal-Users context for Registration under the relay’s Authentication options.   We can’t browse two directories for that feature, so we have the External Directory excluded, which is why it is grayed out.  You can work around ...

      • Unable to update schema

        The customer is a doing new install and can not perform wizard #2 when using Active directory. Customer turned on com.stoneware.service.directoryManager.schema debug and got the following error:  FATAL (04/29) 10:58:32 ...