Can’t connect to SLES 11 SP4 machine

Forums / NoMachine for Linux / Can’t connect to SLES 11 SP4 machine

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #12363
    maleks
    Participant

    Hello,

    Testing NoMachine on a Suse 11 SP4 machine.

    /usr/NX/bin/nxserver –version
    NoMachine – Version 5.1.44

    Client is running Windows 7. Protocol is set to NX. (nomachine_5.1.44_1)

    I see this in the /usr/NX/var/log/nxserver.log when trying to connect:

    2016-09-14 23:05:12 140.956 10590 NXSERVER User ‘maleks’ logged in from ‘xxx.xxx.xxx.xxx’ using authentication method password.
    2016-09-14 23:05:12 929.020 10607 NXSERVER ERROR! Failed to determine the client IP
    2016-09-14 23:05:12 929.129 10607 NXSERVER ERROR! Variables NX_CONNECTION,SSH_CONNECTION,SSH_CLIENT,SSH2_CLIENT not provided.
    2016-09-14 23:05:12 929.189 10607 NXSERVER ERROR! Please set SSHDCheckIP=1 if you want to refuse the connection.
    2016-09-14 23:05:12 929.249 10607 NXSERVER ERROR! Failed to get remote port. Environment NX_CONNECTION,SSH_CONNECTION,SSH_CLIENT,SSH2_CLIENT not set
    2016-09-14 23:05:12 929.315 10607 NXSERVER ERROR! Failed to get local IP. Remote IP is 0.
    2016-09-14 23:05:12 933.803 10607 NXSERVER ERROR! Wrong process id, received pid 0.
    2016-09-14 23:05:12 934.016 10607 NXSERVER WARNING! Could not get SSHD PID: Process 0 does not have expected name.
    2016-09-14 23:05:12 936.417 10607 NXSERVER ERROR! Cannot save forward server pid. ‘value’ for key sshdPid cannot be null
    2016-09-14 23:09:18 780.108 10607 NXSERVER WARNING! Node did not ping since 120 seconds.
    2016-09-14 23:11:38 876.536 10607 NXSERVER ERROR! Node did not ping since 120 seconds. Terminating session.
    2016-09-14 23:11:38 906.256 10607 NXSERVER ERROR! Sending error message ‘NX> 598 ERROR: node does not respond.’
    2016-09-14 23:11:38 906.440 10607 NXSERVER ERROR! <CEF18A8C> Exception:
    2016-09-14 23:11:38 906.501 10607 NXSERVER ERROR! <CEF18A8C> node does not respond at /usr/NX/lib/perl/nxserver/NXPingManager.pm line 36.\n
    2016-09-14 23:11:38 921.868  7947 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user maleks –priority realtime –mode 0 –pid 21’ with pid ‘10619/10619’ finished with exit code 9 after 385,972 seconds.

    Another attempt:

    2016-09-14 23:21:45 061.137 11163 NXSERVER User ‘maleks’ logged in from ‘xxx.xxx.xxx.xxx’ using authentication method password.
    2016-09-14 23:21:45 787.554 11181 NXSERVER ERROR! Failed to determine the client IP
    2016-09-14 23:21:45 787.654 11181 NXSERVER ERROR! Variables NX_CONNECTION,SSH_CONNECTION,SSH_CLIENT,SSH2_CLIENT not provided.
    2016-09-14 23:21:45 787.727 11181 NXSERVER ERROR! Please set SSHDCheckIP=1 if you want to refuse the connection.
    2016-09-14 23:21:45 787.795 11181 NXSERVER ERROR! Failed to get remote port. Environment NX_CONNECTION,SSH_CONNECTION,SSH_CLIENT,SSH2_CLIENT not set
    2016-09-14 23:21:45 787.859 11181 NXSERVER ERROR! Failed to get local IP. Remote IP is 0.
    2016-09-14 23:21:45 793.133 11181 NXSERVER ERROR! Wrong process id, received pid 0.
    2016-09-14 23:21:45 793.261 11181 NXSERVER WARNING! Could not get SSHD PID: Process 0 does not have expected name.
    2016-09-14 23:21:45 796.690 11181 NXSERVER ERROR! Cannot save forward server pid. ‘value’ for key sshdPid cannot be null
    2016-09-14 23:22:16 703.538 11198 NXNODE   WARNING! libnxh::NXConnectLocal cannot connect to localhost:12001: Connection timed out from NXSessionMonitor::__send_to_the_agent.
    2016-09-14 23:27:21 952.251 11181 NXSERVER WARNING! Node did not ping since 120 seconds.

    #12365
    Gega
    Participant

    Hello,

    In order to understand the cause of these problems we need debug logs from the server side. Please uncomment and set the ‘SessionLogLevel 7’ configuration key in the ‘/usr/NX/etc/server.cfg’ and ‘/usr/NX/etc/node.cfg’ files. Here you can find detailed info on how to gather logs: https://www.nomachine.com/DT07M00098.

    Then restart server, reproduce the issue and send the collected logs to forum[at]nomachine[dot]com.

    If it’s not possible to collect debug logs, than sending ‘/usr/NX/var/log/nxerror.log’ might help.

    #12370
    maleks
    Participant

    Hello

    Logs are sent.

    Thanks.

    #13059
    Britgirl
    Keymaster

    The logs show that nxnode hangs for some reason and the and this triggers a series of events: In short, nxserver detects that nxnode finished unexpectedly and sets session status as failed, but the session is not moved to the table of failed sessions.  Upon the second attempt to connect, the session is considered already running (not failed), so your request to connect is aborted.

    We’ve tried to reproduce but without success. What I suggest is you update to 5.1.62 and let us know if the problem continues. We’ll then ask you for further information.

    #13113
    maleks
    Participant

    Hello

    I have upgraded the server (SLES11SP4) and the client (Windows 7) to 5.1.62

    When connecting now I get this error:

    Parameter ‘agentm_display’ has bad value: . Null or wrong parameter ‘display’.

    #13134
    Gega
    Participant

    Hello

    It seems as a different problem so we need new logs, could you collect logs and send them to us the same way as earlier?

    #13187
    maleks
    Participant

    Hello

    I have sent new logs.

    Thanks

    #13597
    Gega
    Participant

    Hello,

    Seems like problem is related to some kind of thread/process limits, two of our components nxclient and nxagent can’t create threads because of some limits which leads to your problem. Are there any limits set by you? If yes than raising this limits and restartingNoMachine should help. If you haven’t set any limit yourself than we need to indentify which limits do we reach exactly, limits could be checked by: 1)ulimit -a 2)cat /proc/sys/kernel/threads-max. command: ps -elfT | wc -l will show number of threads running on system at that moment.

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