Skip to end of metadata
Go to start of metadata

Introduction

The Controller's journal holds information about scheduling objects such as workflows, jobs and orders:

  • scheduling objects are deployed from JOC Cockpit to a Controller.
  • orders are submitted to indicate the start time of workflows.

The Controller's journal is available from a number of files in the following location:

  • Unix: /var/sos-berlin.com/js7/controller/state
  • Windows: C:\ProgramData\sos-berlin.com\js7\controller\state
  • Users can choose different locations when setting up a Controller.

When a Controller's journal is deleted or damaged then this indicates severe loss:

  • Consider that loss of a Controller's journal means that:
    • any scheduling objects such as workflows have to be re-deployed,
    • any orders of the Daily Plan have to be re-submitted,
    • any currently running orders are lost and no information about orders and the execution status of jobs is available.
  • See also the JS7 - FAQ - What happens to workflows in case of outage of a Controller? article.
  • The use of a Controller cluster will leverage such a situation as the standby Controller instance operates a synchronized copy of the journal. The standby Controller instance will pick up operations immediately during fail-over after 3-5s. The failed Controller instance can then be started later on and will automatically synchronize with the then active Controller instance.

Initial Operation

Issues occurring during initial operation are described in the JS7 - How to troubleshoot Controller Cluster Initial Operation article.

Ongoing Operation

The scenarios in this section apply after a Controller has been successfully registered with JOC Cockpit during JS7 - Initial Operation.

Loss of Controller Journal

  • ProblemIf initial operation has been successfully completed for a Controller and due to some weird reason the Controller instance's journal is deleted later on then the Controller has to be registered once again from the JOC Cockpit. 
  • SolutionThis problem can be resolved by restarting the Controller. The Controller will start a new journal. In the JOC Cockpit "Manage Controllers/Agents" page use the "Edit" action menu of the Controller and submit the same settings as before. This operation will connect the JOC Cockpit to the Controller. Registration of existing Agents is automatically repeated. Then redeploy any scheduling objects to the Controller from the JOC Cockpit Configuration view.
  • Implication: This operation does not recover information about past job executions which have not yet been added to the JOC Cockpit history.

Damage to Controller Journal

There is no difference between in troubleshooting damage to a Controller Journal the loss of a Controller journal as described in the previous section, except for the fact that users should remove the journal files from the JS7_CONTROLLER_DATA/state directory before starting the Controller instance.


Write a comment…