Initial setup Desktop noVNC not working - Failed to connect to server

Get Help
1

New install via puppet.

Job submits and reserves node.

Launch Desktop-> Web page for noVNC comes up and errors “Failed to connect to server”

Any help appreciated.

Thanks
Keith

output.log =

Lmod has detected the following error: User module collection: "module" does
not exist.
  Try "module savelist" for possible choices.



Setting VNC password...
Starting VNC server...

Desktop 'TurboVNC: u125.unity:2 (stewart.358)' started on display u125.unity:2

Log file is vnc.log
Successfully started VNC server on u125.unity:5902...
Script starting...
Starting websocket server...
The system default contains no modules
  (env var: LMOD_SYSTEM_DEFAULT_MODULES is empty)
  No changes in loaded modules

Launching desktop 'xfce'...
WebSocket server settings:
  - Listen on :22543
  - Flash security policy server
  - No SSL/TLS support (no cert file)
  - Backgrounding (daemon)
Scanning VNC log file for user authentications...
Generating connection YAML file...
generating cookie with syscall
generating cookie with syscall
generating cookie with syscall
generating cookie with syscall

(xfce4-session:20438): xfce4-session-WARNING **: 10:56:58.653: xfsm_manager_load_session: Something wrong with /home/stewart.358/.cache/sessions/xfce4-session-u125.unity:2, Does it exist? Permissions issue?

(xfwm4:20445): xfwm4-WARNING **: 10:56:58.785: Error opening /dev/dri/card0: Permission denied

/usr/local/share/lmodfiles/base/websockify/0.8.0.lua

setenv("WEBSOCKIFY_CMD", "/usr/bin/websockify")

puppet file

openondemand::clusters:
  unity:
    cluster_title: 'Unity Cluster'
    login_host: unity.asc.ohio-state.edu
    job_adapter: slurm
    job_conf: /etc/slurm/slurm.conf
    job_debug: true
    batch_connect:
      basic:
        script_wrapper: "module restore\n%s"
      vnc:
        script_wrapper: "module restore\nmodule load turbovnc\nmodule load websockify\n%s"

[root@u125 log]# which websockify
/usr/bin/websockify

2

Hi a fellow buckeye! I didn’t realize OSU had another deployment of OnDemand?!

In any case, looks like everything went well on the backend. What are the logs from the browser? Chrome will let you open dev tools on a new window.

I’m looking for this and any errors relate to it. Basically I want to be sure that you’ve setup to allow websocket upgrades. Again, everything looks good on the backend so I’m wondering if it’s a client issue. You also may want to try a different browser.

image
image1782×739 68.6 KB

3

Here’s my output:

(As for another install at OSU, there’s not a public one yet. Production at the end of July)

Screen Shot 2021-06-17 at 6.47.29 PM
Screen Shot 2021-06-17 at 6.47.29 PM923×416 49.2 KB

4

Thanks! Though I’m looking for the response code which I can’t see there. I’m looking to ensure you can 101 upgrade.

5

I’ve found a fix.

My puppet file was…

openondemand::host_regex: ‘(u)\d+’

the CORRECT value should be:

openondemand::host_regex: ‘u\d+.unity’

My noVNC URL is:
https://ondemand-dev.asc.ohio-state.edu/pun/sys/dashboard/noVNC-1.1.0/vnc.html?utf8=✓&autoconnect=true&path=rnode%2Fu125.unity%2F34822%2Fwebsockify&resize=remote&password=REMOVED&compressionsetting=6&qualitysetting=2&commit=Launch+Unity+VDI