Forum / NoMachine for Linux / Tumbleweed – NX> 704 ERROR: Unsupported operating system ‘linux’
- This topic has 3 replies, 3 voices, and was last updated 6 years, 9 months ago by hawk.
-
AuthorPosts
-
November 28, 2017 at 15:59 #16737jaylteeParticipant
Running Tumbleweed with all updates as of November 2017. Tried to install NoMachine v5.1.62 (which I have been successfully running with Leap42.2) and it fails as below. I get the same with 6.0.62 so it’s not version specific.
Preparing… ################################# [100%]
Updating / installing…
1:nomachine-5.1.62-1 ################################# [100%]Usage: nxserver ACTION
Actions:
–install {SYSTEM} Run the NoMachine server install procedure for the
specified system or distribuition–update {SYSTEM} Run the NoMachine server update procedure for the
specified system or distribution–uninstall Run the NoMachine server uninstall procedure.
–pre-uninstall Disable access to new NX sessions, terminate
sessions and reset the session DBs.–keygen Generate a new pair of SSH keys for the NoMachine
login. After running this procedure, clients will
use the key: /usr/NX/share/keys/default.id_dsa.key
to connect to this NX server.–keyrestore Restore the SSH key provided with the server
package. Current key will be moved to
default.id_dsa.key.backup file.–help Show this message
The specified SYSTEM must be one of the following operating systems.
If not the NoMachine setup will try to autodetect the system or will choose
the layout that better resembles one of the known OS.redhat Red Hat Enterprise 4/5/6 etc.
suse SLED 10/11/12, SLES 10/11/12, Open SUSE 10.x/11.x/12.x/13.x
slackware
mandriva Mandriva 2009/2010/2011 etc.
debian Debian GNU Linux 4.0 Etch/5.0 Lenny/6.0 Squeeze etc.
Ubuntu 8.04 Hardy Heron/8.10 Intrepid Ibex/9.04 Jaunty Jackalope
9.10 Karmic Koala/10.4 Lucid Lynx/10.10 Maverick Meerkat
11.04 Natty Narwhal/11.10 Oneiric Ocelot etc.
fedora Fedora 10/11/12/13/14/15/16 etc.
NX> 704 ERROR: Unsupported operating system ‘linux’##########
To resolve this I had a look in the nxserver script and see it does the following to work out the OS/Distribution:
getLinuxNameFromFiles ()
{
#Function returns:
# 0 : OS name is found
# 1 : OS name not foundwantedOS=”$1″
searchedFile=””
ret_getLinuxNameFromFiles=”1″if [ -f /etc/lsb-release ];
then
searchedFile=”/etc/lsb-release”
elif [ -f /etc/os-release ];
then
searchedFile=”/etc/os-release”
elif [ -f /usr/lib/os-release ];
then
searchedFile=”/usr/lib/os-release”
else
return 0
fios_out=${GREPCOMMAND} ‘\(\(NAME\)\|\(DISTRIB_ID\)\)=.*'”${wantedOS}”‘.*$’ “${searchedFile}” 2>/dev/null || test 1
if [ “x${os_out}” != “x” ];
then
ret_getLinuxNameFromFiles=”0″
fi
}
###########
The difference with Tumbleweed and Leap42 is that TW has /etc/lsb-release and Leap does not. As this file is found first it is used in the next stage of the script but it does not have the distribution in it – it looks like this:
LSB_VERSION=”core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64″This leaves the script without knowledge of the distribution and so fails. I simply removed this file and the installation was fine as all Suse distributions have the “standard” /etc/os-release file.
Maybe someone can fix the /usr/NX/scripts/setup/nxserver script so that /etc/lsb-release is not there (or at least move to the end)? If not, I hope this at least helps someone with the same issue as it could hit other distributions.
Cheers,
JTDecember 1, 2017 at 20:11 #16769hawkParticipantThank you for reporting this problem and the detailed analysis. We are still investigating this issue because we weren’t able to reproduce it. We will open a Trouble Report and inform you about it as soon as possible.
January 15, 2018 at 09:48 #17134EragontuxParticipantI have exactly the same problem
January 16, 2018 at 12:14 #17153hawkParticipantThank you for reporting this problem. We have opened a Trouble Report to track this issue: https://www.nomachine.com/TR11O08293. To let the installation complete without errors please temporarily change name or backup and remove “/etc/lsb-release” file (it can be restored after installation/update of NoMachine) as the user “jayltee” instructed.
To be notified when the fix is released, you may register to the ‘Notify me when the TR is closed’ option.
-
AuthorPosts
This topic was marked as solved, you can't post.