Logs for each job are stored in subdirectories within the logpath directory. Within each job directory, there are a number of log files associated with the job and its subjobs. The jobs are located in groups of 1000, where jobs 1-999 go in group 0, jobs 1000-1999 go in group 1, etc.  The logs are grouped this way to make archiving simple. The exact specification is:



    • Linux                /var/spool/qube/job/5000/5042
    • Windows Vista/2008/7   C:\ProgramData\pfx\qube\logs\job\5000\5042
    • Windows XP/2003      C:\Program Files\pfx\qube\logs\job\5000\5042


    The naming convention for each job log file is:
    where the job_ID is the ID of the job, and type is the type of log file. The type of a job log file can be either arc for a job archive, or hst for a job history file.

    Similarly, the naming convention for each subjob file is:
    where job_ID is the ID of the job, subjob_ID is the ID of the subjob, and type is the type of log file. The type of the log file can be out for standard output, err for standard error output, or sts for job status information. Below is a table summarizing the various naming conventions for log files.

    Standard Output


    Standard Error

    job_ID_ subjob_ID.err

    Job History Log


    Job Statistics

    job_ID_ subjob_ID.sts

    Job Archive File


    Job XML Archive File


    Job Account File


    Job Callback Log


    All but the binary job archive files are human-readable. Additionally, the output and error logs can be can be accessed from the command line tools qbout and qberr.

    Verify that the Supervisor and Workers can access the appropriate log file directory, and that the directory permissions are set correctly.



    Under normal circumstances, the Supervisor will automatically create a job log subdirectory when it registers a submitted job. If the Supervisor is unable to create the directory, job execution may fail. Also, since the Workers are responsible for writing output to the subjob log files, if those files cannot be created or written to, job execution may also fail.

    • No labels