- This topic has 2 replies, 2 voices, and was last updated 4 years, 11 months ago by
.
-
Posts
-
I am using NoMachine(free) 6.9.2_1 on a Centos 7 docker container.
I get these lines from the log file:
2020-01-23 07:58:04 199.240 9805 NXSERVER User ‘foo’ logged in from ‘<ip>’ using authentication method NX-password.
2020-01-23 07:58:07 706.940 9753 NXSERVER WARNING! Cannot retreive nxnode PID for virtual server 3931A126055399909121263DEE9ADAFF.
2020-01-23 07:58:07 707.312 9825 NXSERVER ERROR! Cannot start node to create session
2020-01-23 07:58:07 707.571 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user awips –priority realtime –mode 0 –pid 21’ with pid ‘9840/9840’ finished with exit code 1 after 0,004 seconds.
2020-01-23 07:58:07 709.438 9753 NXSERVER ERROR! NXFrameBuffer failed to start.
2020-01-23 07:58:07 709.544 9753 NXSERVER ERROR! Received error message from nxserver NX> 595 Server could not establish communication with local node.
2020-01-23 07:58:07 710.256 9805 NXSERVER ERROR! Received error from nxserver –daemon NX> 595 Server could not establish communication with local node.
2020-01-23 07:58:07 747.406 9805 NXSERVER User ‘foo’ from ‘<ip>’ logged out.
2020-01-23 07:58:12 976.735 9842 NXSERVER User ‘foo’ logged in from ‘<ip>’ using authentication method NX-password.
2020-01-23 07:58:18 821.654 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9860/9860’ finished with exit code 1 after 0,004 seconds.
2020-01-23 07:58:18 821.845 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:58:18 826.855 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9861/9861’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:58:18 827.052 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:58:18 831.944 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9862/9862’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:58:18 832.134 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:58:18 837.481 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec nxcookieget.sh /bin/xauth root 99 /home/awips/.Xauthority’ with pid ‘9863/9863’ finished with exit code 1 after 0,004 seconds.
2020-01-23 07:58:18 842.874 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9864/9864’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:58:18 843.068 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:59:19 923.942 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9868/9868’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:59:19 924.159 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:59:19 929.465 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9869/9869’ finished with exit code 1 after 0,004 seconds.
2020-01-23 07:59:19 929.638 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:59:19 934.735 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9870/9870’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:59:19 934.905 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
2020-01-23 07:59:19 940.038 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec nxcookieget.sh /bin/xauth root 99 /home/awips/.Xauthority’ with pid ‘9871/9871’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:59:19 945.058 9753 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxenvironmentget.sh 9650’ with pid ‘9872/9872’ finished with exit code 1 after 0,003 seconds.
2020-01-23 07:59:19 945.231 9753 NXSERVER WARNING! __getProcessEnvironment /usr/NX/scripts/restricted/nxenvironmentget.sh finished with 1
NoMachine has successfully started with Xvfb running but when I try to login it gives me “No available sessions on this server”
nx 9753 0.1 0.2 643580 72808 pts/1 Sl 07:57 0:00 /usr/NX/bin/nxserver.bin root 9745 –daemon
nx 9786 0.0 0.0 336984 4084 pts/1 Sl 07:57 0:00 /usr/NX/bin/nxd
nx 9842 0.2 0.2 599596 70788 pts/1 Sl 07:58 0:01 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 4
foo 9928 0.0 0.1 223964 34268 pts/1 Sl 08:05 0:00 Xvfb :0 -auth /home/awips/Xvfb-0.auth -screen 0 1680x1050x24
foo 9937 3.0 0.0 71624 6184 pts/1 S 08:08 0:00 fluxbox
Any idea what I am doing wrong here?
More Info, I followed this post exactly https://www.nomachine.com/AR10K00710
Then followed by /usr/NX/bin/nxserver –restart
Even though Xvfb is started on :0 and fluxbox is running on DISPLAY=:0, Nomachine still says there are no sessions available on this server
Hello.
For now it seems the problem is not with Xvfb, but with the NoMachine processes and docker itself.
It seems we want to make this display visible, but every process dies with exit code 1.First we need to check if the container is properly run. We have a document on this topic:
https://www.nomachine.com/DT10O00161
Most commonly there are problems with apparmor blocking the docker container from running
processes using nxexec. Please check the troubleshooting part of that document.There also can be a problem with the privileges on the container, I found that on one specific machine
with Mint I need to add –privileged parameter to docker run command.If the article does not help you, please check if there is anything in the system logs that could
be relevant to starting any nx processes (any access blocking, termination etc.). Also please share
the Dockerfile and the command you use to start the container. With this it should be easy for us
to reproduce the problem to find a solution./Mth
This topic was marked as solved, you can't post.