[FreeNX-kNX] Re: problems w/ freenx 0.7.0 and lastes nomachine sources on RHEL6.0

[hp]

yes I tried  the "ssh -X myserver; /usr/NX/bin/nxnode --agent" suggestion before 
but didn't get any further with the info given:
(trying your suggestion)


[user1:~/freenx] ssh -X user1 at some.host "/usr/libexec/nx/nxnode --agent"
user1 at some.host's password: 
NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
NX> 716 Starting NX Agent ...

NXAGENT - Version 3.3.0

Copyright (C) 2001, 2007 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '39121'.
Session: Starting session at 'Thu Jul 28 10:46:29 2011'.
Info: Using alpha channel in render extension.
Info: Not using local device configuration changes.
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
Session: Session started at 'Thu Jul 28 10:46:29 2011'.

It just hang at the state... nothing came back for a while... usually had to 
Ctrl-C to get out.
BTW, ssh -X in and execute "xclock" does work.

Did some looking up on that SecurityPolicy error; didn't seem like a serious 
issue from found.
I would soft link it makes it happy but SecurityPolicy doesn't exist at all on 
my system.

Haven't tried the suggestions you have for experimenting locally on the system 
yet.  Will try next and post what I find.

Andy



________________________________
From: "chris at ccburton.com" <chris at ccburton.com>
To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
Sent: Thu, July 28, 2011 7:14:32 AM
Subject: [FreeNX-kNX] Re: problems w/ freenx 0.7.0 and lastes nomachine sources 
on RHEL6.0


hp <aput99 at yahoo.com> wrote on 27/07/2011 16:05:23:

> Hi, 
[SNIP] 

Hmmmm, the nxscripts run . . . . 

> NX> 1004 Error: NX Agent exited with exit status 1. 
[SNIP]
> You might also want to try: 
> ssh -X myserver; /usr/NX/bin/nxnode --agent 
> to test the basic functionality. Session log follows: 

Did you try the above suggestion ?? 

How about 
        ssh -X myserver "/usr/NX/bin/nxnode --agent" 
which might work a bit better. 

If nxnode is :- /usr/bin/nxnode instead then you will have 
to change the path. 

If you use a slow link you may have to wait 30 seconds 
or more for the agent window to open . . . .  

Any error messages about anything ????? 

[SNIP] 
> Info: Waiting for connection from '127.0.0.1' on port '6100'.
> Warning: Refusing connection from '0.0.0.0'.
> Error: Connection with remote host '127.0.0.1' 
> could not be established.
> Error: Aborting session with 'Unable to open display 
> 'nx/nx,options=/home/user1/.nx/C-n13-2100-
> F6FE4D16BFDC70C709477C971A036B8F/options:2100''.
> 
> Session: Aborting session at 'Wed Jul 27 09:49:29 2011'.
> Session: Session aborted at 'Wed Jul 27 09:49:29 2011'.
> XIO:  fatal IO error 104 (Connection reset by peer) on X server ":2100.0"
>       after 0 requests (0 known processed) with 0 events remaining.
> 
> ** (gnome-session:8985): WARNING **: Cannot open display:
> 
 
You can also test it manually on port 2100. 

Log-in locally to X session, start a terminal and run:- 

        nxagent :2100 

An agent window should appear, or you should get a useful 
error message. 

Open another terminal and run:- 

        export DISPLAY=:2100 
        xterm 

Either the xterm should appear in the agent window, or you 
should get an error message . . . . 
CB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20110728/faee305c/attachment.html>