VNC Troubleshooting on the UFS HPC

Introduction

This page contains troubleshooting information for using VNC sessions on the UFS HPC.

The guide is organized into the following sections:

  • Creating a VNC session
  • Connecting to a VNC session

Creating a VNC session

  • The error: "bash: qnvc: command not found..." is produced when trying to run qvnc.

    The qvnc command is loaded as part of a container. Some users have containers being loaded by default when they log in (done via the .bashrc script). The solution in this case is to module load a container. For example:

    $ module load bioinformatics

  • A user can only run one VNC session at a time. When executing qvnc with an active session, the user will be prompted to delete the currently active session, after which the new session can be created (given that the requested resources are available).

    pre-active-vnc-sesh

  • When the user requests more resources (cores and memory) than is currently available on the HPC, qvnc will exit with the following error message:

    vnc_job_denied

    In such cases the user will need to adjust the resources and time requested to align with the resources avialible on the cluster. Use this guide to customize the amount of resources and time requested with qvnc.