Add info on how to get OOD log directory for past jobs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
What would you like to see added?
@mdefende has already opened this issue in our main docs-tracking repo as well.
When debugging OOD app problems, we sometimes need the logs from the failed jobs. OOD stores all of these logs in the user's /data/user/$USER/ondemand/batch_connect/sys directory and names each individual log directory with a hash value instead of anything useful. This makes it impossible to tell from a glance which directory belongs to which job ID if the job has already ended.
sacct luckily stores this information in the WorkDir field. To find the log directory for a failed OOD job, use the following command:
sacct -j <jobid> -o jobid,workdir --parsable
This directory can be downloaded, zipped, and attached to a ticket for review by our team.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No target file is named. Locate the relevant Open OnDemand troubleshooting page in devops-docs, then add the supplied sacct command and explain how its WorkDir identifies the user's log directory; done means a reader can find and download the logs for a past failed job.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100