[FreeNX-kNX] Server setup; no logging & command not found

Thu Feb 20 10:50:40 UTC 2014

freenx-knx-bounces at kde.org wrote on 19/02/2014 21:17:01:

>> 
>> Well . . . 
>> 
>> start by checking that you DO have the private key from the FreeNX 
server 
>> key pair set up in the nxclient, 
>> the (default) nomachine one if you didn't generate your own 
>> or 
>> copy over the new key from the server if you did choose to generate 
your 
>> own key pair, when you ran nxsetup 

> I made sure to follow the defaults when running the server setup 
> script, so here's what I get when I try to log in with Nxserver's 
default key:

> Pseudo-terminal will not be allocated because stdin is not a terminal.
> 
> Permission denied (publickey).

OK a real error message - always a good place to start . . . .

. . . . even if
         they're not always issued at the error point,
but by the calling process . . . .

I don't know why people are asking you which desktop you use
etc . .  when the log show you aren't even connecting.

So,
 you ether have the wrong key for the key-pair

** OR **

your user (glen) can't log in to

        the sshd pointed to in node.conf (port 22 default)

using

         "PasswordAuthentication yes"

because

eg.
you have set it to keypair (rsa etc) only in 

        /etc/ssh/sshd_config

(OR both the above maybe)

> 
> And when using my SSH private key (it seems like this is what I had 
> the client setup to do to begin with), the NoMachine client will 
> prompt me for a username and password (I'll specify my ubuntu user 
> account and its password). The client will proceed to think on it 
> for awhile, then respond with the error "The NoMachine service is 
> not available". Looking at my client connection log this time:

OK sounds like it was "both" above,
but
now you have a key which gets you into the server as user nx

> Pseudo-terminal will not be allocated because stdin is not a terminal.
> 
> Warning: No xauth data; using fake authentication data for X11 
forwarding.
> 
> Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.2.0-58-generic-pae i686)
> 
>  * Documentation:  https://help.ubuntu.com/
> 
> 16 packages can be updated.
> 16 updates are security updates.
> 
> Linux
> NX server command not found
> 
> So it seems like my SSH private key is doing the trick, although I 
> see some potentially concerning errors there besides the server 
> command not found.
> 
> I also just found a more detailed log on the client side:

[SNIP]

> 5044 5048 16:01:28 899.273 ClientSession: Change state to 'Failed'.

OK . . . something went wrong . . . have a nice day . . .

> 
> Hopefully that offers some more information...

Not much . . . have an ice day tho' (mint choc chip 4me)

> set logging to debug,  ie. 6 

Good

>> 
>> tho . . 
>> 
>> . . . probably you are not connecting at all. 
>> 

> Bumped logging up to 6 in node.conf, sudo nxserver --stop, sudo 
> nxserver --start, attempted another log in with the client, annnnd...

The service isn't a service i.e. there is **NO** daemon to start/stop

The service script enables/disables the nx (tunnel) account
and
clears up a bit of the mess

> glen at glenux:/var/log$ sudo cat nxserver.log
> glen at glenux:/var/log$
> 
> Still empty. FWIW, the client logs still appear to be relatively the
> same, in case that would have made a difference.

OK, so you still aren't logging in then . . . . by the look of it

>> To test your server you can try 
>> 
>> logging in to the server as your normal user, then running 
>> 
>>         sudo su -l nx 
>> 
>> at a command prompt 
>> to see 
>> if user nx logs in and finds its shell 

> Now *that* is pretty darned cool. I just tried the command:

Proper systematic testing is usually quickly/useful . . . ;)

> glen at glenux:/var/log$ sudo su -l nx
> HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> NX> 105 help
> help
> NX> 105 ls
> ls
> NX> 105 quit
> quit
> Quit
> NX> 999 Bye
> 

So

now you know
         your nx account is fine
and
        nxserver is installed . . .
which
        should log you in as
                 user "glen"
provided

your user "glen" account can log in
         (with PasswordAuthentication yes
         set in /etc/ssh/sshd_config)

> So clearly I have no idea what I'm doing once I'm in, but hey, I 
> logged in on the server side! And naturally, the log:

> glen at glenux:/var/log$ sudo cat nxserver.log 
> -- NX SERVER START:  - ORIG_COMMAND=
> -- NX SERVER START:  - ORIG_COMMAND=
> Info: Using fds #4 and #3 for communication with nxnode.
> HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> NX> 105 help
> NX> 105 ls
> NX> 105 quit
> Quit
> NX> 999 Bye
> glen at glenux:/var/log$

Right

so logging works too
BUT
you've never got that far have you ??
cos
you've never quite logged in . . 

Here's another annoying test to help you along

1/ Add the nx private key (as a new key file) to your .ssh/ directory
        in the same format as the other private keys.
        Sounds like you generated your own pair 2me

2/ run

        ssh  -l nx     -i ~/.ssh/new-nx-private-key.file    your-server-IP

this should key-pair log in as user nx over the network
and
give you the same prompt ( user nx's shell) as the
previous annoying test

Keep going with the various key-pair options
until
         you have the correct key pair identified
**BUT**
look at
         /etc/ssh/sshd.conf
for
         PasswordAuthentication yes
**FIRST**

> 
> So it seems like things may be functioning over there. Now just for 
> getting the client to talk!

Next thing to look at is your user account via ssh
        (PasswordAuthentication yes
          in
         /etc/ssh/sshd_config)

> Development ceased in 2008 tho' various people have fixed various 
> things since . . . 
> 
> Ah, shoot. I was reading up on some of the history; does this 
> coincide with when NoMachine cut off their mailing list?

Nonachine have moved to version 4 which coincides with
the ending of their support for the "opensource" V3 nxagent 
and libraries etc

> 
> Thank you!

UR welcome

let us know how you get on

I'm staying with FreeNX for the moment; I see no advantage in changing

Marcello seems to recompile the libraries and re-package for new ubuntu's
and
Akemi for RHEL/centos
also
some community volunteers do the same for OpenSuse

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20140220/8cf57a9f/attachment.html>