You are viewing limited content. For full access, please sign in.

Question

Question

Error: Node with address X, could not be registered because it is registered to a Scheduler with address X.

Distributed Computing Cluster
Updated September 2, 2014
asked on July 10, 2014

 I am trying to add worker to a DCC cluster and am recieving the error that the address is already assigned. Cluster is setup, using web admin console, with a different machine as scheduler with 3 other nodes currently working.  Previously, the license for this node has been erased and recreated after a different error.  The application has been uninstalled and reinstalled as a worker.  This machine was originally set up as a scheduler in error.

 

Has anyone come accross something like this in setting up DCC?

 

 

0 0

Answer

SELECTED ANSWER
replied on July 10, 2014 • Show version history

This is a known bug that we're working on fixing. It happens because the config files that existed from when you installed the Scheduler on that machine are still present. For now, the workaround is to delete the files in C:\Program Files (x86)\Laserfiche\Distributed Computing Cluster\Config and restart the DCC service, either in Services or with Restart-Service LfDCC.

1 0

Replies

You are not allowed to reply in this post.
replied on July 10, 2014

On the computer that you are trying to add as a worker, please go into C:\Program Files (x86)\Laserfiche\Distributed Computing Cluster\Config and check to see if you have the file ServiceConfig.xml. If you do, then delete that file and restart the Laserfiche Distributed Computing Cluster Service. Now see if you can add the worker.

replied on July 10, 2014

Deleting ServiceConfig.xml won't do it. The specific files that need to be deleted are NodeConfig.xml, SchedulerConfig.xml, SchedulerRole.txt, and JobNumberFile.txt (or whatever subset of these exists). Restarting the service will then regenerate NodeConfig.xml such that it is not registered to a scheduler, and the other files won't be regenerated because they are scheduler specific and not needed by the worker.

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...