Thanks both of you
I will try to mitigate with changing variables.
However, I think perhaps it would be helpful if jobid_name could be 64 instead
of 32
Einar
Sent from my ICE X Supercomputer
Einar Næss jensen
einar.nass.jen...@ntnu.no
+47 90990249
On 13 Aug 2022, at 01:16, Andreas Dilger w
Michael,
I wasn't even aware of this behavior of falling back to jobid_name if
$jobid_var is unset. Could you please file a ticket in Jira LUDOC about this,
and ideally submit a patch to explain this in the manual.
Cheers, Andreas
On Aug 12, 2022, at 16:26, Sternberg, Michael G. via lustre-dis
Einar,
The strings in your $SLURM_JOB_ID values or host names are likely too long to
serve as jobid for the Lustre Jobstats feature .
You might try %H instead of %h in jobid_name. For reference, from the Lustre
manual, https://doc.lustre.org/lustre_manual.xhtml#jobstats :
> %e print executable
logfiles on oss servers are full of these error messages:
Invalid jobid size (37), expect(32)
What does it mean?
we have set this:
[root@mds-1 ~]# lctl get_param jobid_var jobid_name
jobid_var=SLURM_JOB_ID
jobid_name=%j:%u:%h
lustre version is 2.12.6(ddn)
___
