Slurm-web can't find cluster

[rfpg1]

Describe the bug
Slurm-web can't find any cluster

To Reproduce
Installed slurm-web by following the documentation.
Every service is up and every script to check communcations worked but still can't find any clusters

Expected behavior
Find the cluster I've defined

Screenshots

Versions
ii python3-racksdb 0.6.0-1.ubuntu2404 all Python library for datacenter infrastructures database
ii python3-racksdb-web 0.6.0-1.ubuntu2404 all Meta-package for datacenter infrastructures database web app
ii python3-rfl-authentication 1.6.0-2.ubuntu2404 all Rackslab Foundation Library: authentication package
ii python3-rfl-core 1.6.0-2.ubuntu2404 all Rackslab Foundation Library: core package
ii python3-rfl-log 1.6.0-2.ubuntu2404 all Rackslab Foundation Library: log package
ii python3-rfl-permissions 1.6.0-2.ubuntu2404 all Rackslab Foundation Library: permissions package
ii python3-rfl-settings 1.6.0-2.ubuntu2404 all Rackslab Foundation Library: settings package
ii python3-rfl-web 1.6.0-2.ubuntu2404 all Rackslab Foundation Library: web package
ii python3-slurm-web 5.2.0-2.ubuntu2404 all Web interface for Slurm HPC workload manager: common library
ii slurm-smd 25.05.4-1 amd64 Slurm Workload Manager
ii slurm-smd-client 25.05.4-1 amd64 Slurm Workload Manager client commands.
ii slurm-smd-slurmctld 25.05.4-1 amd64 Slurm controller daemon.
ii slurm-smd-slurmdbd 25.05.4-1 amd64 Slurm database daemon.
ii slurm-smd-slurmrestd 25.05.4-1 amd64 Slurm REST API daemon
ii slurm-web-agent 5.2.0-2.ubuntu2404 all Web interface for Slurm HPC workload manager: agent component
ii slurm-web-gateway 5.2.0-2.ubuntu2404 all Web interface for Slurm HPC workload manager: gateway component

Additional context
I'm trying to install slurm-web on the login-node where I also have slurmctld and slurmdbd and slurmrestd and then have a working node with slurmd.
Everything just related to slurm woks

[rezib]

Hello @rfpg1, I just converted your issue #659 into a discussion as this is not qualified as an actual bug.

Can you check gateway and agent services logs?

[rezib]

Well it seems you are impacted by #656 that was present in Slurm-web packages 5.2.0-1. It is fixed in packages 5.2.0-2. Did you restart the gateway service after upgrade to 5.2.0-2?

[rfpg1]

Yes I did
Now I tried the workaround said in #656 ,and the cluster was found in the web interfac,e but when I clicked got this error: Server error: slurmrestd error: Unable to query jobs (slurm_load_jobs()) [Protocol authentication error/1007]

So the workaround did not work 100%

Any other ideas?

Edit:
Also put here the slurm-web-agent logs with errors
Nov 06 21:56:08 login-node-new slurm-web-agent[51000]: Thread-222 (process_request_thread): [ERROR] slurmrestd error: Unable to query jobs (slurm_load_jobs()) [Protocol authentication error/1007]
Nov 06 21:56:08 login-node-new slurm-web-agent[51000]: Thread-222 (process_request_thread): [INFO] 127.0.0.1 - - [06/Nov/2025 21:56:08] "GET /v5.2.0/stats HTTP/1.1" 500 -

Edit2:
Managed to get it working with the workaround, just need to also restart slurm-web-agent

[rezib]

Everything works now? That's my understanding after edit2, do you confirm?

Can you try removing the workaround, restart the gateway and check it still works? If not, can you please give me the output of:

# /usr/libexec/slurm-web/slurm-web-show-conf gateway

[rfpg1]

With the workaround, everything worked, yes!

I removed the workaround, and it still works, even after restarting slurm-web-agent and slurm-web-gateway, so I'm not sure what the issue was and why it works now

If there is anything I can do to help resolve the error for future users, please let me know.

Anyway, this is the output of the command you asked me to do after removing the workaround:

/usr/libexec/slurm-web/slurm-web-show-conf gateway
INFO ⸬ Dumping configuration of Slurm-web gateway
INFO ⸬ Loading configuration definition: /usr/share/slurm-web/conf/gateway.yml
INFO ⸬ Loading site configuration file: /etc/slurm-web/gateway.ini
[agents]
url: http://localhost:5012 (site:ini:/etc/slurm-web/gateway.ini)
version: 5.1.0 (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
racksdb_version: 0.5.0 (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
[authentication]
enabled: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
method: ldap (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
[jwt]
key: /var/lib/slurm-web/jwt.key (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
duration: 1 (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
algorithm: HS256 (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
audience: slurm-web (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
[ldap]
uri: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
cacert: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
starttls: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
user_base: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
group_base: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
user_class: posixAccount (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
user_name_attribute: uid (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
user_fullname_attribute: cn (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
user_primary_group_attribute: gidNumber (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
group_name_attribute: cn (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
group_object_classes: posixGroup, groupOfNames (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
lookup_user_dn: True (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
bind_dn: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
bind_password: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
bind_password_file: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
lookup_as_user: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
restricted_groups: ∅ (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
[service]
interface: 0.0.0.0 (site:ini:/etc/slurm-web/gateway.ini)
port: 5011 (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
cors: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
debug: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
log_flags: ALL (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
debug_flags: ALL (site:ini:/etc/slurm-web/gateway.ini)
[ui]
host: http://MY_IP:5011 (site:ini:/etc/slurm-web/gateway.ini)
enabled: True (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
path: /usr/share/slurm-web/frontend (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
templates: /usr/share/slurm-web/templates (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
message_template: message.html.j2 (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
message_login: /etc/slurm-web/messages/login.md (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
hide_denied: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
racksdb_rows_labels: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)
racksdb_racks_labels: False (def:yaml:/usr/share/slurm-web/conf/gateway.yml)

Thank you very much for your help!

[rezib]

With the workaround, everything worked, yes!

Cool! 👍

I removed the workaround, and it still works, even after restarting slurm-web-agent and slurm-web-gateway, so I'm not sure what the issue was and why it works now

Well, I guess we'll never know then 🤷‍♂️

Thank you very much for your help!

You're welcome!