<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite"><br>
<tt><font size="2">Well . . .</font></tt>
<br>
<br>
<tt><font size="2">start by checking that you DO have the private
key
from the FreeNX server </font></tt>
<br>
<tt><font size="2">key pair set up in the nxclient,</font></tt>
<br>
<tt><font size="2">either</font></tt>
<br>
<tt><font size="2">the (default) nomachine one if you didn't
generate
your own</font></tt>
<br>
<tt><font size="2">or</font></tt>
<br>
<tt><font size="2">copy over the new key from the server if you
did choose
to generate your</font></tt>
<br>
<tt><font size="2">own key pair, when you ran nxsetup</font></tt>
</blockquote>
<br>
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:<br>
<br>
<blockquote type="cite">Pseudo-terminal will not be allocated
because stdin is not a terminal.<br>
<br>
Permission denied (publickey).</blockquote>
<br>
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:<br>
<br>
<blockquote type="cite">Pseudo-terminal will not be allocated
because stdin is not a terminal.<br>
<br>
Warning: No xauth data; using fake authentication data for X11
forwarding.<br>
<br>
Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.2.0-58-generic-pae
i686)<br>
<br>
* Documentation: <a class="moz-txt-link-freetext" href="https://help.ubuntu.com/">https://help.ubuntu.com/</a><br>
<br>
16 packages can be updated.<br>
16 updates are security updates.<br>
<br>
Linux<br>
NX server command not found</blockquote>
<br>
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.<br>
<br>
I also just found a more detailed log on the client side:<br>
<br>
<blockquote type="cite">Info: Slave server running with pid 4976.<br>
Info: Listening to slave connections on port 34391.<br>
5044 5048 16:01:22 581.262 Connection: Finished connection at
0x4ab0bb0.<br>
5044 5048 16:01:22 581.262 Connection: Initializing connection at
0x4ab0bb0.<br>
5044 5048 16:01:22 581.262 Connection: Initialized connection at
0x4ab0bb0.<br>
5044 5048 16:01:22 581.262 Connection: Starting connection at
0x4ab0bb0.<br>
5044 5048 16:01:22 596.862 ClientProcess: Starting command
'nxssh.exe "-F" "(redacted)\sshoptions" <a class="moz-txt-link-rfc2396E" href="mailto:glen@192.168.1.133">"glen@192.168.1.133"</a>'<br>
5044 5048 16:01:22 596.862 Process: ERROR! Can't set priority to
0.<br>
5044 5048 16:01:22 596.862 Process: ERROR! Error is 22 'Invalid
argument'.<br>
5044 5048 16:01:22 596.862 ClientSession: Going to add child with
pid '2128' and process at 0.<br>
5044 5048 16:01:22 596.862 ClientSession: Now there are 1 running
children.<br>
5044 5048 16:01:22 596.862 Connection: Started connection at
0x4ab0bb0.<br>
5044 5048 16:01:22 612.462 ClientSession: Change state to
'Started'.<br>
5044 5048 16:01:22 612.462 ClientSession: Started session at
0x741740.<br>
5044 5048 16:01:28 852.473 Connection: Connection at 0x4ab0bb0
failed.<br>
5044 5048 16:01:28 852.473 ClientSession: Runnable at 0x4ab0bb0
caused the session at 0x741740 to fail.<br>
5044 5048 16:01:28 852.473 ClientSession: Failing reason is 'The
NoMachine service is not available'.<br>
5044 5048 16:01:28 868.073 ClientSession: Stopping session at
0x741740.<br>
5044 5048 16:01:28 868.073 ClientSession: Change state to
'Stopping'.<br>
5044 4976 16:01:28 883.673 SlaveServerApplication/Application:
WARNING! Not waiting with FD#1636 ready.<br>
5044 5048 16:01:28 883.673 Connection: Stopping connection at
0x4ab0bb0.<br>
5044 5048 16:01:28 883.673 Connection: Stopped connection at
0x4ab0bb0.<br>
5044 5048 16:01:28 883.673 ClientSession: Going to kill all
children.<br>
5044 5048 16:01:28 883.673 ClientSession: Joining the child
process '2128'.<br>
5044 5048 16:01:28 899.273 ClientSession: Change state to
'Stopped'.<br>
5044 5048 16:01:28 899.273 ClientSession: Stopped session at
0x741740.<br>
5044 5048 16:01:28 899.273 ClientSession: Change state to
'Failed'.</blockquote>
<br>
Hopefully that offers some more information...<br>
<br>
<blockquote type="cite"><tt><font size="2">set logging to debug,
ie. 6</font></tt>
<br>
<br>
<tt><font size="2">tho . . </font></tt>
<br>
<br>
<tt><font size="2">. . . probably you are not connecting at all.</font></tt>
</blockquote>
<br>
Bumped logging up to 6 in node.conf, sudo nxserver --stop, sudo
nxserver --start, attempted another log in with the client,
annnnd...<br>
<br>
<blockquote type="cite">glen@glenux:/var/log$ sudo cat nxserver.log<br>
glen@glenux:/var/log$<br>
</blockquote>
<br>
Still empty. FWIW, the client logs still appear to be relatively the
same, in case that would have made a difference.<br>
<br>
<blockquote type="cite"><tt><font size="2">To test your server you
can try </font></tt>
<br>
<br>
<tt><font size="2">logging in to the server as your normal user,
then
running</font></tt>
<br>
<br>
<tt><font size="2"> sudo su -l nx</font></tt>
<br>
<br>
<tt><font size="2">at a command prompt</font></tt>
<br>
<tt><font size="2">to see</font></tt>
<br>
<tt><font size="2">if user nx logs in and finds its shell</font></tt>
</blockquote>
<br>
Now *that* is pretty darned cool. I just tried the command:<br>
<br>
<blockquote type="cite">glen@glenux:/var/log$ sudo su -l nx<br>
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend:
3.5.0)<br>
NX> 105 help<br>
help<br>
NX> 105 ls<br>
ls<br>
NX> 105 quit<br>
quit<br>
Quit<br>
NX> 999 Bye<br>
</blockquote>
<br>
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:<br>
<br>
<blockquote type="cite">glen@glenux:/var/log$ sudo cat nxserver.log
</blockquote>
<blockquote type="cite">-- NX SERVER START: - ORIG_COMMAND=<br>
-- NX SERVER START: - ORIG_COMMAND=<br>
Info: Using fds #4 and #3 for communication with nxnode.<br>
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend:
3.5.0)<br>
NX> 105 help<br>
NX> 105 ls<br>
NX> 105 quit<br>
Quit<br>
NX> 999 Bye<br>
glen@glenux:/var/log$<br>
</blockquote>
<br>
So it seems like things may be functioning over there. Now just for
getting the client to talk!<br>
<br>
<blockquote type="cite"><tt><font size="2">Development ceased in
2008 tho' various people have
fixed various</font></tt>
<br>
<tt><font size="2">things since . . . </font></tt>
</blockquote>
<br>
Ah, shoot. I was reading up on some of the history; does this
coincide with when NoMachine cut off their mailing list?<br>
<br>
Thank you!<br>
<br>
<div class="moz-cite-prefix">On 2/19/2014 6:52 AM,
<a class="moz-txt-link-abbreviated" href="mailto:chris@ccburton.com">chris@ccburton.com</a> wrote:<br>
</div>
<blockquote
cite="mid:OFB93A5A7F.CC85A2C7-ON80257C84.003FEAAD-80257C84.004138F6@ccburton.com"
type="cite">
<br>
<tt><font size="2"><a class="moz-txt-link-abbreviated" href="mailto:freenx-knx-bounces@kde.org">freenx-knx-bounces@kde.org</a> wrote on 18/02/2014
16:45:46:<br>
<br>
> Hello everyone,<br>
> <br>
> I would like to ask a question that is more
Ubuntu-specific: I'm hoping
<br>
> that it won't be too far off topic from the freenx server
in general.<br>
> <br>
> I've finished setting up the server and I would like to
start <br>
> connecting. So I start up the NoMachine NX client on my
windows computer
<br>
> to connect. I've set it up for the SSH protocol, and I
try to auth
using <br>
> my ubuntu username and SSH private key (although it might
be the private
<br>
> key that freenx generated; I can't quite remember which).</font></tt>
<br>
<br>
<tt><font size="2">Well . . .</font></tt>
<br>
<br>
<tt><font size="2">start by checking that you DO have the private
key
from the FreeNX server </font></tt>
<br>
<tt><font size="2">key pair set up in the nxclient,</font></tt>
<br>
<tt><font size="2">either</font></tt>
<br>
<tt><font size="2">the (default) nomachine one if you didn't
generate
your own</font></tt>
<br>
<tt><font size="2">or</font></tt>
<br>
<tt><font size="2">copy over the new key from the server if you
did choose
to generate your</font></tt>
<br>
<tt><font size="2">own key pair, when you ran nxsetup</font></tt>
<br>
<tt><font size="2"><br>
> <br>
> The connection is dropped however, and when I look at the
clientside
<br>
> logs from NoMachine, I see my SSH log in welcome message,
followed
by a <br>
> line saying "the command was not found". Trying to find
more information <br>
</font></tt>
<br>
<br>
<tt><font size="2">What exactly does it say ( on the client, in
the log
). . . .</font></tt>
<br>
<br>
<br>
<tt><font size="2">> on my server is fruitless, however, as the
nxserver.log
file is <br>
> completely empty, despite me setting the logging level to
5 and <br>
</font></tt>
<br>
<tt><font size="2">set logging to debug, ie. 6</font></tt>
<br>
<br>
<tt><font size="2">tho . . </font></tt>
<br>
<br>
<tt><font size="2">. . . probably you are not connecting at all.</font></tt>
<br>
<br>
<br>
<tt><font size="2">To test your server you can try </font></tt>
<br>
<br>
<tt><font size="2">logging in to the server as your normal user,
then
running</font></tt>
<br>
<br>
<tt><font size="2"> sudo su -l nx</font></tt>
<br>
<br>
<tt><font size="2">at a command prompt</font></tt>
<br>
<tt><font size="2">to see</font></tt>
<br>
<tt><font size="2">if user nx logs in and finds its shell</font></tt>
<br>
<br>
<br>
<tt><font size="2">> subsequently rebooting the server. The log
file
also appears to be owned <br>
> (and is writable by) an nx user.<br>
</font></tt>
<br>
<tt><font size="2">yup, the original "ssh tunnel" connection
is made by</font></tt>
<br>
<tt><font size="2"> user nx</font></tt>
<br>
<tt><font size="2">with a</font></tt>
<br>
<tt><font size="2"> ssh key
pair</font></tt>
<br>
<br>
<tt><font size="2">then</font></tt>
<br>
<tt><font size="2">your username and password are used to log in
your
user session</font></tt>
<br>
<tt><font size="2">via the tunnel</font></tt>
<br>
<br>
<tt><font size="2">> <br>
> If anyone can help me get up and running, that would be
wonderful.<br>
> <br>
> P.S. Is the freenx server still actively developed? I see
there hasn't
<br>
> been a stable release in nearly four years!<br>
</font></tt>
<br>
<tt><font size="2">Development ceased in 2008 tho' various people
have
fixed various</font></tt>
<br>
<tt><font size="2">things since . . . </font></tt>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:
<a class="moz-txt-link-freetext" href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a>
Don't forget to check the NX Knowledge Base:
<a class="moz-txt-link-freetext" href="http://www.nomachine.com/kb/">http://www.nomachine.com/kb/</a>
________________________________________________________________
FreeNX-kNX mailing list --- <a class="moz-txt-link-abbreviated" href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/freenx-knx">https://mail.kde.org/mailman/listinfo/freenx-knx</a>
________________________________________________________________</pre>
</blockquote>
<br>
</body>
</html>