[FreeNX-kNX] FreeNX & NoMachine Player - Connection Issues

[Nick Couchman]

> 
> Yup.
> 
> Try OpenNX just to see if it works OK then.
> 
> There are a few issues with Suse
> 
> e.g.
> There is a library version issues with OpenSuse 12.2 which trips up
> nxagent with
>         undefined symbol: _XGetRequest
> 
> if you don't include the old libcomposite in the NX-3.4. . . . .

I believe this has been resolved - there were a couple of bugs related to this, and I think I saw that they were all resolved.  The RPMS that I'm currently using are NX 3.5 (upgraded the 3.4 RPM to 3.5), and I'm using openSuSE 12.1 rather than 12.2, so I don't think think I'm hitting this issue.

> 
> [SNIP]
>> >> server_nxnode_echo: NX> 1001 Bye.
>> >> Info: Closing connection to slave with pid 27540.
>> >> 
>> >> - Finally, if I look at the user-specific logs mentioned, I see:
>> >> Error: The remote NX proxy closed the connection.
>> >> Error: Failure negotiating the session in stage '10'.
>> >> Error: Aborting session with 'Unable to open display 'nx/nx,
>> >> options=/home/nxtest/.nx/C-
>> >> se003945-11000-7CE6ABAB93B40AE2CB8303E679FBE39C/options:11000''.
>> >> Session: Aborting session at 'Fri Jan 18 19:57:45 2013'.
>> >> Session: Session aborted at 'Fri Jan 18 19:57:45 2013'.
>> >> xrdb: Connection refused
>> >> xrdb: Can't open display ':11000'
>> >> /usr/bin/startxfce4: X server already running on display :11000
>> > 
>> > already running . . . XAuth issue probably
>> > 
>> > 
>> > Update the FreeNX server
>> > 
>> >                 #DISPLAY_BASE=1000  ( or whatever. if it's # ed out, 
> the 
>> > value is set by nxloadconfig )
>> >                 DISPLAY_BASE=(your value)
>> > 
>> > parameterin /etc/nxserver/node.conf
>> > 
>> > and try a value other than 11000 or 1000
>> 
>> Okay, I will try that, but I think I've tried a few other values 
>> there and nothing seems to make a difference.  I'll try something in
>> the 2000-5000 range or something like that to see if that helps.
> 
> 
> 
> The issue to which I refer is caused by connecting to two
> NX servers simultaneously, if the nxclient X (server) tries to map
> both NX servers to the same nxclient display.
> 
> So
> the DISPLAY_BASE value needs to be unique for each FreeNX server
> to which you may be simultaneously connecting.
> 
> Are you connecting to more than one ???

I definitely have run into this one before and am careful about setting my servers to different DISPLAY_BASE values.  However, this particular issue happens whether or not I'm connected to multiple systems at the same time, and I'm also quite certain that I've chosen a DISPLAY_BASE value on this test system that is different from all of my other servers.  In fact, that's why I chose 11000 the first time around, because I was certain I'd never gone to that high a number on anything else.  So, I don't think DISPLAY_BASE is the issue.

> 
> 
>> 
>> > 
>> > 
>> >> xrdb: Connection refused
>> >> xrdb: Can't open display ':11000'
>> >> xscreensaver: 19:57:45: Can't open display: :11000
>> >> xscreensaver: 19:57:45: running as nxtest/users (120/100)
>> >> 
>> >> xscreensaver: 19:57:45: Errors at startup are usually authorization 
>> > problems.
>> >>               But you're not logging in as root (good!) so something
>> >>               else must be wrong.  Did you read the manual and the 
> FAQ?
>> >> 
>> >>               http://www.jwz.org/xscreensaver/faq.html
>> >>               http://www.jwz.org/xscreensaver/man.html
>> >> 
>> >> 
>> >> ** ERROR **: Cannot open display: 
>> >> /etc/xdg/xfce4/xinitrc: line 159: 28167 Trace/breakpoint trap 
>> > xfce4-session
>> >> 
>> >> 
>> >> So, can anyone shed any light on what's going on here??  First, it 
>> >> seems like the server and client are both pointing the finger at 
>> >> each other saying it's the other's fault.  But then there's this 
>> >> error about Unable to open display??  I should also note that I have
>> >> tried and successfully been able to do the "ssh -X <hostname> 
>> >> nxagent" test - works fine, once it's running I can open up items 
>> >> inside that display, etc.  Also, on NXPlayer, if I do a custom 
>> >> session and specify xterm as the command to run, that seems to work 
>> >> every time.  So, perhaps it's a timing thing - the window manager 
>> > 
>> > It might be timing i.e nxagent hasn't had time to start
>> >          rather than it can't because :11000 is in use
>> 
>> :11000 isn't in use by anything else on the system - I did check that.
> 
> 
> 
> What about on the nxclient ????

No, not used on the client system, either, and the test of changing it to another value seems to corroborate that.  Also, this would fail to explain why it works 10% of the time - if it were a port issue I'd expect to see it fail consistently and never randomly succeed.

Thanks for all the ideas - keep 'em coming.  I'm sure there's something that needs adjusting somewhere, just have to nail down where.

-Nick


--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.