Page History
| Table of Contents |
|---|
Introduction
- Initial Operation is performed after installation of JS7 Controller, Agent and JOC Cockpit, see JS7 - Initial Operation
- In case there are issues while registering the Controllers then the Controller cannot orchestrate the job-related configuration to Agents. Also, the Controller is used for the execution of workflows that include jobs running on a number of Agents as switching of Agents during workflow execution is performed by the customer.
Troubleshooting
On After registering the Controller the its status of the Controller can be checked either from the JOC Cockpit from the JS7 - Dashboard. While registering a Controller the following issues can be faced:
...
When registering a Controller a number of misconfigurations can occur.
Operations to register a Controller are performed from the JOC Cockpit page "Manage Controllers/Agents" that is available from the user menu in the right upper corner of the GUI. Administrative permissions are required to be able to see and to use this page.
User Errors
Same Controller is used as a Standalone Controller and as a member of a Controller Cluster
...
- Problem:
...
- Assume that the JOC Cockpit
...
- uses a Controller registered as a Standalone Controller
...
- . If the same Controller is
...
- registered as a Controller Cluster member then the JOC Cockpit throws an error such as
JocObjectAlradyExistException: com.sos.joc.exceptions.JocObjectAlreadyExistException: Controller(s) with id 'controller' already exists
...
- This error message is available from the JOC Cockpit's log file too, e.g. from the
JS7_JOC_DATA/logs/joc.logfile, see JS7 - Log Files and Locations.
- This error message is available from the JOC Cockpit's log file too, e.g. from the
- Solution:
...
- It is not possible
...
- to register the same Controller
...
- twice, as a Standalone
...
- Controller and as a Controller cluster.
Users who wish to migrate their Standalone Controller to a Controller
...
Cluster should consider the following proceeding:
- Check that you have a license key ready as the clustering for Controllers is available for a commercial license, see JS7 - Licensing.
- Verify that execution of workflows is completed with the Standalone Controller and that no orders are running.
- Remove the Standalone Controller from the JOC Cockpit GUI.
- Shutdown the Standalone Controller and remove the Controller's journal files in its
JS7_OONTROLLER_DATA/Statedirectory. - Follow the steps from the JS7 - Initial Operation for Controller Cluster article.
- Redeploy the scheduling objects such as workflows from JOC Cockpit to the Controller Cluster.
Controller Instances with different Controller IDs are used as a Controller Cluster
...
- Problem: : If
...
- a Controller Cluster is registered with
...
- its Controller instances using different Controller IDs then this will raise an error:
as joc
...
.log ControllerInvalidResponseDataException:com.sos.joc.exceptions.ControllerInvalidResponseDataException: The cluster members must have the same Controller Id: http://<host1>:
...
<port1> -> controller_ID1, HTTP://<host2>:<port2> -> controller_ID2.- This error message is available from the JOC Cockpit's log file too, e.g. from the
JS7_JOC_DATA/logs/joc.logfile, see JS7 - Log Files and Locations.
- Solution:
...
- It is not possible to register
...
- Controller instances with different Controller
...
- IDs to work as a Controller Cluster
...
- . Instead check which Controller instance uses the wrong Controller ID and rerun the installation. During installation the Controller ID can be specified, see JS7 - Controller Installation On Premises and JS7 - Controller Installation for Docker Containers.
License missing when configuring the Controller Cluster
...
- Problem:
...
- Use of a Controller Cluster requires a license, see JS7 - Licensing. It is not possible to
...
- configure a Controller Cluster
...
- without
...
- license keys being in place with both Controller instances. In case that the license is missing from
...
- a Controller instance while configuring
...
- the cluster the following error is raised:
js7.common.system.startup.JavaMain - No license for js7.controller.cluster js7.base.problem.ProblemException$NoStackTrace: No license for js7.controller.cluster.
...
- This error message is available from the Controller instance's log file too, e.g. from the
JS7_CONTROLLER_DATA/logs/controller.logfile, see JS7 - Log Files and Locations.
- This error message is available from the Controller instance's log file too, e.g. from the
- Solution: Install both Controller instances with a license key, see JS7 - Controller Installation On Premises and JS7 - Controller Installation for Docker Containers. Alternatively add the license key as explained by the JS7 - Initial Operation for Controller Cluster article. Find additional information from the JS7 - FAQ - How to apply a JS7 License Key
...
- article.
Further Information
For troubleshooting during ongoing operation see JS7 - How to troubleshoot Controller journals
Overview
Content Tools