Britgirl

[Britgirl]

Logs indicate that the NoMachine display server (integrated in the  nxnode.bin process) is hanging, that’s why your connection fails.

It would be helpful to find the reason of the problem if you can grab withthe GDB tool a backtrace of the hanging process.

To do that, please execute the following instructions in a terminal on the server host:

1. Install GDB if is it’s not already installed.
(http://www.gnu.org/software/gdb/)

2. Run GDB as root or as sudo user:

# gdb -p <pid of nxnode.bin without ‘-H’ in the command line>

3. In the GDB command line type:

set logging file /tmp/displayServerBacktrace.log
set logging on
thr apply all bt

4. Send us the /tmp/displayServerBacktrace.log file.

 

[Britgirl]

Test one bedroom computer, NoMachined into bedroom computer (gigabit ethernet on one wifi ac 5.2GHZ on the other) almost flawless performance(test passed, getting excited), test 2 connect laptop to same bedroom pc that the livingroom pc was NoMachined too(multiple issues) first off doing this killed the connection to the living room pc (it looks to be programmed to do this..

The free version of NoMachine allows one connection at a time. So when you connect a second time from another client to the same server, a dialog should pop up notifying you of this. If you want to be connected multiple times to the same server computer, you should try the evaluation of Enterprise Desktop. This will allow unlimited connections to the same server.

[Britgirl]

Hi, I have opened a new topic so as to keep the issue separate from your previous question:

https://www.nomachine.com/forums/topic/cant-connect-error-is-110-connection-timed-out

[Britgirl]

Can you give some more detail? Are the applications on Linux, or Windows, or other? NoMachinsoftware (any of the products offering the virtual desktop functionality) lets users access single applications (running on Linux) and also Windows if you are accessing over RDP in this case. Which product or products are suitable for you depends on how big your set-up needs to be.

[Britgirl]

Please update to the latest version and let us know if you continue to have problems.

[Britgirl]

Please try to run the following command from a console on the server:

NX_ROOT=/usr/NX NX_SYSTEM=${NX_ROOT} LD_LIBRARY_PATH=${NX_ROOT}/lib:${NX_ROOT}/lib:$LD_LIBRARY_PATH bash -c ‘${NX_ROOT}/bin/nxkeygen -u’

and show us the output.

If command above doesn’t return an error, please try to fix the problem as follows.

1) Remove uuid file:

sudo rm /usr/NX/etc/uuid

2) Update the NoMachine server installation:

sudo /usr/NX/scritps/nxserver –update

Then, please send us the following file:

/usr/NX/var/log/nxupdate.log

[Britgirl]

Can you send us the following?

– /usr/NX/etc/nodes.db
– /usr/NX/etc/uuid
– and whole /usr/NX/var/log directory
Send to issues[at]nomachine[dot]com. Make sure you reference in the title of the topic in the subject.

[Britgirl]

This seems to be an issue with SELinux. We are working on changes to our SELinux modules in order to make it work on FC21. Does disabling SELinux help?

https://docs.fedoraproject.org/en-US/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html

[Britgirl]

This might be of help:

Using two-factor authentication with NoMachine

https://www.nomachine.com/AR12L00828

[Britgirl]

Using the free NoMachine application to connect to the local host will give you a mirrored effect. This is because it’s for connecting to the physical desktop. When you are connecting from the player to server and they are both on the same machine, you will need a product with the virtual desktop functionality. Try the Workstation: https://www.nomachine.com/download-enterprise#NoMachine-Workstation

[Britgirl]

…..a way to disable auto-scrolling in the client window….

There’s a key for viewport scrolling in the player.cfg ($HOME/.nx/config/player.cfg). Set it to 0.

<option key=”Automatic viewport scrolling sensitive area size” value=”40″ />

[Britgirl]

Can you send us the server side logs? You submitted the client side ones but they don’t reveal anything strange.

[Britgirl]

@loadedmind, the logs show you are using a derivative of NX which we are not responsible for. I suggest you contact the appropriate project forum.

[Britgirl]

The current behavior is that when a node is removed from nodes DB, all running sessions are preserved on the remote node. Since the node is removed from the nodes DB, its sessions are no longer listed by ‘nxserver –list’. If the node is re-added to the multi-node server, all sessions can be recovered.

[Britgirl]

They could have been too big for the forums to accept. Send them to the email referenced above and make sure you included the topic title in your subject 😉

[Author]

Posts