...
JobScheduler Master Log Files in Detail
| Anchor | ||||
|---|---|---|---|---|
|
scheduler.logThe Debug Log is created:
...
- Column 1: Starts with "." if demo version, Day of Month
- Column 2: Time (with ms)
- Column 3: application name (Windows) - empty otherwise
- Column 4: elapsed time in ms
- Column 5: Process ID, ".", Thread ID (hex)
- Column 6: Used memory in MB (Windows) - empty otherwise
- Column 7: Log text
| Anchor | ||||
|---|---|---|---|---|
|
scheduler-<yyyy-mm-dd-hhmmss>.<scheduler-id>.logThe Main Log is created:
- during JobScheduler startup.
- when log rotation is performed.
- by all types of JobScheduler instances, i.e. Standalone, Active Cluster, Passive Cluster, Agent, not applicable for new JobScheduler Universal Agent .
- with the file name
scheduler-<yyyy-mm-dd-hhmmss>.<scheduler-id>.logwhere<yyyy-mm-dd-hhmmss>states the timestamp when the log was started.<scheduler-id>states the JobScheduler instance identification that has been specified during installation. If multiple JobScheduler instances store log files to a common log folder then this is helpful to identify the log file of a specific JobScheduler instance.
...
In Addition to being read from the file System, the a number of JobScheduler log files can be viewed by JOC Cockpit users:
- The main and debug logs for a JobScheduler Master (scheduler-<yyyy-mm-dd-hhmmss>.<scheduler-id>.log and scheduler.log respectively) can be downloaded
...
- from the JOC Cockpit's Dashboard view by JOC Cockpit users with permissions to view the JobScheduler Status widget in the Dashboard.
Note that log files can only be accessed in this way when the JobScheduler Master in question does not have the status unreachable.
...