No available sessions on this server on RHEL

Forum / NoMachine for Linux / No available sessions on this server on RHEL


Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #2566

    I am a new NoMachine user, and I am trying to use NoMachine to connect to a RHEL instance on Amazon EC2. I tried to follow the instructions from this post:

    But when I try to connect, I get the “No available sessions on this server” error.

    I can ssh into the instance, and check the status:

    $ ./nxserver –status
    NX> 161 Enabled service: nxserver.
    NX> 161 Enabled service: nxd.

    The Amazon EC2 security group firewall has been set to open port 4000. The RHEL instance also has port 4000 open. GNOME has been installed and enabled, /etc/initab has been set to boot in GUI mode.


    The article explains how to use version 3.5.0 and needs to be updated by the author (since we don’t make version 3.5.0 available any longer).

    For headless Linux servers where you have NoMachine 4 installed, you should check the instructions here:




    I have the “No available sessions…” error showing up on the client. I am running a fresh install of Centos6.4 and have installed an X environment on a headless VPS (OpenVZ) and I followed the directions here to setup the headless server:

    Everything goes fine until the last command to start the gnome desktop manager. It fails to start properly – from .xsession-errors:

    gnome-session[10429]: WARNING: Unable to determine session: Unable to lookup session information for process ‘10429’

    Xlib: extension “RANDR” missing on display “:0”.




    and from the NX server log:

    2014-03-07 03:26:12 848.159 NXNODE-4.1.29[2283] ERROR: shutdown: cannot remove a

    gent authority cookies, giving up

    2014-03-07 03:26:12 849.031 NXNODE-4.1.29[2283] ERROR: session monitor: cleaning

    session files: cannot remove dir ‘/home/paraic/.nx/

    5281CA00E82EAAADAC8250260D8F799/pids’: No such file or directory

    That dir at /home/paraic doesn’t exist and the .nx is owned by user paraic and perms 700.

    So when I connect occasionally I will get the basic desktop but its in suspend mode and I can’t click on anything on it.

    Any ideas or other things to check?




    Can you update to 4.2.15 and let us know if you are still having problems?

Viewing 4 posts - 1 through 4 (of 4 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.