500 ERROR: Cannot connect to the requested session

Forums / NoMachine for Windows / 500 ERROR: Cannot connect to the requested session

This topic contains 5 replies, has 4 voices, and was last updated by Avatar Gega 2 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #22792
    Avatar
    tsher
    Participant

    Win7 to RedHat Linux, both NoMachine version is the same 6.7.6 on both sides..

    Attachsession fails with

    500 ERROR: Cannot connect to the requested session. Session with id: 9838E2BA07BFF1EE5FF509D4F84AC661 does not exist.

    The linux side creates the expected dirs

    slc14unw /usr/NX/var/log/node>ls
    F-C-slc14unw-1001-9838E2BA07BFF1EE5FF509D4F84AC661

    But the active session started seems to be on 13E01F5A403A80C32DFF113CDD094013

     

    slc14unw /usr/NX/var/log/node>ps -ef |grep NX
    nx       10883 22459 27 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5
    root     10899 10883  4 11:01 ?        00:00:00 /usr/NX/bin/nxexec –auth
    tsherbec 10902  6551  0 11:01 pts/0    00:00:00 grep –color=auto NX
    nx       22381     1  0 09:13 ?        00:00:01 /usr/NX/bin/nxserver.bin –daemon
    nx       22459 22381  0 09:13 ?        00:00:00 /usr/NX/bin/nxd
    slc14unw /usr/NX/var/log/node>ps -ef |grep NX
    nx       10883 22459 21 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5
    nx       10908 22381  0 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin –virtualsession –sessionid 13E01F5A403A80C32DFF113CDD094013
    root     10924 22381  0 11:01 ?        00:00:00 /usr/NX/bin/nxexec –node –user tsherbec –priority realtime –mode 0 –pid 35
    tsherbec 10926  6551  0 11:01 pts/0    00:00:00 grep –color=auto NX
    nx       22381     1  0 09:13 ?        00:00:01 /usr/NX/bin/nxserver.bin –daemon
    nx       22459 22381  0 09:13 ?        00:00:00 /usr/NX/bin/nxd
    slc14unw /usr/NX/var/log/node>ps -ef |grep NX
    nx       10883 22459 12 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5
    nx       10908 22381 30 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin –virtualsession –sessionid 13E01F5A403A80C32DFF113CDD094013
    root     10924 22381  7 11:01 ?        00:00:00 /usr/NX/bin/nxexec –node –user tsherbec –priority realtime –mode 0 –pid 35
    tsherbec 10932 10924 52 11:01 ?        00:00:00 /usr/NX/bin/nxnode.bin
    tsherbec 11026 10932  0 11:01 ?        00:00:00 /usr/NX/bin/nxclient.bin –monitor –pid 10971
    tsherbec 11116 11026  0 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin –version
    root     11148 11026  0 11:01 ?        00:00:00 /usr/NX/bin/nxexec /etc/NX/nxserver noloop upnpstatus
    root     11165 11116  0 11:01 ?        00:00:00 /usr/NX/bin/nxexec nxlicense.sh
    tsherbec 11191  6551  0 11:01 pts/0    00:00:00 grep –color=auto NX
    nx       22381     1  0 09:13 ?        00:00:01 /usr/NX/bin/nxserver.bin –daemon
    nx       22459 22381  0 09:13 ?        00:00:00 /usr/NX/bin/nxd
    slc14unw /usr/NX/var/log/node>ps -ef |grep NX
    nx       10883 22459 10 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5
    nx       10908 22381 20 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin –virtualsession –sessionid 13E01F5A403A80C32DFF113CDD094013
    root     10924 22381  5 11:01 ?        00:00:00 /usr/NX/bin/nxexec –node –user tsherbec –priority realtime –mode 0 –pid 35
    tsherbec 10932 10924 28 11:01 ?        00:00:00 /usr/NX/bin/nxnode.bin
    tsherbec 11026 10932 28 11:01 ?        00:00:00 /usr/NX/bin/nxclient.bin –monitor –pid 10971
    tsherbec 11910  6551  0 11:01 pts/0    00:00:00 grep –color=auto NX
    nx       22381     1  0 09:13 ?        00:00:01 /usr/NX/bin/nxserver.bin –daemon
    nx       22459 22381  0 09:13 ?        00:00:00 /usr/NX/bin/nxd
    slc14unw /usr/NX/var/log/node>ps -ef |grep NX
    nx       10883 22459  6 11:01 ?        00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5
    tsherbec 11999  6551  0 11:01 pts/0    00:00:00 grep –color=auto NX
    nx       22381     1  0 09:13 ?        00:00:01 /usr/NX/bin/nxserver.bin –daemon
    nx       22459 22381  0 09:13 ?        00:00:00 /usr/NX/bin/nxd
    slc14unw /usr/NX/var/log/node>ls

     

    #22814
    Avatar
    Mth
    Contributor

    Hello.

    First thing, from the process list, the nxserver with parameters

    –virtualsession –sessionid 13E01F5A403A80C32DFF113CDD094013

    means that NoMachine could not find the physical session and is creating a virtual session for you to connect. So the question is, is the machine you are trying to connect to (RedHat) headless, or maybe the Xserver providing service is disabled?

    If you can confirm there is a physical session running on that machine, there is a first problem – NoMachine was not able to detect the physical session.

    Second problem is with that virtual session itself, as you mention the directory

    F-C-slc14unw-1001-9838E2BA07BFF1EE5FF509D4F84AC661

    is created, the information here is that the beginning letter F means this is failed session.

    The most probable scenario here is that this session failed during the connection attempt, which produced the bizarre error that session does not exist.

    The fact that the last process list does not have any nxserver –virtualsession
    process running could mean the sessions are being created and rapidly failing.

    Unfortunately to investigate this issue further, we would require logs.

    Article on how to collect logs:

    https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

    After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s
    thread as the mail’s subject.

    Also please check the node.cfg configuration file, usually located on linux here:

    /usr/NX/etc/node.cfg

    and see if the config key DefaultDesktopCommand is set properly to the desktop environment
    installed on the machine.

    /Mth

    #22886
    Avatar
    tsher
    Participant

    Uploaded logs…

    #22961
    Avatar
    Britgirl
    Keymaster

    @tsher, it seems the logs you sent were not correct. Can you make sure you follow the instructions from Mth carefully and in the article and try sending again?

    #23184
    Avatar
    tsher
    Participant

    Trying again…

    #23258
    Avatar
    Gega
    Participant

    Hello tsher,

    It looks like there’s problem with gnome, there are numerous errors in remote node logs:
    2019-07-10 16:34:12 287.271 18278 NXNODE WARNING! Process ‘/bin/bash -c exec -a – /bin/ksh -c ‘/etc/gdm/Xsession ‘\”gnome-session –session=gnome’\” with pid ‘18316/18316’ finished with exit code 1 after 1,848 seconds.

    .xsession-errors file in user’s home directory or system logs(such as syslog) might show some more information.
    Is that machine headless? Could you confirm that Desktop environment is working properly?

Viewing 6 posts - 1 through 6 (of 6 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.