IMPORTANT - Can not start any slurm job anymore! #55
Replies: 5 comments
-
|
accinfo shows that there are 34k available. I dont know if it is updated every day. Also, I saw that there are 62 accounts so each one of should be able to burn 6451 credits. I think nobody can run any job, 30mins ago I could run some 2mins jobs for testing now I cant. |
Beta Was this translation helpful? Give feedback.
-
|
So if even a 2 minutes slurm job can not be scheduled, no wonder that I can not run any slurm job, as I need a few hours. Hopefully, we can get a time extension. Because this situation is unworkable! |
Beta Was this translation helpful? Give feedback.
-
|
Just to double check: These values I have been using all the time. So they should be okey. But just in case. #!/bin/bash srun apptainer exec --nv --env-file .env container.sif /bin/bash main.sh |
Beta Was this translation helpful? Give feedback.
-
|
Nick Brummans confirmed that we ran out of credits. |
Beta Was this translation helpful? Give feedback.
-
|
I could not run any simulations today. Hopefully the dead-line can be extended with 1 week. Because during the week I have to work. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I get the message "budget running low" here, and apparently I can't even start any slurm jobs anymore because of low budget. I find that strange, because I haven't really run much. So I can't run anything anymore. What to do now?
Until my budget gets increased, I am stuck.
Can the budget be increased again to the start amount, and can I get a time extension till next week?
Beta Was this translation helpful? Give feedback.
All reactions