You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Combination of cluster name and node name can be too long for munged #337
Nov 20 13:35:42 aarch64-neoverse-n1-node1.int.azure-almalinux93-202411-mc-14-1-2 munged[1478]: munged: Error: Failed to determine hostname: File name too long
It's an issue with munge 0.5.13. It's been reported here: dun/munge#140
The limit of characters for hostname is 64 because of a fixed size buffer. Upgrading to 0.5.14 would fix it. However, we currently fetch munge from EPEL so we do not have the freedom of upgrading. I'll look at the options.
Activity
cmd-ntrf commentedon Nov 20, 2024
It's an issue with munge 0.5.13. It's been reported here:
dun/munge#140
The limit of characters for hostname is 64 because of a fixed size buffer. Upgrading to 0.5.14 would fix it. However, we currently fetch munge from EPEL so we do not have the freedom of upgrading. I'll look at the options.
cmd-ntrf commentedon Nov 21, 2024
Since RHEL 8, munge is in appstream repo instead of being provided by EPEL, but they are still at 0.5.13.
https://pkgs.org/search/?q=munge
cmd-ntrf commentedon Mar 27, 2026
We intend to stop using munge for authentication and instead use Slurm auth plugin using jwt in Magic Castle 16.