Closed NathanielMiddleton closed 3 months ago
This issue concerns Slurm-web v2 which is not maintained anymore. You are highly encouraged to test the new version v3.0.0 for which the quick start guide is available online: https://docs.rackslab.io/slurm-web/install/quickstart.html
Note that Slurm-web v3.0.0 is officially supported on many distributions with RPM and deb packages. If you prefer containers, we plan to work on this in https://github.com/rackslab/Slurm-web/issues/266
Unless someone is motivated to maintain the old version of Slurm-web or you have a justified reason to keep this issue open, it will be closed in a few weeks.
For the reasons explained in the previous comment, I finally close this issue.
I have been able to get some basic functionality of the slurm api to work (mainly the header) but beyond that seems to be blocked by redis not listening:
conf/restapi.conf references that it "default to host=localhost, port=6379" but that didn't work: "ConnectionError: Error -2 connecting to :6379. Name or service not known"
setting this specifically to localhost: redis_host=localhost redis_port=6379 results in : ConnectionError: Error 101 connecting to localhost:6379. Network is unreachable (guessing that docker is not able to make that translation) I tried just disabling caching which just resulted in: "NameError: name 'redis_host' is not defined"
Where is the redis server configured to run? I must be missing something here...