[Bug 288593] sysutils/slurm-wlm 23.11.7 fails to start with slurmctld: error: Error binding slurm stream socket: Invalid argument
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 288593] sysutils/slurm-wlm 23.11.7 fails to start with slurmctld: error: Error binding slurm stream socket: Invalid argument"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 288593] sysutils/slurm-wlm 23.11.7 fails to start with slurmctld: error: Error binding slurm stream socket: Invalid argument"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 01 Aug 2025 16:22:17 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288593
Bug ID: 288593
Summary: sysutils/slurm-wlm 23.11.7 fails to start with
slurmctld: error: Error binding slurm stream socket:
Invalid argument
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: rikka.goering@outlook.de
Attachment #262625 text/plain
mime type:
Created attachment 262625
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=262625&action=edit
patch to fix wrong socket_length
I tried to install slurm-wlm 23.11.7 on FreeBSD-14.3-RELEASE-p1 but when trying
to start slurmctld via "slurmctld -Dvvv -f [config-file]" i got the error:
slurmctld: debug: slurmctld log levels: stderr=debug2 logfile=quiet
syslog=quiet
slurmctld: debug: Log file re-opened
slurmctld: pidfile not locked, assuming no running daemon
slurmctld: debug: auth/munge: init: loaded
slurmctld: debug: hash/k12: init: init: KangarooTwelve hash plugin loaded
slurmctld: error: Error binding slurm stream socket: Invalid argument
slurmctld: fatal: slurm_init_msg_engine_port: error Invalid argument
I identified the problem to be inside of the slurm_init_msg_engine() function
inside of src/common/slurm_protocol_socket.c
It seemed like the function was trying to set an invalid socket_length when
calling the bind() function. I came up with the patch i attached. Adding the
patch to sysutils/slurm-wlm/files was able to fix the issue for me.
--
You are receiving this mail because:
You are the assignee for the bug.