I had something like this happen on a test cluster of Raspberry Pis several
years ago, and in my case, I was able to isolate it to being an MPI issue
unrelated to SLURM. If you can run directly on the nodes, that might be a
useful distinction for you to try to make. (Running "directly" might mean
m
Sorry, 2022-2016=6 years old. This is why I let the computers do the
arithmetic
On Tue, Aug 16, 2022 at 10:19 AM Andrew Reid
wrote:
> Wondering if I should reply from an alt for this, but in my case, it's
> not so much "less well-funded" as "less well-organized".
>
> I have some small c
Wondering if I should reply from an alt for this, but in my case, it's
not so much "less well-funded" as "less well-organized".
I have some small clusters that, for convenience, run the Debian-packaged
version of SLURM. Debian 9 reached the end of LTS June, 30, 2022, and
packaged version 16.0
