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

Issue with Cgroup #38

Open
jxdn opened this issue Apr 19, 2024 · 0 comments
Open

Issue with Cgroup #38

jxdn opened this issue Apr 19, 2024 · 0 comments

Comments

@jxdn
Copy link

jxdn commented Apr 19, 2024

i have these below issue:

slurmd: error: cgroup_dbus_attach_to_scope: cannot connect to dbus system daemon: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory slurmd: error: _init_new_scope_dbus: scope and/or cgroup directory for slurmstepd could not be set. slurmd: error: cannot initialize cgroup directory for stepds: if the scope /sys/fs/cgroup/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-poda101c1c8_1589_4313_acf5_02e3ca8d3994.slice/system.slice/slurmstepd.scope already exists it means the associated cgroup directories disappeared and the scope entered in a failed state. You should investigate why the scope lost its cgroup directories and possibly use the 'systemd reset-failed' command to fix this inconsistent systemd state. slurmd: error: Couldn't load specified plugin name for cgroup/v2: Plugin init() callback failed slurmd: error: cannot create cgroup context for cgroup/v2 slurmd: error: Unable to initialize cgroup plugin slurmd: error: slurmd initialization failed

i have modify the image to install dbus-devel and created cgroup.conf alongside with slurm.conf

any idea to fix this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant