Forum Replies Created
-
AuthorPosts
-
HavenParticipant
Hello Sim81,
In attached NX Network server (nxd) logs we can find:Error: Error 98 'Address already in use'.
The default setting of NoMachine is to run connections is via the NX protocol on port 4000.
Did you try to change default NX port?
You can do it by editing /usr/NX/etc/server.cfg file:# # Specify the TCP port where the NX service is listening. # #NXPort 4000
uncomment and change this default value from 4000 to 4001.
After that please execute
/etc/NX/nxserver --restart
to apply changes.Please remember to update port value also on nxplayer side.
- This reply was modified 9 years, 3 months ago by Haven.
HavenParticipantHello gbp9848,
Did you try to change default NX port?
You can do it by editing/usr/NX/etc/server.cfg
file:# # Specify the TCP port where the NX service is listening. # #NXPort 4000
uncomment and change this default value from 4000 to 4001.
After that please execute/etc/NX/nxserver --restart
to apply changes.Please remember to update port value on nxplayer side.
HavenParticipantHello Fsadni,
Please provide installed version of the NoMachine software by executing:
/etc/NX/nxserver --version
You can list running session by executing:
/etc/NX/nxserver --list
To make sure that session was created and was not closed, please provide
output of command:
/etc/NX/nxserver --history
HavenParticipantHello patemery67,
We will need debug NoMachine server logs to investigate further.
Please follow the instructions here:
https://www.nomachine.com/AR07K00677Please enabled debug level logs on multi-node server and on the remote node.
Reproduce the issue and please gather logs from both hosts.
Send them to forum[at]nomachine[dot]comHavenParticipantHello wagometer,
We will 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 X
We need more information about crashed process. Please find the script attached and execute:
./cdebug.sh /usr/NX/bin/nxclient.bin <corefile>
The script will generate a file named <core file>-details.log.
Please send it to us also.
Attachments:
HavenParticipanthello flydeprutten,
We will need debug NoMachine server logs to investigate further.
Please follow the instructions here:
https://www.nomachine.com/AR07K00677Reproduce the problem of the high CPU usage and send logs to forum[at]nomachine[dot]com.
If possible please also install Microsofts ‘Process Explorer’ program.
Check working threads in nxnode process and provide stack from high-consuming CPU thread.HavenParticipantHello ctipat,
Please check/etc/NX/nxserver --history
command it can be useful in to retrieve such information.HavenParticipantHello G,
Thank you for the provided logs. We have identified the issue and have opened a Trouble Report:
https://www.nomachine.com/TR05M05382
You can use the ‘alert me’ check box to know when we have a fix.April 23, 2015 at 10:11 in reply to: Why Are There Two Physical Displays Shown When Connecting? #6999HavenParticipantHello G,
We cannot reproduce the issue in our laboratory,
please try to reproduce the issues with debug logs in nxserver enabled.April 22, 2015 at 08:58 in reply to: Why Are There Two Physical Displays Shown When Connecting? #6983HavenParticipantHello G,
Thank you for submitting logs.
We need to ask for more information to investigate further.In logs you provided we are missing debug level logs from nxserver, please make sure that you set SessionLogLevel key on debug level in file /Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg: ‘SessionLogLevel 7’
The client side logs will be useful, please fallow the article: https://www.nomachine.com/AR04M00843 to gather them.
HavenParticipantHello milosz,
Please make sure that your server has Enterprise version installed by
executing
/usr/NX/bin/nxserver --version
The described behavior is consistent with NoMachine (free version) where profiles and virtual desktops
are not supported.If you want to get access to virtual desktops please remove current
NoMachine software from the server. Also remove /usr/NX directory,
especially make sure that files:/usr/NX/etc/server.lic /usr/NX/etc/node.lic
are deleted before installing: NoMachine Enterprise Server (or one
of the other products offering the same functionality)http://www.nomachine.com/enterprise
https://www.nomachine.com/terminal-serverMarch 26, 2015 at 16:50 in reply to: Per-user desktop environment in NoMachine Workstation not working #6745HavenParticipantHello rjones01,
Please try to set “DefaultDesktopCommand” key without specifying the Gnome or KDE for example:
DefaultDesktopCommand “/etc/gdm/Xsession”
and please make sure that ~/.xsession file has execute rights:
ls -l .xsession
-rwxrwxr-x. 1 nomachine nomachine 6 Mar 26 16:25 .xsessionHavenParticipantHello krusher,
Thank you for submitted logs,
we need to ask for more information.Please provide output of commands:
/etc/NX/nxserver --resourcelist /etc/NX/nxserver --rulelist /etc/NX/nxserver --version
and
/usr/NX/etc/node.cfg /usr/NX/etc/server.cfg
files from the problematic machine.
Please send them to forum[at]nomachine[dot]com.
HavenParticipantHello krusher,
We will 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 X
HavenParticipantHello tominglis,
We will need debug NoMachine Server logs to investigate further. Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comAfter enable debug logs on problematic machine please execute:
/etc/NX/nxserver --restart
and after that gather the logs. -
AuthorPosts