Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combination of cluster name and node name can be too long for munged #337

Open
ocaisa opened this issue Nov 20, 2024 · 2 comments
Open

Combination of cluster name and node name can be too long for munged #337

ocaisa opened this issue Nov 20, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ocaisa
Copy link
Collaborator

ocaisa commented Nov 20, 2024

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
@cmd-ntrf cmd-ntrf self-assigned this Nov 20, 2024
@cmd-ntrf cmd-ntrf added the bug Something isn't working label Nov 20, 2024
@cmd-ntrf
Copy link
Member

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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants