Troubleshooting
Use the following tips for help with job management:
- I get the following permission enforcement warning when I monitor a job:
-
Permission enforcement is enabled for this organization, but the following Data Collectors do not support it: <Data Collector URL>
- A job fails to start with the following error message:
-
Number of instances: <number> are more than number of matching Data Collectors: <number>
- A job has a red active status and displays the following message in the job details:
-
JOBRUNNER_72 - Insufficient <execution engine type> resources to run job. All matching <execution engine type> [<URLs>] have reached their maximum CPU usage limits.
- One of the remote pipeline instances run from my job has stopped. How can I view the logs for that pipeline?
- When you monitor an active job, you can view the Data Collector or Transformer log to review log messages for pipelines running on the execution engine. For details, see Logs.
- A Data Collector engine has suddenly lost its connection to Control Hub. What happens to the currently active jobs on that engine?
- When a Data Collector engine running a pipeline loses its connection to Control Hub, the engine continues to remotely run the pipeline, temporarily saving the
pipeline status and last-saved offset in data files on the engine machine.
If the engine reconnects to Control Hub before the maximum engine heartbeat interval expires, the engine reports the saved pipeline data to Control Hub. No data loss nor data duplication occurs.
If the maximum engine heartbeat interval expires before the engine reconnects to Control Hub, Control Hub considers the engine unresponsive. Control Hub handles jobs on unresponsive engines based on whether pipeline failover is enabled for the job. For details, see Jobs and Unresponsive Data Collector Engines.