Vnc port configurations

runlolarun · November 12, 2024, 4:54pm

Hello,

I’m trying to change min_port and max_port for my interactive desktop connection.

  batch_connect:
    basic:
      script_wrapper: |
        module purge
        %s
    vnc:
      min_port: 10000
      max_port: 60000
      script_wrapper: |
        module purge
        export PATH="/opt/TurboVNC/bin:$PATH"
        export WEBSOCKIFY_CMD="/usr/bin/websockify"
        export XDG_RUNTIME_DIR="/tmp/${UID}"
        %s

It doesn’t seem to make a difference as I am still seeing in connection.yml:
port: 5901

I have also tried modifying /var/www/ood/apps/sys/bc_desktop/submit.yml.erb

 ---
 batch_connect:
   template: vnc
   basic:
     min_port: 10000
     max_port: 60000
   vnc:
     min_port: 10000
     max_port: 60000

$ cat websockify.log
WebSocket server settings:

Listen on :35595

No SSL/TLS support (no cert file)

proxying from :35595 to localhost:5901

Does websockify.log explain that in reality, it’s port 35595, and not 5901 (by proxy) that is being used?

I’ve restarted httpd and Web Server.

Thank you.

jeff.ohrstrom · November 12, 2024, 5:45pm

That appears to be hard coded.

github.com

OSC/ood_core/blob/4342e29119c9db3a4860940f83191ba1cb760156/lib/ood_core/batch_connect/templates/vnc.rb#L119


      
          
                # If running, then all is well and break out of loop
                kill -0 ${VNC_PID} 2>/dev/null && break
              done
          
              # If we fail to start it after so many tries, then just give up
              kill -0 ${VNC_PID} 2>/dev/null || clean_up 1
          
              # Parse output for ports used
              display=$(echo "${VNC_OUT}" | awk -F':' '/^Desktop/{print $NF}')
              port=$((5900+display))
          
              echo "Successfully started VNC server on ${host}:${port}..."
          
              #{super}
            EOT
          end
          
          # Run the script under the VNC server's display
          def run_script
            %(DISPLAY=:${display} #{super})

Min and max ports only apply when you’re looking to find_port. So it doesn’t appear to be used here in the noVNC case.

github.com

OSC/ood_core/blob/4342e29119c9db3a4860940f83191ba1cb760156/lib/ood_core/batch_connect/template.rb#L169


      
          
            return 127
          }
          export -f port_used
          
          # Find available port in range [$2..$3] for host $1
          # Default host: localhost
          # Default port range: [#{min_port}..#{max_port}]
          # returns error code (0: success, 1: failed)
          # On success, the chosen port is echoed on stdout.
          find_port () {
            local host="${1:-localhost}"
            local min_port=${2:-#{min_port}}
            local max_port=${3:-#{max_port}}
            local port_range=($(shuf -i ${min_port}-${max_port}))
            local retries=1 # number of retries over the port range if first attempt fails
            for ((attempt=0; attempt<=$retries; attempt++)); do
              for port in "${port_range[@]}"; do
                if port_used "${host}:${port}"; then
                  continue
                fi

runlolarun · November 12, 2024, 5:51pm

Thank you for responding.

So which ports are required to be open with firewall? I’ll be using xfce desktop.

Can you also elaborate on your “no vnc” comment, please?

Thank you!

jeff.ohrstrom · November 12, 2024, 6:40pm

Where’s the firewall? The network path in question is between the OOD server (the machine OOD is installed on) and the compute node where the job is running. Your client browser, for example, doesn’t need network connectivity to the computeNode:5901 - the OOD server does.

When you connect to the desktop - we’re proxying you through OOD to it. So the full path is

you -> OOD on port 443 -> the compute node on port 5901

So if there’s a firewall between you and OOD - all you need to open up is 443, the https port.

jeff.ohrstrom · November 12, 2024, 6:42pm

We have two different kinds of applications. Those that need a desktop GUI which need noVNC (a technology we use to pass VNC data over the web) and those that run straight http servers themselves like Jupyter.

HTTP applications - like Jupyter, you could specify the port range. Apparently that’s not the case for GUI applications like desktops.

runlolarun · November 12, 2024, 6:53pm

Thank you very much. I’m still stuck, but I think my issue is something else, so I will open another ticket if anything. I really appreciate your help.

jeff.ohrstrom · November 12, 2024, 7:37pm

To be clear - the port 35595 here is what you can limit.

I can continue to help you here. What’s the issue you’re seeing? You have some network connectivity issue?

runlolarun · November 12, 2024, 8:15pm

Thank you for offering to help.

I’m trying to start an interactive desktop, but getting the wonderful Failed to connect to server error message.

My output.log:

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

WARNING: node805.host.edu:1 is taken because of /tmp/.X1-lock
Remove this file if there is no X server node805.host.edu:1
Killing Xvnc process ID 3534720
Xvnc process ID 3534720 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: node805.host.edu:1 (aadvorki)' started on display node805.host.edu:1

Log file is vnc.log
Successfully started VNC server on node805.ionic.cs.princeton.edu:5901...
Script starting...
Starting websocket server...
Launching desktop 'xfce'...
Failed to init libxfconf: Error spawning command line “dbus-launch --autolaunch=e785394556274b3fb9c1573b6d7e44f1 --binary-syntax --cl
ose-stderr”: Child process exited with code 1.
Failed to init libxfconf: Error spawning command line “dbus-launch --autolaunch=e785394556274b3fb9c1573b6d7e44f1 --binary-syntax --cl
ose-stderr”: Child process exited with code 1.
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
[websockify]: pid: 3615206 (proxying 14220 ==> localhost:5901)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...

(xfwm4:3615204): xfwm4-WARNING **: 15:11:11.346: Could not create GLX context.

(xfwm4:3615204): Gdk-WARNING **: 15:11:11.347: The program 'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 2764 error_code 2 request_code 150 (GLX) minor_code 24)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[websockify]: started successfully (proxying 14220 ==> localhost:5901)
Scanning VNC log file for user authentications...
Generating connection YAML file...
xfsettingsd: No window manager registered on screen 0.

root@ondemand /etc/ood/config/apps/bc_desktop/submit $ cat slurm.yml.erb
---
batch_connect:
  before_script: |
    # Export the module function if it exists
    [[ $(type -t module) == "function"  ]] && export -f module

    # MATE acts strange in pitzer-exp and doesn't like /var/run/$(id -u)
    export XDG_RUNTIME_DIR="$TMPDIR/xdg_runtime"
    # reset SLURM_EXPORT_ENV so that things like srun & sbatch work out of the box
    export SLURM_EXPORT_ENV=ALL

$ cat ionic.yml
---
title: "HPC Desktop"
cluster: "ionic"
attributes:
  desktop: "xfce"
  bc_account:
      help: "You can leave this blank to use default SLURM account."
  bc_queue: "compute"

root@node805 /etc/slurm $ ls -la /tmp/.X1*
-r--r--r--. 1 aadvorki guest   11 Nov 12 15:11 /tmp/.X1-lock

/tmp/.X11-unix:
total 304
drwxrwxrwx.    2 aadvorki guest   4096 Nov 12 15:11 .
drwxrwxrwt. 2408 root     root  303104 Nov 12 15:11 ..
srwxrwxrwx.    1 aadvorki guest      0 Nov 12 15:11 X1

Is there anything else I can provide you with? Thank you very much!

jeff.ohrstrom · November 12, 2024, 8:24pm

runlolarun:

(xfwm4:3615204): Gdk-WARNING **: 15:11:11.347: The program 'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 2764 error_code 2 request_code 150 (GLX) minor_code 24)

This seems to be the source of your issues. From what I’ve seen (or can recall off the top of my head) this seems to be an issue with your video card drivers (specifically maybe even nVidia drivers?).

runlolarun · November 12, 2024, 8:28pm

$ nvidia-smi
Tue Nov 12 15:27:27 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 560.35.03              Driver Version: 560.35.03      CUDA Version: 12.6     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:3D:00.0 Off |                  N/A |
| 23%   22C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   1  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:3E:00.0 Off |                  N/A |
| 23%   24C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   2  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:3F:00.0 Off |                  N/A |
| 23%   26C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   3  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:40:00.0 Off |                  N/A |
| 23%   20C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   4  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:41:00.0 Off |                  N/A |
| 23%   23C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   5  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:60:00.0 Off |                  N/A |
| 23%   21C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   6  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:61:00.0 Off |                  N/A |
| 23%   25C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   7  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:62:00.0 Off |                  N/A |
| 23%   22C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   8  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:63:00.0 Off |                  N/A |
| 23%   25C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   9  NVIDIA GeForce GTX 1080 Ti     On  |   00000000:64:00.0 Off |                  N/A |
| 23%   23C    P8              8W /  250W |       3MiB /  11264MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

jeff.ohrstrom · November 12, 2024, 8:31pm

I wonder if you need to run nvidia-xconfig?

jeff.ohrstrom · November 12, 2024, 8:51pm

If you ran it as root, it would write files to /etc/X11. It’s odd you don’t have anything there at all…

You can try nvidia-xconfig -o ~/some-tmp-dir or similar to write files to your own HOME to see what files could be generated before you actually run it as root.

runlolarun · November 12, 2024, 8:54pm

Yes sorry, I realized I had to run it as root:) Sorry.

Same error message.

$ more vnc.log
TurboVNC Server (Xvnc) 64-bit v3.1.1 (build 20240127.sdl9)
Copyright (C) 1999-2024 The VirtualGL Project and many others (see README.md)
Visit http://www.TurboVNC.org for more information on TurboVNC

12/11/2024 15:50:23 Using security configuration file /etc/turbovncserver-security.conf
12/11/2024 15:50:23 Enabled security type 'tlsvnc'
12/11/2024 15:50:23 Enabled security type 'tlsotp'
12/11/2024 15:50:23 Enabled security type 'tlsplain'
12/11/2024 15:50:23 Enabled security type 'x509vnc'
12/11/2024 15:50:23 Enabled security type 'x509otp'
12/11/2024 15:50:23 Enabled security type 'x509plain'
12/11/2024 15:50:23 Enabled security type 'vnc'
12/11/2024 15:50:23 Enabled security type 'otp'
12/11/2024 15:50:23 Enabled security type 'unixlogin'
12/11/2024 15:50:23 Enabled security type 'plain'
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
12/11/2024 15:50:23 Desktop name 'TurboVNC: node805.host.edu:1 (aadvorki)' (node805.ionic.cs.princeton.edu:1)
12/11/2024 15:50:23 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
12/11/2024 15:50:23 Listening for VNC connections on TCP port 5901
12/11/2024 15:50:23   Interface 0.0.0.0
12/11/2024 15:50:23 Framebuffer: BGRX 8/8/8/8
12/11/2024 15:50:23 New desktop size: 800 x 600
12/11/2024 15:50:23 New screen layout:
12/11/2024 15:50:23   0x00000040 (output 0x00000040): 800x600+0+0
12/11/2024 15:50:23 Maximum clipboard transfer size: 1048576 bytes
12/11/2024 15:50:23 VNC extension running!

$ more output.log
Setting VNC password...
Starting VNC server...

WARNING: node805.ionic.cs.princeton.edu:1 is taken because of /tmp/.X1-lock
Remove this file if there is no X server node805.host.edu:1
Killing Xvnc process ID 3615141
Xvnc process ID 3615141 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: node805.host.edu:1 (aadvorki)' started on display node805.ionic.cs.princeton.edu:1

Log file is vnc.log
Successfully started VNC server on node805.host.edu:5901...
Script starting...
Starting websocket server...
Launching desktop 'xfce'...
Failed to init libxfconf: Error spawning command line “dbus-launch --autolaunch=e785394556274b3fb9c1573b6d7e44f1 --binary-syntax --cl
ose-stderr”: Child process exited with code 1.
Failed to init libxfconf: Error spawning command line “dbus-launch --autolaunch=e785394556274b3fb9c1573b6d7e44f1 --binary-syntax --cl
ose-stderr”: Child process exited with code 1.
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
[websockify]: pid: 3624325 (proxying 13937 ==> localhost:5901)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...

(xfwm4:3624323): xfwm4-WARNING **: 15:50:25.538: Could not create GLX context.

(xfwm4:3624323): Gdk-WARNING **: 15:50:25.540: The program 'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 2764 error_code 2 request_code 150 (GLX) minor_code 24)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[websockify]: started successfully (proxying 13937 ==> localhost:5901)
Scanning VNC log file for user authentications...
Generating connection YAML file...
xfsettingsd: No window manager registered on screen 0.
xfce4-panel: No window manager registered on screen 0. To start the panel without this check, run with --disable-wm-check.

** (wrapper-2.0:3624377): WARNING **: 15:50:39.391: No outputs have backlight property

(wrapper-2.0:3624376): libnotify-WARNING **: 15:50:39.439: Failed to connect to proxy

(wrapper-2.0:3624377): Gtk-CRITICAL **: 15:50:39.508: gtk_icon_theme_has_icon: assertion 'icon_name != NULL' failed

(wrapper-2.0:3624377): Gtk-CRITICAL **: 15:50:39.510: gtk_icon_theme_has_icon: assertion 'icon_name != NULL' failed

(wrapper-2.0:3624377): Gtk-CRITICAL **: 15:50:39.510: gtk_icon_theme_has_icon: assertion 'icon_name != NULL' failed

(wrapper-2.0:3624377): Gtk-CRITICAL **: 15:50:39.554: gtk_icon_theme_has_icon: assertion 'icon_name != NULL' failed
No window manager registered on screen 0. To start the xfdesktop without this check, run with --disable-wm-check.

ERROR: A supplied argument is invalid


(nm-applet:3624627): libnotify-WARNING **: 15:50:58.027: Failed to connect to proxy

(nm-applet:3624627): nm-applet-WARNING **: 15:50:58.029: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceU
nknown: The name org.freedesktop.Notifications was not provided by any .service files

(tracker-miner-fs-3:3624624): Tracker-CRITICAL **: 15:50:58.053: Could not create store/endpoint: no such table: nrl:Ontology
Xlib:  extension "DPMS" missing on display ":1.0".
Xlib:  extension "DPMS" missing on display ":1.0".
Xlib:  extension "DPMS" missing on display ":1.0".
Xlib:  extension "DPMS" missing on display ":1.0".
Xlib:  extension "DPMS" missing on display ":1.0".

root@node805 /etc/X11 $ ls -la
total 52
drwxr-xr-x.   7 root root  4096 Nov 12 15:49 .
drwxr-xr-x. 164 root root 12288 Nov 12 15:09 ..
drwxr-xr-x.   2 root root  4096 Aug  9  2021 applnk
drwxr-xr-x.   2 root root  4096 Jul  2 09:44 fontpath.d
drwxr-xr-x.   2 root root  4096 Jul  2 09:39 mwm
drwxr-xr-x.   5 root root  4096 Feb 16  2024 xinit
-rw-r--r--.   1 root root   547 Aug 10  2021 Xmodmap
-rw-r--r--.   1 root root  1235 Nov 12 15:49 xorg.conf
-rw-r--r--.   1 root root  1228 Nov 12 15:49 xorg.conf.backup
drwxr-xr-x.   2 root root  4096 Oct 17 09:45 xorg.conf.d
-rw-r--r--.   1 root root     0 Nov 12 15:34 xorg.conf.nvidia-xconfig-original
-rw-r--r--.   1 root root   493 Aug 10  2021 Xresources

jeff.ohrstrom · November 12, 2024, 8:57pm

Is there any /var/log/Xorg.0.log file or similar?

runlolarun · November 12, 2024, 9:35pm

Unfortunately, no.

root@node805 /var/log $ locate *xorg* |grep -i log
/usr/share/doc/xorg-x11-drv-wacom/ChangeLog
/usr/share/doc/xorg-x11-xinit/ChangeLog
root@node805 /var/log $ grep -ri xorg messages*

runlolarun · November 13, 2024, 3:41pm

I’ve tried following instructions from Problems with interactive Matlab app window - #16 by djareval

Now my I get a quick connection, but the job failes within seconds. When I can connect, I am still getting Failed to connect to server error message. output.log has changed, though.

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

Desktop 'TurboVNC: node805.host:1 (aadvorki)' started on display node805.host.edu:1

Log file is vnc.log
Successfully started VNC server on node805.host.edu:5901...
Script starting...
Starting websocket server...
+ sleep 5
+ xfwm4 --sm-client-disable

(xfwm4:3721310): xfwm4-CRITICAL **: 10:36:57.213: Xfconf could not be initialized

(xfwm4:3721310): xfwm4-WARNING **: 10:36:57.213: Missing data from default files
[websockify]: pid: 3721340 (proxying 47792 ==> localhost:5901)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...
[websockify]: started successfully (proxying 47792 ==> localhost:5901)
Scanning VNC log file for user authentications...
Generating connection YAML file...
Cleaning up...
Killing Xvnc process ID 3721295

jeff.ohrstrom · November 13, 2024, 4:13pm

Not quite sure what this could be, but there maybe logs at ~/.xfce4-session.verbose-log* or similar. A google search appears to be indicating there’s some issue with your configuration?

You should have ~/.config/xfce4/ (and maybe -session too). Maybe try removing those directories to see if there’s some wrong config in your HOME?

runlolarun · November 13, 2024, 4:25pm

I’ve been trying everything possible to fix this…

I’ve removed ~/.config/xfce4/ - no difference.

I don’t have ~/.xfce4-session.verbose-log* or similar.

runlolarun · November 13, 2024, 5:03pm

more progress. I saw some comments that conda environment might cause it… Removed it.

Now I get below output, but still can’t connect to desktop and job gets killed immediately.

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

Desktop 'TurboVNC: node805.host.edu:1 (aadvorki)' started on display node805.host.edu:1

Log file is vnc.log
Successfully started VNC server on node805.host.edu:5901...
Script starting...
Starting websocket server...
+ sleep 5
+ xfwm4 --sm-client-disable
[websockify]: pid: 3726370 (proxying 41963 ==> localhost:5901)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...

(xfwm4:3726334): xfwm4-WARNING **: 12:00:58.103: Another compositing manager is running on screen 0
[websockify]: started successfully (proxying 41963 ==> localhost:5901)
Scanning VNC log file for user authentications...
Generating connection YAML file...
Cleaning up...
Killing Xvnc process ID 3726319

jeff.ohrstrom · November 13, 2024, 5:09pm

What’s already attached to screen 0?

Topic		Replies	Views
websocket/VNC port range/settings Get Help	5	1181	May 26, 2022
OOD 1.5.5: Cluster config: batch_connect: vnc: environment settings issue Get Help question	10	2444	May 26, 2022
Missing port on the connect URL to vnc sessions Get Help novnc-launch-button , ondemand2	4	222	April 20, 2024
How to modify TurboVNC options for OOD apps? Get Help	2	77	June 17, 2024
VNC Session Failed to connect to server Get Help question	1	159	June 25, 2024

Vnc port configurations

Related topics