Hi,
I had the same issue. It was just because I had an older slurmctld
somwhere with the node set to drain. Even if the node was drain in the
old slurmctld, it tries to connect to slurmd.
Le 08/12/2021 à 18:03, Sean McGrath a écrit :
Hi Bjørn-Helge,
Thanks for that.
On Wed, Dec 08, 2021 at 09:03:36AM +0100, Bj?rn-Helge Mevik wrote:
Sean McGrath <smcg...@tchpc.tcd.ie> writes:
I'm seeing something similar.
slurmdbd version is 21.08.4
All the slurmd's & slurmctld's are version 20.11.8
This is what is in the slurmdbd.log
[2021-12-07T17:16:50.001] error: unpack_header: protocol_version 8704 not
supported
I believe 8704 corresponds to 19.05.x, which is no longer accepted in
21.08.x.
Can anyone advise how to identify the clients that are generating those
errors please?
I don't think slurmd connects directly to slurmdbd, so perhaps it is
some frontend node or machine outside the cluster itself which has the
slurm commands installed and is doing requests to slurmdbd (sacct,
sacctmgr, etc.)?
Yes, I think it is it, I haven't been able to track it down and will
just have to live with the messages in the logs.
With SlurmdbdDebug set to debug or higher, new client connections will
be logged with
[2021-12-08T09:00:07.992] debug: REQUEST_PERSIST_INIT: CLUSTER:saga
VERSION:9472 UID:51568 IP:10.2.3.185 CONN:8
in slurmdbd.log. But perhaps that will not happen if slurmdbd fails to
unpack the header?
Unfortunately it doesn't as it can't unpack the headers so I don't get a
more informative error.
Thanks for your help all the same.
Sean
--
Regards,
Bjørn-Helge Mevik, dr. scient,
Department for Research Computing, University of Oslo
--
Nicolas Greneche
USPN
Support à la recherche / RSSI
https://www-magi.univ-paris13.fr
