rachettia
(Rachettia)
September 2, 2025, 2:52pm
1
When attempting to launch an Interactive desktop via Open Ondemand server receiving the following message of “Failed to connect to server - NoVNC”.
I’ve looked at the documents below but have been unable to resolve the issue with the interactive desktop failing to make the connection.
I open up developer tools in Firefox and there appears to be an issue with the websockify connection and the vnc password input.
I was hoping you could take a look at the log files and let us know what we maybe missing or over looking.
developer-tools.txt (3.6 KB)
websockify.log.txt (129 Bytes)
vnc.log.txt (1.3 KB)
output.log.txt (2.4 KB)
Hello, I am working on a fresh install of OOD on Ubuntu 22.04 (migrating from CentOS 7). All dependencies seem to be installed but running into the following issue:
Setting VNC password...
Starting VNC server...
WARNING: n006.cluster.pssclabs.com:1 is taken because of /tmp/.X1-lock
Remove this file if there is no X server n006.cluster.pssclabs.com:1
Killing Xvnc process ID 754372
Xvnc process ID 754372 already killed
Xvnc did not appear to shut down cleanly. Removing /tmp/.X11-unix/X1
Xvnc did…
Hi all, I have recently managed to get an installation of OOD going on my hpc. I have added a desktop app by cloning the “bc_desktop” repo here .
The desktop app successfully launches but I get a “Failed to connect to server” on the noVNC page. The output.log is below:
Setting VNC password...
Starting VNC server...
WARNING: n002.cluster.com:1 is taken because of /tmp/.X1-lock
Remove this file if there is no X server n002.cluster.com:1
Killing Xvnc process ID 158023
Xvnc process ID 158023 alrea…
I solved it! The error above was overcome by fixing the permissions on /tmp (it was not writable for some reason). I found that this was an issue by running Xvnc manually and seeing that Xvnc failed to create a “/tmp/.tX1-lock”. There was no other system error log, so it was tough to figure out until I did this manual run.
After that, the “Launch Desktop” button was finally visible. But, clicking it resulted in “Failed to connect to server” in the VNC console. By reading a prior topic here, I f…
Hi and welcome!
As an initial check - I’d like to ensure that node_uri and rnode_uri are enabled in the ood_portal.yml and that their Location directives are in ood-portal.conf.
If they are and that all looks good, these are the errors I’d hone in on:
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
You can see here how we set this at OSC:
Additionally, you can set these configurations globally for the whole cluster file in the cluster.d file: