Go look at that system. Likely it has an old slurmd running that should be removed.
Brian Andrus
Thanks. It resolve the issue. Now slrumcld is commuication to all nodes.These nodes are not listed the slurm.conf file.
error: unpack_header: protocol_version 8960 not supported[2025-09-20T20:05:03.455] error: destroy_forward: no init[2025-09-20T20:05:03.461] error: slurm_unpack_received_msg: [192.168.3.119:55650] Incompatible versions of client and server code
192.168.3.119 is not mentioned in the slrum.conf file.
Nilesh Dhumal
Associate Professor of Chemistry,
http://faculty.fgcu.edu/ndhumal/
Coordinator, FGCU Computational Facility,
https://www.fgcu.edu/cas/facultyresources/computationalfacility/
SH-430; Department of Chemistry and Physics
Florida Gulf Coast University
10501 FGCU Boulevard South
Fort Myers, FL 33965-6565
Phone: (239) 745-4394
Email: ndhumal@fgcu.edu
From: Renfro, Michael <Renfro@tntech.edu>
Sent: Saturday, September 20, 2025 12:21 PM
To: Dhumal, Dr. Nilesh <ndhumal@fgcu.edu>; Slurm User Community List <slurm-users@lists.schedmd.com>
Subject: Re: Compute node not respondingExternal Email: Do not click links or attachments unless you recognize the sender and know the content is safe.
Level II: Internal
slurmdbd is not a requirement to get things started [1], but you'll probably want it later.
It’s possible you’ve got host-based firewall rules on either system that are blocking communication. If you’re using firewalld, ufw, or something similar, stop their services, restart the slurmd and slurmctld services, and see if that helps.