My Interactive Desktop fails

hi, Interactive Desktop fails,May I ask what is the reason?
OS environment
CentOS 7.6 x64
ondemand-2.0.26
nmap-ncat-6.40
turbovnc-2.2.2
websockify-0.9.0-py2.7

“launch node desktop” → Failed to connect to novnc
"Native connect " is ok

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

Desktop 'TurboVNC: node002:1 (user01)' started on display node002:1

Log file is vnc.log
Successfully started VNC server on node002:5901...
Script starting...
Starting websocket server...
cmdTrace.c(713):ERROR:104: 'restore' is an unrecognized subcommand
cmdModule.c(411):ERROR:104: 'restore' is an unrecognized subcommand
Launching desktop 'xfce'...
WebSocket server settings:
  - Listen on :58532
  - No SSL/TLS support (no cert file)
  - Backgrounding (daemon)
generating cookie with syscall
generating cookie with syscall
generating cookie with syscall
generating cookie with syscall
Scanning VNC log file for user authentications...
Generating connection YAML file...

(xfce4-session:9645): xfce4-session-WARNING **: 16:10:51.513: xfsm_manager_load_session: Something wrong with /gfs/home/user01/.cache/sessions/xfce4-session-node002:1, Does it exist? Permissions issue?

(xfwm4:9658): xfwm4-WARNING **: 16:10:51.587: Error opening /dev/dri/card0: Permission denied
vmware-user: could not open /proc/fs/vmblock/dev
/usr/share/system-config-printer/applet.py:44: PyGIWarning: Notify was imported without specifying a version first. Use gi.require_version('Notify', '0.7') before import to ensure that the right version gets loaded.
  from gi.repository import Notify
system-config-printer-applet: failed to start NewPrinterNotification service
system-config-printer-applet: failed to start PrinterDriversInstaller service: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.434" is not allowed to own the service "com.redhat.PrinterDriversInstaller" due to security policies in the configuration file

(nm-applet:9671): dconf-CRITICAL **: 16:10:51.851: unable to create directory '/run/user/1001/dconf': Permission denied.  dconf will not work properly.

(nm-applet:9671): dconf-CRITICAL **: 16:10:51.851: unable to create directory '/run/user/1001/dconf': Permission denied.  dconf will not work properly.

(nm-applet:9671): dconf-CRITICAL **: 16:10:51.854: unable to create directory '/run/user/1001/dconf': Permission denied.  dconf will not work properly.
SELinux Troubleshooter: Applet requires SELinux be enabled to run.

(nm-applet:9671): dconf-CRITICAL **: 16:10:52.092: unable to create directory '/run/user/1001/dconf': Permission denied.  dconf will not work properly.

Hi Liu.

In looking over your logs. It appears that there many permissions issues in the logs. Can you please make sure that your user has access to everything that is required for this to launch successfully?

Thanks,
-gerald

Does websockify need WSS ?

websock.js:185 Mixed Content: The page at 'https://ood.hpc.edu/pun/sys/dashboard/noVNC-1.1.0/vnc.html?utf8=%E2%9C%93&autoconnect=true&path=rnode%2Fnode002%2F10717%2Fwebsockify&resize=remote&password=Hn4SHRSX&compressionsetting=6&qualitysetting=2&commit=Launch+Node+Desktop' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://ood.hpc.edu:443/rnode/node002/10717/websockify'. This request has been blocked; this endpoint must be available over WSS.

output log as following

Setting VNC password…
Starting VNC server…

Warning: node002:1 is taken because of /tmp/.X1-lock
Remove this file if there is no X server node002:1
Killing Xvnc process ID 2264
Xvnc process ID 2264 already killed
Xvnc did not appear to shut down cleanly. Removing /tmp/.X11-unix/X1
Xvnc did not appear to shut down cleanly. Removing /tmp/.X1-lock

Desktop ‘TurboVNC: node002:1 (user01)’ started on display node002:1

Log file is vnc.log
Successfully started VNC server on node002:5901…
Script starting…
Starting websocket server…
cmdTrace.c(713):ERROR:104: ‘restore’ is an unrecognized subcommand
cmdModule.c(411):ERROR:104: ‘restore’ is an unrecognized subcommand
Launching desktop ‘xfce’…
WebSocket server settings:

  • Listen on :33895
  • 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
    vmware-user: could not open /proc/fs/vmblock/dev

Using a self-signed certificate causes desktop unavailability

Hi Liu-shaobo,

Using a self-singed certificate might not be issue. We have setup with self signed certificate able to connect with Interactive Desktop.

There is a verification steps for https reverse proxy validation. Following URL providing steps for the same.

Here we have single node setup example, But it will be applicable for multi node node too.

Thanks,
Raja Chinnathambi

Self-signed certificates also need to set websocketly,I set up SSL with websocketly, no effect.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.