Page History

...

• If a Controller was connected to the Agent then the Controller will know the respective orders and status information.
• If no Controller was connected to the Agent for some time then there is no way in knowing what jobs have been executed by the Agent for the time between the connection loss with the Controller and loss of the Agent's journal.
  • The Agent's agent.log file holds information about orders and jobs being processed.
  • For each job a pair of temporary files for output to the stdout and stderr channels is created in the Agent's JS7_AGENT_DATA/tmp directory. These files are dropped after job execution if the Agent can report back execution results to a Controller and otherwise remain in place.

...

• Problem: Assume that initial operation is successfully completed for an Agent and due to some weird reason the Agent's journal later on is damaged. This may fail the coupling between Controller and Agent.
  • The JOC Cockpit will report the Agent status "Coupling failed" or "Shutdown". When hovering the Agent status with the mouse then the full error message will be displayed, for example
    • AgentNotDedicated: This Agent has not been created yet.
• Solution: This problem can be resolved by removing any files in the Agent's .JS7_AGENT_DATA/state directory. At the point in time of Agent restart the JOC Cockpit and the Controller have to be active and connected. In case that the problem to couple the Agent persists, then re-register the Agent from the JOC Cockpit using the "Edit" action menu and submitting the same settings for the Agent.
• Implication: This operation includes to loose information about past job executions that have not yet been added to the JOC Cockpit history.

...