Custom-Session connection to the server was lost

Forums / NoMachine Terminal Server Products / Custom-Session connection to the server was lost

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #1555
    Anonymous
    Inactive

    Hi

    We are evaluating nomachine-terminal-server. Actual we are running version 4.0.369_2. The problem descriped in the ticket https://www.nomachine.com/TR10K03974 should be resolved in this version but it already occurs.

    We use gnome-terminal as custom-session. Connection is via port 22 and ssh. Running the command in a virtual desktop works but that is a no go for us.

    Best regards

    #1730
    Britgirl
    Keymaster

    Can you tell us what Linux distribution and version you are using on the server side. What OS on the client side? Steps to reproduce.

     

    #1751
    Anonymous
    Inactive

    Server side: Red Hat Enterprise Linux Server 6.5 (x86_64, Kernel 2.6.32-431.3.1.el6.x86_64)

    Client side: Windows 7 SP1 64Bit

    Steps to reproduce:

    1. Connect to nx-server via nomachine client
    2. Choose <New virtual desktop or custom session>
    3. Choose “Create a new custom session”
    4. Use gmome-terminal in the “Run the following command” (Options: “Run the command in a floating window”)
    5. Click connect
    6. Error: “The connection with the server was lost. Error is 134: Protocol error.”

    Logfiles from clientside are attached.

    #1828
    Britgirl
    Keymaster

    We aren’t able to reproduce it. Can you submit the server side logs, please?

    #2038
    Anonymous
    Inactive

    Did a complete shutdown of nxserver, deleted all logfiles, restart nx and tried to log in via client. This are the entries in the nxserver.log:

     

    12:43:25:471.472 NXSERVER-4.0.369[25574] User ‘xxxxx’ logged in from ‘172.20.9.73’.

    12:43:37:808.262 NXNODE-4.0.369[25653] ERROR: NXPL::NXSelect(22,7) exited with error ‘Interrupted system call’.

    12:43:38:161.178 NXNODE-4.0.369[25653] ERROR: Audio cleanup: cannot remove audio directory ‘/usr/users/MSummer/.nx/C-adzh-srlt-en12.intern.cube.ch-1001-FA1485A3E35B6350ADEC8CD271A7E3E0/audio’: Directory not empty

    12:43:38:992.236 NXNODE-4.0.369[25653] ERROR: session monitor: cleaning session files: cannot remove dir ‘/usr/users/MSummer/.nx/C-adzh-srlt-en12.intern.cube.ch-1001-FA1485A3E35B6350ADEC8CD271A7E3E0/audio’: Directory not empty

    12:43:38:992.605 NXNODE-4.0.369[25653] ERROR: session monitor: cleaning session files: cannot remove dir ‘/usr/users/xxxx/.nx/C-adzh-srlt-en12.intern.cube.ch-1001-FA1485A3E35B6350ADEC8CD271A7E3E0/scripts’: Directory not empty

    12:43:38:992.763 NXNODE-4.0.369[25653] ERROR: session monitor: cleaning session files: cannot remove dir ‘/usr/users/xxxx/.nx/C-adzh-srlt-en12.intern.cube.ch-1001-FA1485A3E35B6350ADEC8CD271A7E3E0’: Directory not empty

    12:43:39:006.188 NXSERVER-4.0.369[25574] User ‘xxxxxx’ from ‘172.20.9.73’ logged out.

    The other logfiles are empty.

    #2096
    Anonymous
    Inactive

    Did a clean OS installation an then installed nomachine-terminal-server-evaluation_4.0.370_2_x86_64.rpm. Same behavior when try to create a custom session.

    #2097
    Anonymous
    Inactive

    If you want, we can give you our kvm-image to reproduce the error.

    #2107
    Britgirl
    Keymaster

    That would be very helpful. Can you send us details? Contact us at isses[at]nomachine.com so that any sensitive data is not published on the forums.

    #2632
    Anonymous
    Inactive

    Sorry for the late replay. We have uploaded the complete kvm-image to our download-portal. Could you please give me an mailadress to wich i can send informations about the download? The isses[at]nomachine.com is:

    Recipient address rejected: User unknown in local recipient table

    regards

    beduine

    #2635
    Britgirl
    Keymaster

    My fault, there was a typo in the email address: issues[at]nomachine.com. Sorry. Send them again.

    #2636
    HPCAdmin
    Participant

    Hello from HPC Laboratuaries in Turkey

    We are evaluating your product and everything was fine until we got this error today.

    Our env. is Windows 7.1 SP1 and CentOS 6.4  Kernel 2.6.32-431.5.1.el6.x86_64

     

    #2784
    Anonymous
    Inactive

    Hi

    We switched from ssh to NX-protocol (port 4000) but it is not possible to open a custom session. Always the same error.

    regards

    #2773
    Anonymous
    Inactive

    Did a clean install of nomachine-terminal-server-evaluation_4.1.29_6_x86_64.rpm and updated my Windows-Client to the newest version. Problem already exists. For us, this is a killer-bug.

    #2843
    Anonymous
    Inactive

    The solution was to open port 4777 in our firewall-setup. This port is also needed when connecting via ssh.

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

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