Forum Replies Created
-
Posts
-
Logs would be useful as an nxserver process running at 100% is not normal. Follow the instructions here and submit to issues[at]nomachine[dot]com making sure you reference your forum title.
https://www.nomachine.com/AR07K00677
I would like to prevent nxserver to start at every reboot. Is there a way to do it?
See the image I attached. You can access this via the !M (Monitor) icon in the task/system try and then select ‘Show the connection status’. Click on the on/off button and the dialog should appear.
Attachments:
root@rainkin:~# xauth -f $AUTHFILE add :0 MIT-MAGIC-COOKIE-1 $COOKIE
xauth: file add does not existThis means that $AUTHFILE was not set. I.e it’s empty.
Are you executing this? AUTHFILE=$HOME/Xvfb-0.auth
After that step you can do: echo $AUTHFILE to ensure that the variable was correctly set.
If you are using one of the terminal server range (you posted your topic in the section for this range of products) you can simply start a virtual session without having to do any of the above.
But, as I see, number of files in ICE directory still increasing, but not so quick :
[root@termserv8-med ~]# find /tmp/.ICE-unix/ | wc -l
342Further investigation shows that this is a leak from Gnome resources and not leftovers of NoMachine.
For single application, so running just Firefox rather than connecting to the desktop (Gnome or KDE etc) you need to select “Custom session”.
See here: https://www.nomachine.com/AR03L00795
We reproduced it and have opened a TR. Thanks for reporting it. https://www.nomachine.com/TR01M04797
There is a Trouble Report open for this. Please try the workaround.
NoMachine services don’t start on Fedora 21
https://www.nomachine.com/TR0104791Issues concerning the 3.5.0 server version are dealt with via the traditional channels. The forums are specifically for version 4 client/server issues. If you are able to reproduce this problem connecting from a client 4 to a server 4, please open a new post. You can contact the team using the Contact Us in the footer of the website. Thanks.
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 bt4. Send us the /tmp/displayServerBacktrace.log file.
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.
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
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.
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
