- This topic has 3 replies, 3 voices, and was last updated 4 years, 9 months ago by
.
-
Posts
-
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | groupadd: group ‘user’ already exists
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | NX> 111 New connections to NoMachine server are enabled. inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | NX> 161 Enabled service: nxserver.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | NX> 162 WARNING: A new virtual display will be created on demand.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | NX> 161 Enabled service: nxd.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:11 635.490 16 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user user –priority realtime –mode 0 –pid 10′ with pid ’28/28’ finished with exit code 1 after 0,007 seconds.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:11 641.214 16 NXSERVER Starting LS 6.5.6 and services.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:11 641.293 16 NXSERVER System information: Ubuntu 18.04.3 LTS, standalone.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:11 649.511 16 NXSERVER WARNING! Process ‘/usr/bin/dbus-send –system –dest=org.freedesktop.DBus –type=method_call –print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames’ with pid ’29/29′ finished with exit code 1 after 0,005 seconds.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:11 650.762 16 NXSERVER WARNING! Command for net statistics not found.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:12 168.555 16 NXSERVER WARNING! Cannot retreive nxnode PID for virtual server 6C040BA491C5EF33A56A1F3127E29576.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:12 169.168 16 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user user –priority realtime –mode 0 –pid 14′ with pid ’45/45’ finished with exit code 1 after 0,008 seconds.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:12 169.578 30 NXSERVER ERROR! Cannot start node to create session
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:12 172.207 16 NXSERVER ERROR! NXFrameBuffer failed to start. inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:12 268.800 16 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec /usr/NX/scripts/restricted/nxupdate.sh nx background check’ with pid ’60/60′ finished with exit code 1 after 0,021 seconds.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:12 955.211 61 NXSERVER ERROR! Cannot specify is local node base on: :. (NXNodeExec, /usr/NX/lib/perl/nxserver/NXNodeExec.pm, 2552, NXNodes::isRemoteNode)
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:13 070.440 16 NXSERVER ERROR! NXFrameBuffer failed to start.
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:30:43 716.763 72 NXSERVER ERROR! Cannot specify is local node base on: :. (NXNodeExec, /usr/NX/lib/perl/nxserver/NXNodeExec.pm, 2552, NXNodes::isRemoteNode)
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:31:45 317.717 82 NXSERVER ERROR! Cannot specify is local node base on: :. (NXNodeExec, /usr/NX/lib/perl/nxserver/NXNodeExec.pm, 2552, NXNodes::isRemoteNode)
inspired_main.4.8w6vzd6437f6@ip-172-31-3-82.us-east-2.compute.internal | 2020-02-24 05:36:46 090.669 92 NXSERVER ERROR! Cannot specify is local node base on: :. (NXNodeExec, /usr/NX/lib/perl/nxserver/NXNodeExec.pm, 2552, NXNodes::isRemoteNode)
Hello.
The logs shows that every instance of nxexec process is being blocked.
Most commonly there are problems with apparmor blocking the docker container.
We have a document on this topic:https://www.nomachine.com/DT10O00161
Please check the troubleshooting part of that document.
There also can be a problem with the privileges on the container, sometimes
it is also required to add--privilegedparameter to docker run command.
If the article does not help you, please check if there is anything in the system logs
of the parent operating system 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 for us to debug./Mth
This topic was marked as solved, you can't post.