January 13, 2020 at 09:15 #25191
My remote server crashed and NoMachine logged me out. Reset server, but I couldn’t log back in and saw an error that it wasn’t able to create a display. I couldn’t find a solution, so I uninstalled using “sudo dpkg- r nomachine” and ” sudo rm -rf /usr/NX.” As far as I know, there shouldn’t be any left over files. I can login using ssh and other software just fine.
The new installation is failing regardless if I install using root or a sudo user. Server is updated and I’ve download both the deb and tar files to /tmp, as well as /usr. I know the tar works differently. Same issue crops up. The installation isn’t setting the correct rights for a few files, namely the config and ssh files. I see a variety of owner/group permissions view the folder in /usrNX, but I have no idea what the correct settings should be. I attached the log. Listed below is the putty output.
I’d appreciate any help resolving this issue, thanks.
Attachments:January 14, 2020 at 10:13 #25224
Unfortunately we will need some additional information. Those should tell us where the real problem is. Please collect
/usr/NX/var/log/nxupdate.log(if it exist) files. Output from commands
ls -ltr /usr/NX/etc/and
uname -awill be very useful. Send those information to forum[at]nomachine[dot]com, please.January 17, 2020 at 09:41 #25250
I just an email with the requested information. Let me know if you need anything else. Thanks.January 21, 2020 at 16:47 #25336
We have been unable to reproduce this problem. From logs you sent to us we have some conflicting information. One log says there are all files and have proper permissions set. Another log says that installation can’t find those files. Logs appear to be from two different machines, e.g one set from the connecting client, the other from the server. Also we did not received
/usr/NX/var/log/nxupdate.logwhich are essential to reproduce the problem in our lab.
You can also create detailed debug file which should tell us everything about the problem. You can do it by executing command
sudo sed -i '20s/^/set -x\n/' /usr/NX/scripts/setup/nxnode && sudo /usr/NX/scripts/setup/nxserver --update > nxlog.txt 2>&1 && sudo sed -i "/set -x/d" /usr/NX/scripts/setup/nxnodefrom your terminal and then send us
nxlog.txtwhich will be in the place you executed command above.
Please note that the logs must be from the machine where you are having installation problems.February 3, 2020 at 12:57 #25464zaqContributor
The problem is related to ‘install’ command.
Probably the standard command was replaced by a link/wrapper to apt.
Could you run:
It should looks like this:
$ install --help Usage: install [OPTION]... [-T] SOURCE DEST or: install [OPTION]... SOURCE... DIRECTORY or: install [OPTION]... -t DIRECTORY SOURCE... or: install [OPTION]... -d DIRECTORY... This install program copies files (often just compiled) into destination locations you choose........
The default location of original ‘install’ program in Ubuntu 16.04 is:
/usr/bin/installFebruary 4, 2020 at 10:54 #25469
I have no idea what’s going on with this program. I haven’t had any issues installing other programs using root or a sudo user. I vaguely recall trying to install it once using 4.3 Tar instructions, but I deleted everything when that approach produced the same errors.
I followed the DEB instructions per this page.
Running the aforementioned command showed the following.
root@ ~ # /bin/install –help
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
It’s my understand that the default paths should already be taken care of by the standard “dpkg -i <filenamehere>” command. Did you get the files I sent after running the command Hawk mentioned?
What I’m seeing in the log files DOES contradict the command prompt output, which I why I sent both. They should match up, ya know lol. It’s not 2 different machines. Something is wrong with the install script for my server.
I’m to open any ideas. If you need anything please let me know.February 4, 2020 at 16:57 #25476
As you can see your
installcommand is replaced by some script that is trying to use
installis a basic command used on all linux distributions for copying files and should not be replaced. To fix this issue you need to check if install command is not replaced by alias (
alias | grep installand if it’s on the list
unalias install). If it’s not replaced by alias please change name of /bin/install file and try to install NoMachine again.
install --helpcommand should look like this:
install --help Usage: ./install [OPTION]... [-T] SOURCE DEST or: ./install [OPTION]... SOURCE... DIRECTORY or: ./install [OPTION]... -t DIRECTORY SOURCE... or: ./install [OPTION]... -d DIRECTORY... This install program copies files (often just compiled) into destination locations you choose. If you want to download and install a ready-to-use package on a GNU/Linux system, you should instead be using a package manager like yum(1) or apt-get(1). In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to the existing DIRECTORY, while setting permission modes and owner/group. In the 4th form, create all components of the given DIRECTORY(ies). Mandatory arguments to long options are mandatory for short options too. --backup[=CONTROL] make a backup of each existing destination file -b like --backup but does not accept an argument -c (ignored) -C, --compare compare each pair of source and destination files, and in some cases, do not modify the destination at all -d, --directory treat all arguments as directory names; create all components of the specified directories -D create all leading components of DEST except the last, or all components of --target-directory, then copy SOURCE to DEST -g, --group=GROUP set group ownership, instead of process' current group -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x -o, --owner=OWNER set ownership (super-user only) -p, --preserve-timestamps apply access/modification times of SOURCE files to corresponding destination files -s, --strip strip symbol tables --strip-program=PROGRAM program used to strip binaries -S, --suffix=SUFFIX override the usual backup suffix -t, --target-directory=DIRECTORY copy all SOURCE arguments into DIRECTORY -T, --no-target-directory treat DEST as a normal file -v, --verbose print the name of each directory as it is created --preserve-context preserve SELinux security context -Z set SELinux security context of destination file to default type --context[=CTX] like -Z, or if CTX is specified then set the SELinux or SMACK security context to CTX --help display this help and exit --version output version information and exit The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX. The version control method may be selected via the --backup option or through the VERSION_CONTROL environment variable. Here are the values: none, off never make backups (even if --backup is given) numbered, t make numbered backups existing, nil numbered if numbered backups exist, simple otherwise simple, never always make simple backups GNU coreutils online help: <http://www.gnu.org/software/coreutils/> Full documentation at: <http://www.gnu.org/software/coreutils/install> or available locally via: info '(coreutils) install invocation'February 5, 2020 at 09:33 #25486
There is no output when running alias | grep install
Inside bin/install file is “sudo apt install” I held back updating a few programs awhile ago, which shouldn’t have anything to do with NoMachine.
What should I change the filename to ?February 5, 2020 at 16:59 #25500
NoMachine setup is using command
installfor copying and setting files. As
installis replaced on your machine files are installing incorrectly. Please rename /bin/install to for example /bin/inst (by command
mv /bin/install /bin/inst) and try to install NoMachine again.February 6, 2020 at 10:10 #25504
The installation was a success after making the directory change.
However, trying to access the remote server is not working. Error message I see is, “authentication failed, please try again.” I know the password is correct.
Any ideas?February 7, 2020 at 17:12 #25530
I was able to reproduce the issue and unfortunately previous problem caused installation damage and it is hard to fix without reinstalling NoMachine.
To completely reinstall NoMachine you need to use command
sudo dpkg --purge nomachinethen remove leftover catalog by command
rm -rf /usr/NX/and install it again. This should fix the problem with authentication.February 8, 2020 at 05:06 #25534
Installation went very well, but now I’m seeing an error message, ”
Error: Cannot create a new display, please contact your system administrator.” I’m using XFCE4 and haven’t changed it. Something I need to fix on the config file?
Error: Cannot create a new display, please contact your system administrator’.
6680 236 20:11:37 628.742 ClientSession: Stopping session at 0x02d4d7f0.
6680 236 20:11:37 640.710 Connection: Stopping connection at 0x03bf1c50.
Info: Slave server running with pid 948.
6680 236 20:11:37 640.710 ClientDaemonConnector: Stopping the current connection.
Info: Listening to slave connections on port 35040.
6680 236 20:11:37 641.710 Connection: Stopped connection at 0x03bf1c50.
6680 236 20:11:37 652.731 ClientSession: Stopped session at 0x02d4d7f0.
6680 236 20:11:37 652.731 Connection: Stop reading because of parser request.February 10, 2020 at 12:25 #25552
We will need your node.cfg file so we can verify if file is complete. You can find it at
/usr/NX/etc/node.cfg, then send those information to forum[at]nomachine[dot]com, please.
Also please verify if your default desktop command is set properly. First check what is the path to startxfce4 by using command
which startxfce4and then navigate to /usr/NX/etc/node.cfg and check if DefaultDesktopCommand key is set to path you got from
whichcommand. It should look similar to this:
You must be logged in to reply to this topic.