Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
- The location of the the log files is specified by the
log_dir
parameter in the${SCHEDULER_DATA}/config/factory.ini
file where${SCHEDULER_DATA}
is the JobScheduler data directory that has been specified during installation. The default location is the${SCHEDULER_DATA}/logs
folder. This setting should remain unchanged otherwise JOC Cockpit doesn't find the logs. If another directory is desired, then a symlink should be created (see next chapter).
Custom Log File Location
- Administrators are free to specify an alternative location for the JobScheduler log files. In this situation, to ensure that the JOC Cockpit is able to find the alternative log file location, we recommend that administrators do not change the
log_dir
parameter in thefactory.ini
file but create a SymLink pointing to the new log directory in place of the default folder specified by thelog_dir
parameter. The JOC cockpit will then look at the default log file location and follow the SymLink to the new location. - To Configure a Custom Log File location:
- Stop the JobScheduler Master (to allow the original
logs
folder to be moved/deleted/renamed) - Move/delete/rename the original
logs
folder - On Window: Open a command prompt window (with elevated Administrator rights)
- Navigate to the current location of the logs folder
- Enter:
mklink /D logs Target
- where
Target
is the new name/location (absolute or relative) of the logs directory
- where
- On Linux: Open a shell
- Navigate to the current location of the logs folder
- Enter:
ln -s "Target" logs
- where
Target
is the new name/location (absolute or relative) of the logs directory
- where
- Start the JobScheduler Master
- Stop the JobScheduler Master (to allow the original
...
JobScheduler Log Files
JobScheduler Master Log Files
No. | Log Type | Log File Name Pattern |
---|---|---|
1 | Debug Log | scheduler.log |
2 | Main Log | scheduler-<yyyy-mm-dd-hhmmss>.<scheduler-id>.log |
3 | Job Log | job.<job_chain_name>,<job_name>.log |
4 | Task Log | task.<job_chain_location>,<job_chain_name>,<job_name>.log |
5 | Order Log | order.<job_chain_location>,<job_chain_name>,<order_id>.log |
6 | Installation Log | Install_V<release_number>_<yyyymmddhhmmss>_<timestamp>.log |
7 | Engine Log | scheduler_engine.log |
8 | Output Stream Log | scheduler.out |
9 | Web Server Log | http.log |
10 | Web Service Log |
.log |
JobScheduler Agent Log Files
No. | Log Type | Log File Name Pattern |
---|---|---|
1 | Agent Main Log | jobscheduler_agent_<port>.log |
2 | Agent Task Log |
|
Feature Availability - features introduced with release 1.10
...
The central Log Level settings will be applied to all the JobScheduler objects, e.g. jobs, job chains, orders etc.
Info |
---|
The higher Log Level will lead to large size of Main Log and Debug Log, and also will require more database storage to save JobScheduler Order Logs and Task Logs |
...
- The debug and main logs for a JobScheduler Master (
scheduler.log
andscheduler-<yyyy-mm-dd-hhmmss>.<scheduler-id>.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. - Log files for individual Orders, Jobs and Tasks can be read in the relevant JOC Cockpit view by users with the necessary permissions. Permissions are described in detail in the Authentication and Authorization - Permissions for the JOC Cockpit Web Service article.
...
Children Display | ||||
---|---|---|---|---|
|