I’d check the output from sacct to see what the exit code is or what Slurm is doing. It seems like it’s being scheduled and immediately failing - maybe out of memory issue or some odd shell thing.
In any case, because sacct shows historical jobs you can see the exit code of the job and that exit code/and or slurm error should point you in the right direction.
slurm job exit code is normal 0.
Able to submit normal batch mode jobs and running fine.
Interactive Desktop job is completing with in few seconds, but it is not showing any output and output.log is empty.
OK… That doesn’t make much sense that it exits 0 immediately and without anything in the logs. I see it’s a fairly new cluster… there’s something here we’re missing that’s obvious and now I think I see it.
You need the %s in the script_wrapper. I see you have it for basic - but not for vnc. This is the important bit. %s is literally the script that we provide. It is the script that you’re wrapping. Since you didn’t add it - we didn’t!
Look at the file job_script_content.sh and you’ll see there’s basically nothing there (this is the file that’s submitted to Slurm).