Cannot connect to server (MDM XFCE4)

Forum / NoMachine for Linux / Cannot connect to server (MDM XFCE4)

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #17180
    molokovskikh
    Participant

    Hello everybody!

    I confront with strange issue.

    Subj is only on Linux machine.

    Desktop Xfce4  (Linux Mint 17)

    Display manager MDM (earlier was LightDM, when was working fine, before update)

    $ uname -a

    Linux ixy 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

    $ /usr/NX/bin/nxserver –version

    NoMachine – Version 6.0.66

    On client I see clear white window.

    After fews minutes, on client occured message error 138: Timeout.

    I tried client on Windows 7, Android. Is result same.

    On server which described above is:

    in /usr/NX/var/log/nxerror.log

    Info: Handler started with pid 18386 on Wed Jan 17 12:22:10 2018.

    Info: Handling connection from 192.168.132.2 port 57509 on Wed Jan 17 12:22:10 2018.

    Info: Connection from 192.168.132.2 port 57509 closed on Wed Jan 17 12:23:24 2018.

    Info: Handler with pid 18386 terminated on Wed Jan 17 12:23:24 2018.

    Info: Handler started with pid 18736 on Wed Jan 17 12:23:27 2018.

    Info: Handling connection from 192.168.132.2 port 59854 on Wed Jan 17 12:23:27 2018.

    Info: Connection from 192.168.132.2 port 59854 closed on Wed Jan 17 12:24:11 2018.

    Info: Handler with pid 18736 terminated by signal 15 on Wed Jan 17 12:24:11 2018.

     

    in /usr/NX/var/log/nxserver.log

    retried warning

    2018-01-19 11:10:46 785.853 26858 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1

    2018-01-19 11:10:46 980.795 26858 NXSERVER NXOpen FD#28 – file /usr/NX/var/log/nxerror.log with mode 1089 and permissions 384 from Common::NXRunCommand::__setupParentChildStderr.

    2018-01-19 11:10:46 997.267 26858 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh xfce4-session   xfce4-session’ with pid ‘28257/28257’ finished with exit code 1 after 0,013 seconds.

    2018-01-19 11:10:46 997.828 26858 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1

    2018-01-19 11:10:47 260.146 26858 NXSERVER NXOpen FD#28 – file /usr/NX/var/log/nxerror.log with mode 1089 and permissions 384 from Common::NXRunCommand::__setupParentChildStderr.

    2018-01-19 11:10:47 272.759 26858 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh xfce4-session   xfce4-session’ with pid ‘28262/28262’ finished with exit code 1 after 0,009 seconds.

    2018-01-19 11:10:47 273.299 26858 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1

    2018-01-19 11:10:47 472.915 26858 NXSERVER NXOpen FD#28 – file /usr/NX/var/log/nxerror.log with mode 1089 and permissions 384 from Common::NXRunCommand::__setupParentChildStderr.

    2018-01-19 11:10:47 487.999 26858 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh xfce4-session   xfce4-session’ with pid ‘28267/28267’ finished with exit code 1 after 0,011 seconds.

    2018-01-19 11:10:47 488.573 26858 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1

    2018-01-19 11:10:47 724.006 26858 NXSERVER NXOpen FD#28 – file /usr/NX/var/log/nxerror.log with mode 1089 and permissions 384 from Common::NXRunCommand::__setupParentChildStderr.

    2018-01-19 11:10:47 738.900 26858 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh xfce4-session   xfce4-session’ with pid ‘28272/28272’ finished with exit code 1 after 0,011 seconds.

    2018-01-19 11:10:47 739.542 26858 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1

     

    More concrete error, sounds as “NX> 500 Error: Cannot find environment for process xfce4-session   xfce4-session’

     

    I investigated the call so bad next parameter “xfce4-session xfce4-session”.

    There expect like “1234/1234” because it is $PROCESS_ID.

    What is proccess id? How I can find out it?

     

    #17190
    molokovskikh
    Participant

    There attached log files

    #17192
    molokovskikh
    Participant
    #17195
    og00r
    Contributor

    About those warnings there is such problem described here:
    https://www.nomachine.com/TR12O08309

    but problem should not affect conenction to session, only some mess in logs.
    Can you please paste output of “ps -ef | grep X”?

    Is there any warning during nxserver –restart?
    During connection there was question about creating new display because nomachine did not find any?
    Or it just white window after connection without anything?

    If it is second option can you check client logs?
    These logs are located on machine where nxplayer is used, in user home directory. For example you say, that tried connect from windows.
    To find it, write the following in the address bar or the file browser:
    %USERPROFILE%\.nx
    As an alternative, you may navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach this hidden folder.
    Path can be similar to: C:/Users/nomachine/.nx

    #17203
    Britgirl
    Keymaster

    Please send any logs to forum[at]nomachine[dot]com. Thanks!

    #17212
    molokovskikh
    Participant

    About those warnings there is such problem described here: https://www.nomachine.com/TR12O08309

    Similar as my problem, txh .. will see it.

    Can you please paste output of “ps -ef | grep X”?

    nx 2440 1 0 12:59 ? 00:00:01 /usr/NX/bin/nxserver.bin –daemon

    nx 3452 2440 0 12:59 ? 00:00:00 /usr/NX/bin/nxserver.bin –virtualsession –sessionid 9C967A23B1C6F720C77BA74E9F18321A

    root 3477 2440 0 12:59 ? 00:00:00 /usr/NX/bin/nxexec –node –user sergey –priority realtime –mode 0 –pid 14

    root 3479 3472 2 12:59 tty8 00:10:32 /usr/lib/xorg/Xorg :0 -audit 0 -auth /var/lib/mdm/:0.Xauth -nolisten tcp vt8

    sergey 3640 3477 6 12:59 ? 00:27:48 /usr/NX/bin/nxnode.bin

    sergey 4317 4232 0 13:00 ? 00:00:00 /bin/sh /etc/xdg/xfce4/xinitrc — /etc/X11/xinit/xserverrc

    sergey 4422 3640 0 13:00 ? 00:00:00 /usr/NX/bin/nxclient.bin –monitor –pid 4232

    sergey 4489 3997 0 13:00 ? 00:00:00 /bin/sh /etc/xdg/xfce4/xinitrc — /etc/X11/xinit/xserverrc

    nx 4616 2440 0 13:00 ? 00:00:00 /usr/NX/bin/nxd -p 4000

    root 11670 7630 0 20:17 pts/0 00:00:00 sudo tail -f /usr/NX/var/log/nxserver.log

    root 11671 11670 0 20:17 pts/0 00:00:00 tail -f /usr/NX/var/log/nxserver.log

    nx 11885 4616 0 20:18 ? 00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5

    sergey 12571 12091 0 20:20 pts/6 00:00:00 grep –color=auto X

    nx 29852 4616 0 13:52 ? 00:00:01 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 5

    root 29976 29852 0 13:52 ? 00:00:00 /usr/NX/bin/nxexec –node –user sergey –priority realtime –mode 0 –pid 13 -H 5

    sergey 29987 29976 0 13:52 ? 00:00:02 /usr/NX/bin/nxnode.bin -H 5

    Is there any warning during nxserver –restart?
    During connection there was question about creating new display because NoMachine did not find any?
    Or it just white window after connection without anything?

    No warning. Was no question.

    Just white … you can to look video.

    #17216
    molokovskikh
    Participant

    When I did as recommended in Trouble Report https://www.nomachine.com/TR12O08309.

    I was seeing such screen.

    No available sessions on this server

    #17223
    og00r
    Contributor

    You should not use workaround from this TR, because it removes physical session from connection options.

    27645 27677 11:37:09 255.702 TcpListener/Listener: WARNING! Refusing connection from ‘192.168.132.2’ port 39***.
    Warning: Refusing connection from ‘192.168.132.2’ port 39***.

    Looks like there could be problem with loopback for localhost when you connect. Do you have any changes in network configuration?

    Standard name for loopback in Linux is lo:
    ip addr show dev lo

    #17265
    molokovskikh
    Participant

    I have similar problem with another application based on java stack.

    In that case i had have error “refused connection” (in gradle plugin for IDEA).

    I need to investigate my OS in details. It seems they are related…

    #17301
    Britgirl
    Keymaster

    @molokovskikh, it’s worth checking the loopback configuration as ‘og00r’ suggested. Let us know what you find.

    #17741
    molokovskikh
    Participant

    Hello everybody again!

    My issue resolved after update to version 6.0.78.

    Can close topic!

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

This topic was marked as solved, you can't post.