# Logging for failed job submissions
**URL:** https://discourse.openondemand.org/t/logging-for-failed-job-submissions/4976
**Category:** Get Help
**Created:** [September 14, 2026, 6:58pm UTC](https://discourse.openondemand.org/t/logging-for-failed-job-submissions/4976 "2026-09-14T18:58:47Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@jcreech](https://discourse.openondemand.org/u/jcreech)
#### Post date: [September 14, 2026, 6:58pm UTC](https://discourse.openondemand.org/t/logging-for-failed-job-submissions/4976/1 "2026-09-14T18:58:47Z")
We have had a few instances where our slurm job submissions fail before submitting. A very simple example would be a typo in an app’s yaml code. Typically we find those things in a sandbox environment, but there have been a few cases where a slurm change (outside of OOD) breaks an app. We recently encountered this with slurm federation, for example.
In these situations there is no output.log to dig into, and the files that are present don’t provide much help with the specific error. What would be useful is a log of the command that was attempted, which failed, for example “sbatch blahdeblah” instead of only the error message. It isn’t always clear what went wrong, when nothing changed on the OOD side.
Is this kind of logging possible, or is it perhaps already there but I don’t know where to find it? I did find \.\_error\_ssl.log, but that doesn’t seem to have what I’m looking for.
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [September 14, 2026, 7:09pm UTC](https://discourse.openondemand.org/t/logging-for-failed-job-submissions/4976/2 "2026-09-14T19:09:15Z")
You can look in `/var/log/ondemand-nginx/$USER/error.log` for full `sbatch` commands that are issued.
---
### Author:  [@jcreech](https://discourse.openondemand.org/u/jcreech)
#### Post date: [September 14, 2026, 7:35pm UTC](https://discourse.openondemand.org/t/logging-for-failed-job-submissions/4976/3 "2026-09-14T19:35:37Z")
Thanks, this is what I was looking for.
Do you have a recommended format clean-up process to dig into these logs? Looks like it’s a mix of Ruby and JSON.
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [September 14, 2026, 7:59pm UTC](https://discourse.openondemand.org/t/logging-for-failed-job-submissions/4976/4 "2026-09-14T19:59:20Z")
No sorry, I generally just `ctrl+f` or `grep` what I’m looking for.