Forum Replies Created
-
Posts
-
Hello vnaipaul,
The “at-exit message shown to the user” will be fixed in the context of mentioned TR.Hello vnaipaul,
Thank you for taking the time to report this.
We reproduced the issue in our labs. Here is the relevant Trouble Report:
https://www.nomachine.com/TR12M06262
Please use the “Notify me” to know when a fix is available.hello macphi,
NoMachine server logs to investigate further.
Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to forum[at]nomachine[dot]com making sure to reference your topic.Hello charleshenry,
Are using the newest NoMachine 5.0.47 (free)?
In this case NoMachine should provide access to current working X server.
Or ask to create X11 display when no X servers are running on this host.Could you provide output of command:
ps -Af | grep X
to confirm what is the current situation?nxplayer by default is keeping all setting in .nx directory in home directory.
You could remove it to make sure that all setting are restored to default.
Note that path to nxplayer setting directory can be changed in ‘setting’ in nxplayer menu.Hello James.Sch,
We are not aware of the such problem. Just based on your description
it could be some issue with settings saved in ‘connection file’.Could you send us the logs as per the instructions here?
https://www.nomachine.com/AR07K00677
Send them to forum[at]nomachine[dot]com making sure to reference the
topic in your email.We are especially interest in nxplayer logs when this issues occurs.
Hello charleshenry,
NoMachine is not suspending the session when user disconnects.
Could clarify you experience? Which Linux distribution are you using?
Which version of NoMachine are you using?
Are you accessing the physical desktop or creating the virtual session?Hello newmanium,
The reason of error:unix-kde is not available on this serverwas because this session type was missing in AvailableSessionTypes key innode.cfg.
During the reinstallation of NoMachine we auto-detect KDE and add this session type to this key.Hello Alex,
None of those errors looks critical.We will more need debug NoMachine server logs to investigate further.
Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to forum[at]nomachine[dot]comAfter enable debug logs on problematic machine please execute:
/etc/NX/nxserver --restart
and after that try to reproduce the issue.Additionally please provide output of command:
ps -Af | grep XPlease make sure that NX is in
ClientConnectionMethodskey in server.cfig file.Hello unlim,
Thanks for bearing with me during the investigation.
We have identified the issue and have opened a Trouble Report:
http://www.nomachine.com/TR10M06073
You can use the ‘alert me’ check box to know when we have a fix.
You could also apply the described workaround.
Please remember to restart nxserver after changing server.cfg file.Hello unlim,
Thank you for new set of logs. Unfortunately I still cannot identify the issue.
We know that running nxserver –daemon process:
nx 13809 1 7 22:38 pts/0 00:00:00 /usr/NX/bin/nxserver.bin root 13770 --daemon
has limit of1024open files. It should be more then enough to work properly.The issue on your system occurs after several hours after ‘restart’.
Could please you keep debug level in the server and provide new set of logs
when thenxserver --daemonprocess will be lost due to error: ‘Too many open files’ ?Hello pvn,
This step:## Replace default SSH keys on E2C instanceis not necessary.
NoMachine (free) does not support SSH protocol.After setting up a tunnel to the E2C instance, you should try to connect
using the following connection settings:Protocol: NX
Host: localhost
Port: 4003
Authentication method: Password
Username: ec2-user
Password: ***If you want to access ‘E2C instance’ with key based authentication
please follow the article: https://www.nomachine.com/AR02L00785The crucial is to add public key to: /home/ec2-user/.nx/config/authorized.crt
Then should try to connect using the following connection settings:Protocol: NX
Host: localhost
Port: 4003
Authentication method: Private-key
Private Key: nomachine.pem (with correct path)
Username: ec2-user
Passphrase: <empty>Hello ostromark,
I cannot recommend any assured way to reserve display for the user.
Could you maybe usenxserver --listcommand output to identify user display?
We have also commandnxserver --messagewhere you can send message to the session, maybe it could be helpful.Hello unlim,
Let’s investigate further.
Please follow those instructions and if possible provide full commands output.Please keep debug level log in
server.cfgfile and perform server restart:
/etc/NX/nxserver --restartthen execute:
ps -Af | grep nxFind
nxserver --daemonprocess PID, and check its limits:
cat /proc/<nxserver --daemon PID>/limits
It’s necessary to verify especially the fields ‘Max open files’Please check also user limits after that ‘nxserver –restart’ command was performed:
ulimit -aS ulimit -aHIf limits are set correctly, please send output of those command with new set of logs.
hello unlim,
Thank you for sending the logs.
In nxserver.log file we can find:Error is: 24, 'Too many open files'.Did you try follow the article:
How to avoid "Too many open files" messages while opening a NX session
from my previous post?Hello unlim,
One of the possible issue that fits described symptoms is crash of
‘nxserver –daemon’ process. This process is vital to provide access
to the physical display. Unfortunately we need full nxserver logs to
find what is exactly going on.
Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Reproduce the issue, please gather logs and send them to forum[at]nomachine[dot]comAs a note, a common case is that the ‘nxserver –daemon’ process
crashes due to “Too many open files” error. If you see in nxserver.log
file error:Error is: 24, 'Too many open files'.
Please follow the instructions from article to fix this:
How to avoid ‘Too many open files’ messages while opening a NX session