[FreeNX-kNX] Problems with Fedora 10 & qtnx

Александър Шопов ash at contact.bg
Wed Dec 17 06:27:48 UTC 2008


> something is wrong with the key for the user 'nx'.
I suppose something similar.
Still I am already able to login via nx user. I reported this in a
previous mail.

I did nxsetup --test and got the following:

=================================
Warning: Could not find nxdesktop in /usr/libexec/nx. RDP sessions won't
work.
Warning: Could not find nxviewer in /usr/libexec/nx. VNC sessions won't
work.
Warning: Invalid value
"APPLICATION_LIBRARY_PRELOAD=/usr/lib/nx/libX11.so.6.2:/usr/lib/nx/libXext.so.6.4:/usr/lib/nx/libXcomp.so:/usr/lib/nx/libXcompext.so:/usr/lib/nx/libXrender.so.1.2". /usr/lib/nx/libXcomp.so could not be found. Users will not be able to run a single application in non-rootless mode.
Warning: "/usr/lib/cups/backend/nxipp" is not executable.
         Users will not be able to enable printing.
Warning: Invalid value "COMMAND_START_KDE=startkde"
         Users will not be able to request a KDE session.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
         Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able
to use SAMBA. 
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able
to use SAMBA.
Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2.
         Users will not be able to enable printing.

  Warnings occured during config check.
  To enable these features please correct the configuration file.

<---- done

----> Testing your nxserver connection ...
Warning: Identity file /var/lib/nxserver/home/.ssh/client.id_dsa.key not
accessible: No such file or directory.
Permission denied (publickey,gssapi-with-mic,password).
Fatal error: Could not connect to NX Server.

Please check your ssh setup:

The following are _examples_ of what you might need to check.

	- Make sure "nx" is one of the AllowUsers in sshd_config.
    (or that the line is outcommented/not there)
	- Make sure "nx" is one of the AllowGroups in sshd_config.
    (or that the line is outcommented/not there)
	- Make sure your sshd allows public key authentication.
	- Make sure your sshd is really running on port 22.
	- Make sure your sshd_config AuthorizedKeysFile in sshd_config is set
to authorized_keys2.
    (this should be a filename not a pathname+filename)
  - Make sure you allow ssh on localhost, this could come from some
    restriction of:
      -the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
      -the iptables. add to it:
         $ iptables -A INPUT  -i lo -j ACCEPT
         $ iptables -A OUTPUT -o lo -j ACCEPT
=================================

I found this line interesting:
Warning: Identity file /var/lib/nxserver/home/.ssh/client.id_dsa.key not
accessible: No such file or directory.


I did: 

cd /var/lib/nxserver/home/.ssh/
ln -s /etc/nxserver/client.id_dsa.key .

Now nxsetup --test gives:
=================================
----> Testing your nxserver connection ...
HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.2.0)
NX> 105 quit
Quit
NX> 999 Bye
<--- done
=================================


However qtnx still does not allow connections. I still get: Warning:
Identity file id.key not accessible: No such file or directory.


What I tried next is completely removing the nx related packages and the
setup files:

rpm -e freenx-server freenx-client nx
userdel -f -r nx
rm -fr /etc/nxserver/


After that I reinstalled the packages:

yum install -y freenx-server freenx-client nx

I get the same problems as up to now - unable to connect via qtnx while
being able to connect via ssh as nx.

I tried what you suggested: 
nxsetup --install --setup-nomachine-key --clean --purge

(It is also mentioned here:
http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ/Server#80.25_of_the_authorization_problems_are_ssh_related)

I think this broke things even further.

The home directory of the nx user now does *not* contain a .ssh
subdirectory. In fact - nx's home seems just like the normal home of
other users.

I looked into /etc/nxserver - now there are two new and empty files: 
passwords  passwords.orig. These files got changed: 
users.id_dsa  users.id_dsa.pub. 

I created ~/.ssh and set the permissions, copied the
server.id_dsa.pub.key as authorized_keys2, set the permissions - still I
cannot log as nx via ssh.

I will investigate further but perhaps I will try with the default
install without nxsetup --install --setup-nomachine-key --clean --purge


One additional thing - in /etc/nxserver I have the file
node.conf.sample but not node.conf. 

I will copy it, raise the log level and check what fun ensues.

Kind regards:
al_shopov 


>  You could try to do an uninstall/reinstall with purge (removes the ssh-keys, amongst other) and then see if that helps.
> 
> nxsetup --install --setup-nomachine-key --clean --purge
> 
> should do the trick, if I remember correctly - if not, do 'nxsetup --help'.
> 
> Regards,
> Terje
> 
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>   
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/ 
> 
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________




More information about the FreeNX-kNX mailing list