Introduction
The JobScheduler create number of different logs, to provide specific information about job, job chain, order, task and JobScheduler internal operational itself.
The location of the the log files can vary as per as specific installation, but for default installation one can find the log files at ${SCHEDULER_DATA}/logs folder (where ${SCHEDULER_DATA} is the JobScheduler installation path)
JobScheduler logs
- scheduler.log
- scheduler-yyyy-mm-dd-hhmmss.<schduler-id>.log
- job.job_chain_name,job_name.log
- task.job_chain_location,job_chain_name,job_name.log
- order.job_chain_location,job_chain_name,order_id.log
- Install_VX.X.XXXX_timestamp.log
- http.log
- web_service,web_service_name.log
1. scheduler.log
The scheduler.log is created during JobScheduler start up. Just before the JobScheduler startup JobScheduler copy the existing scheduler.log as scheduler-old.log, and create new 0 KB scheduler.log file. The scheduler.log has most of the information concerning internal working of the JobScheduler. The scheduler.log is create by all type of JobScheduler instances i.e. standalone, cluster, agent, backup.
Each line of the scheduler.log contains in their columns the following information:
- 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
NOTE
If JobScheduler is restarted or logs are rotated JobScheduler create a backup of the scheduler.log to scheduler-old.log and create a new scheduler.log. For any given time there will be only two scheduler.log files, there is no arching for scheduler.log files.
2. scheduler-yyyy-mm-dd-hhmiss.<scheduler-id>.log
The scheduler-yyyy-mm-dd-hhmmss.<schduler-id>.log is created during JobScheduler startup and always create with a time stamp for archiving purposes. The scheduler-id is the unique JobScheduler Id. If multiple JobSchedulers are storing there logs to a common log folder its helpful to find log of a corresponding JobScheduler. The scheduler-yyyy-mm-dd-hhmmss.<schduler-id>.log has information about process being executed by JobScheduler and other higher level information of JobScheduler operation. The log scheduler-yyyy-mm-dd-hhmmss.<schduler-id>.log can be configured to be rotate ( create new log with new time stamp) by the house keeping job sos/housekeeping/scheduler_rotate_log . The log scheduler-yyyy-mm-dd-hhmmss.<schduler-id>.log is always stored on the file system.
3. job.job_chain_name,job_name.log
The job.job_chain_name,job_name.log is created during execution of individual jobs. After job execution the log job.job_chain_name,job_name.log is also saved into the database.
4. task.job_chain_location,job_chain_name,job_name.log
The task.job_chain_location,job_chain_name,job_name.log is created during individual tasks. The task log has most of the information about execution of instance of job i.e. parameters, stdout, stderror from the application.
5. order.job_chain_location,job_chain_name,order_id.log
The order.job_chain_location,job_chain_name,order_id.log is create as order traverse from one node to another node. After order execution the order.job_chain_location,job_chain_name,order_id.log is also saved into the database.
6. Install_VX.X.XXXX_timestamp.log
The install log has important information about JobScheduler installation. installation log is very important in case of JobScheduler has problem/error after fresh installation/update.
All the job. task and order logs are saved in the database and can be accessed from the JOC and JID.
The scheduler.log,scheduler-old.log, scheduler-yyyy-mm-dd-hhmmss.<schduler-id>.log, install_VX.X.XXXX_timestamp.log are stored on the filesystem in the folder ${SCHEDULER_DATA}/logs folder.