We experience the same issue. SLURM 24.05.1 segfaults with squeue –json and squeue --json=v0.0.41 but works with squeue --json=v0.0.40
From: Markus Köberl via slurm-users <slurm-users@lists.schedmd.com> Date: Wednesday, 3. July 2024 at 15:15 To: Joshua Randall <jrand...@altoslabs.com> Cc: slurm-users@lists.schedmd.com <slurm-users@lists.schedmd.com> Subject: [slurm-users] Re: problem with squeue --json with version 24.05.1 On Wednesday, 3 July 2024 13:26:25 CEST Joshua Randall wrote: > Markus, > > I had a similar problem after upgrading from v23 to v24 but found that > specifying _any_ valid data version worked for me, it was only > specifying `--json` without a version that triggered an error (which > in my case was I believe a segfault from sinfo rather than a malloc > error from squeue - but as these are both memory issues it seems > possible they could both potentially arise from the same underlying > library issue presenting differently in different CLI tools). So the > underlying issue _may_ be with the logic that attempts to determine > what the latest data version is and to load that, whereas specifying > any valid version explicitly may work. > > Are you able to run `squeue --json=v0.0.41` successfully? It seams to be a problem only with squeue and data parser version v0.0.41 only, it also affects 24.05.0 the same way. $ squeue --json=v0.0.41 malloc(): corrupted top size Aborted data parser version v0.0.40 works, v0.0.39 does not return anything. regards Markus -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb...@tugraz.at
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
