Error is 134: Protocol error (Ubuntu)

Forums / NoMachine for Linux / Error is 134: Protocol error (Ubuntu)

Tagged: 

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #14764
    mikeev
    Participant

    Hi,

    I’m a long-term NoMachine user and advocate in the Enterprise space, but I’m having a difficult time getting NX5 free version to work on a headless Ubuntu machine. If I connect a monitor to it, NX5 works fine. Here are the details:

    • Client-side error: Error is 134: Protocol error (Ubuntu)
    • There is no monitor connected (Virtual). Physical works fine (if I connect a monitor obviously).
    • Fresh reinstall of NoMachine 5 Free Version / nomachine_5.2.21_1_amd64.deb
    • CLIENT: Win10 NX5 (latest version)
    • SERVER: Ubuntu 16.04.2 LTS running Unity

    Note: if I keep trying on the client end, sometimes I get alternate client-side errors:

    Could not start the display server.

    Error is 5: Input/output error

    –or–

    Sometimes it’ll connect, but it’ll say <No available sessions on this server>.

    And since this is the free version, I can’t create a new one.</p>

    Logs:

    CLIENT LOGS:

    session (attached).
    SERVER LOGS:

    nxerror.log:

    16851 16906 21:47:38 106.404 DaemonParser/Parser: WARNING! Creating directory '/var/NX/nx/.nx'.
    Info: Handler started with pid 17026 on Thu May 11 21:48:02 2017.
    Info: Handling connection from 192.168.1.8 port 54224 on Thu May 11 21:48:02 2017.
    17026 17026 21:48:11 072.178 File: WARNING! Can't change ownership of '/usr/NX/etc/server.cfg.tmp'.
    17026 17026 21:48:11 072.200 File: WARNING! Error is 1, Operation not permitted.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    Info: Connection from 192.168.1.8 port 54224 closed on Thu May 11 21:48:13 2017.
    Info: Handler with pid 17026 terminated on Thu May 11 21:48:13 2017.
    Info: Handler started with pid 30505 on Thu May 11 22:37:48 2017.
    Info: Handling connection from 192.168.1.8 port 55997 on Thu May 11 22:37:48 2017.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    Info: Connection from 192.168.1.8 port 55997 closed on Thu May 11 22:37:50 2017.
    Info: Handler with pid 30505 terminated on Thu May 11 22:37:50 2017.
    Info: Handler started with pid 1975 on Thu May 11 22:49:52 2017.
    Info: Handling connection from 192.168.1.8 port 56294 on Thu May 11 22:49:52 2017.
    nxexecPAMCheckCredentials: Authentication failed with error 7.
    Info: Connection from 192.168.1.8 port 56294 closed on Thu May 11 22:49:59 2017.
    Info: Handler with pid 1975 terminated on Thu May 11 22:49:59 2017.
    Info: Handler started with pid 2025 on Thu May 11 22:50:00 2017.
    Info: Handling connection from 192.168.1.8 port 56297 on Thu May 11 22:50:00 2017.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    16851 16851 22:50:34 124.548 Ancillary: ERROR! Can't connect to the requested socket.
    16851 16851 22:50:34 124.611 Ancillary: ERROR! Error is 2 'No such file or directory'.
    nxexecExecNode: Info: Cant not restore saved resource limits.
    Info: Connection from 192.168.1.8 port 56297 closed on Thu May 11 22:50:44 2017.
    Info: Handler with pid 2025 terminated on Thu May 11 22:50:44 2017.
    Info: Handler started with pid 3177 on Thu May 11 22:51:45 2017.
    Info: Handling connection from 192.168.1.8 port 56328 on Thu May 11 22:51:45 2017.
    Info: Connection from 192.168.1.8 port 56328 closed on Thu May 11 22:51:47 2017.
    Info: Handler with pid 3177 terminated on Thu May 11 22:51:47 2017.
    Info: Handler started with pid 3204 on Thu May 11 22:51:49 2017.
    Info: Handling connection from 192.168.1.8 port 56332 on Thu May 11 22:51:49 2017.
    Info: Connection from 192.168.1.8 port 56332 closed on Thu May 11 22:52:53 2017.
    Info: Handler with pid 3204 terminated on Thu May 11 22:52:53 2017.
    

     

    nxserver.log:

    2017-05-11 21:47:38 093.935 16851 NXSERVER Starting NoMachine server 5.2.21 and services.
    2017-05-11 21:48:06 157.639 17026 NXSERVER User 'mikeev' logged in from '192.168.1.8' using authentication method password.
    2017-05-11 21:48:11 072.241 17026 NXSERVER WARNING! Cannot chown to: file: /usr/NX/etc/server.cfg.tmp: 1, Operation not permitted.
    2017-05-11 21:48:13 292.769 17080 NXSERVER WARNING! Cannot retrieve node socket for session E96FF4747BD85BB8CC463DEF423275E3.
    2017-05-11 21:48:13 361.204 17095 NXNODE ERROR! Application terminated too early.
    2017-05-11 21:48:13 362.866 17080 NXSERVER ERROR! Sending error message 'NX> 501 ERROR: Session failed, application terminated prematurely.'
    2017-05-11 21:48:13 432.968 17095 NXNODE WARNING! Process '/usr/bin/pulseaudio --high-priority=no' with pid '17192/17192' finished with exit code 1 after 1,497 seconds.
    2017-05-11 21:48:24 464.515 17026 NXSERVER User 'mikeev' from '192.168.1.8' logged out.
    2017-05-11 22:37:48 443.179 30505 NXSERVER User 'mikeev' logged in from '192.168.1.8' using authentication method password.
    2017-05-11 22:37:50 924.364 30522 NXSERVER WARNING! Cannot retrieve node socket for session 731443D0B30523DF4F170B462294D4E5.
    2017-05-11 22:37:51 027.306 30537 NXNODE ERROR! Application terminated too early.
    2017-05-11 22:37:51 029.365 30522 NXSERVER ERROR! Sending error message 'NX> 501 ERROR: Session failed, application terminated prematurely.'
    2017-05-11 22:37:51 099.449 30537 NXNODE WARNING! Process '/usr/bin/pulseaudio --high-priority=no' with pid '30639/30639' finished with exit code 1 after 1,790 seconds.
    2017-05-11 22:37:55 329.984 30505 NXSERVER User 'mikeev' from '192.168.1.8' logged out.
    2017-05-11 22:49:59 871.872 1975 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --auth' with pid '2014/2014' finished with exit code 1 after 1,864 seconds.
    2017-05-11 22:49:59 872.087 1975 NXSERVER ERROR! Error while trying to authenticate user: mikeev using authentication method password. NXNssUserManager::auth returned 1
    2017-05-11 22:49:59 872.247 1975 NXSERVER ERROR! wrong 'nxexec authentication' for user 'mikeev' from '192.168.1.8'.
    2017-05-11 22:49:59 872.319 1975 NXSERVER ERROR! Sending error message 'NX> 404 ERROR: Wrong password or Login.'
    2017-05-11 22:50:04 772.678 2025 NXSERVER User 'mikeev' logged in from '192.168.1.8' using authentication method password.
    2017-05-11 22:50:06 957.673 2075 NXNODE ERROR! Application terminated too early.
    2017-05-11 22:50:06 959.141 2060 NXSERVER ERROR! Sending error message 'NX> 501 ERROR: Session failed, application terminated prematurely.'
    2017-05-11 22:50:06 989.040 2075 NXNODE WARNING! Process '/usr/bin/pulseaudio --high-priority=no' with pid '2177/2177' finished with exit code 1 after 1,345 seconds.
    2017-05-11 22:50:07 032.795 2060 NXSERVER WARNING! Cannot retrieve node socket for session 93BFE26C90270E74BB8F6901AB9D10D9.
    2017-05-11 22:50:07 047.194 2025 NXSERVER WARNING! Connection to node closed unexpectedly.
    2017-05-11 22:50:34 124.744 16851 NXSERVER ERROR! Cannot acquire descriptor from pid 2060. Error is: 2 ENOENT No such file or directory
    2017-05-11 22:50:34 124.863 16851 NXSERVER WARNING! Failed to acquire descriptor from server 2060 and /tmp/session-93BFE26C90270E74BB8F6901AB9D10D9.
    2017-05-11 22:50:44 092.313 2025 NXSERVER ERROR! Node did not terminate in 3 seconds.
    2017-05-11 22:50:44 105.933 2025 NXSERVER User 'mikeev' from '192.168.1.8' logged out.
    2017-05-11 22:51:45 674.207 3177 NXSERVER User 'mikeev' logged in from '192.168.1.8' using authentication method password.
    2017-05-11 22:51:47 388.288 3177 NXSERVER User 'mikeev' from '192.168.1.8' logged out.
    2017-05-11 22:51:54 014.017 3204 NXSERVER User 'mikeev' logged in from '192.168.1.8' using authentication method password.
    2017-05-11 22:52:53 590.742 3204 NXSERVER User 'mikeev' from '192.168.1.8' logged out.
    #14776
    brotech
    Participant

    Hello,
    the problem is that the application run terminated immediately. We can see:
    2017-05-11 22:50:06 957.673 2075 NXNODE ERROR! Application terminated too early.

    So please check DefaultDesktopCommand key in node configuration key, and set it according to
    to your needs. There is also article about: https://www.nomachine.com/AR04K00667

    #14782
    mikeev
    Participant

    Thanks for the reply. This seems to have had no effect. Are you sure that linked article is relevant? I don’t care about which virtual desktop environment is selected. I just want it to work.

    #14844
    zaq
    Contributor

    Hello mikeev

    We couldn’t reproduce your problem in our laboratory. We need more
    information. Please follow steps below:

    1. Check if you have installed desktop environment. Please send
    the output to us.

    dpkg -l ubuntu-desktop

    ls -l /etc/X11/Xsession

    2. Check if Xorg process exists. Please send the output to us.

    ps -ef | grep -i xor | grep -v grep

    3. Gather logs:

    a) Edit the /usr/NX/etc/server.cfg file. Uncomment and set the
    following:

    SessionLogLevel 7

    b) Edit the /usr/NX/etc/node.cfg file. Uncomment and set the
    following:

    SessionLogLevel 7

    and:

    SessionLogClean 0

    c) Reboot nxserver:

    sudo /usr/NX/bin/nxserver --restart

    d) Reproduce the problem – try create connection to Ubuntu headless
    when monitor isn’t connected.

    4. Pack the whole log directory:

    tar czf log.tar.gz /usr/NX/var/log

    5. Send the log archive to forum[at]nomachine[dot]com

    #14913
    mikeev
    Participant

    Apologies for the late reply- I’ve been trying a number of different things in the meantime, but nothing quite works. I’ll send the logs above, but I was wondering if we could take an alternate approach? Can you please provide a procedure on how to install Ubuntu to act as a headless NX server (free version)?

    Here’s what I’m doing now (to get to the point where these logs occurred):

    1. Install Ubuntu Server (on a AMD Ryzen + NVIDIA GTX 1080).

    2. Install ubuntu-gnome-desktop.

    3. Install NX

    4. Connect to Ubuntu server via Win10. Confirm that it works (I can see Gnome fine).

    5. Shutdown Ubuntu Server. Disconnect monitor.

    6. Turn on Ubuntu Server

    7. Connect to Ubuntu server via Win10. Observe that it’s a black screen.

     

    In the original post I couldn’t connect at all. Now all I see is a black screen. I consider that progress, but I’d still like to get this working. This is a clean install that I’m doing and I am able to wipe everything and start over. Can you please try to produce a headless Ubuntu Gnome NX server (no monitor connected) in your lab and tell me what I’m doing wrong?

    #14944
    zaq
    Contributor

    Hi mikeev,

    Looks like your graphic card without a connected monitor works
    in power save mode and doesn’t draw graphics properly. This is
    the reason why you got black screen. The solution is to disable
    graphical runlevel of your headless Ubuntu 16.04. You can simple
    run:

    sudo systemctl stop gdm.service

    sudo /etc/NX/nxserver --restart

    You should got expected warning about X server.

    sudo systemctl set-default -f multi-user.target

    Now you can connect to the machine and NoMachine create graphical
    session. If you got problems with resolution you can change it in
    display settings:

    https://www.nomachine.com/changing-how-you-view-the-remote-host

    If you want to restore your previous default runlevel just execute:

    sudo systemctl set-default -f graphical.target

    and after next reboot your OS should display Gnome.

    #14972
    mikeev
    Participant

    Hi Zag,

    I tried what you suggested, and I continue to get a black screen. Any other ideas? Can you try to create a headless Ubuntu system on your end?

    Thanks!

    #14987
    Britgirl
    Keymaster

    @mikeev, we’ll need logs again as per Zaq’s instructions for the last time.

    We have no issues setting up a headless system with NoMachine on Ubuntu, that’s why we ask for logs 😉

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.