[FreeNX-kNX] Re: problems w/ freenx 0.7.0 and lastes nomachine sources on RHEL6.0
Les Mikesell
lesmikesell at gmail.com
Thu Jul 28 15:42:50 UTC 2011
I'd expect that rpm to work on RHEL6 the same as CentOS6... Even if you
don't want to install the package you could look at the src rpm to see
if any patches were needed.
On 7/28/2011 10:34 AM, hp wrote:
> Thanks for the suggestions. I checked both /etc/sysconfig/selinux and the
> sestatus command; they both indicated SELinux is off on my system.
>
> Andy
>
>
>
> ----- Original Message ----
> From: Les Mikesell<lesmikesell at gmail.com>
> To: freenx-knx at kde.org
> Sent: Wed, July 27, 2011 4:53:57 PM
> Subject: [FreeNX-kNX] Re: problems w/ freenx 0.7.0 and lastes nomachine sources
> on RHEL6.0
>
> This was mentioned on the CentOS list:
>
> http://blog.toracat.org/2010/12/selinux-and-freenx/
>
> Plus a test rpm-packaged version that worked for me on CentOS 6:
> http://centos.toracat.org/misc/nx-freenx/6/
> (I think I did a rebuild of the src rpm but that probably wasn't
> necessary and I'd expect it to work with RHEL too).
>
>
>
> On 7/27/2011 4:18 PM, Terje Andersen wrote:
>> Maybe selinux isn't turned off or configured to not allow the
>> connections. Try to disable it, reboot and test again.
>>
>> On 2011 7 27 22:01, "hp"<aput99 at yahoo.com<mailto:aput99 at yahoo.com>> wrote:
>> > Hi,
>> >
>> > The tigerVNC server that came with RHEL 6.0 didn't seem to preform
>> well on my
>> > PPC64 box; so I decided to look around for a better one. After some
>> searchings
>> > the freeNX server came up as good candidate to try. So I downloaded
>> the code
>> > and compiled it; everything went well. I gave it a run and
>> encountered this
>> > error:
>> >
>> > from the client console: (version 3.5.0-7 running on an Ubuntu
>> 10.04.3 i386
>> > box)
>> >
>> > NXPROXY - Version 3.5.0
>> >
>> > Copyright (C) 2001, 2011 NoMachine.
>> > See http://www.nomachine.com/ for more information.
>> >
>> > Info: Proxy running in client mode with pid '23670'.
>> > Session: Starting session at 'Wed Jul 27 09:47:39 2011'.
>> > Error: The remote NX proxy closed the connection.
>> > Error: Failure negotiating the session in stage '7'.
>> > Error: Wrong version or invalid session authentication cookie.
>> > Session: Terminating session at 'Wed Jul 27 09:47:44 2011'.
>> > Session: Session terminated at 'Wed Jul 27 09:47:44 2011'.
>> >
>> > from /var/log/nxserver.log
>> >
>> > -- NX SERVER START: -c /usr/NX/bin/nxserver - ORIG_COMMAND=
>> > -- NX SERVER START: - ORIG_COMMAND=
>> > Info: Using fds #4 and #3 for communication with nxnode.
>> > HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.5.0)
>> > NX> 105 hello NXCLIENT - Version 3.2.0
>> > NX> 134 Accepted protocol: 3.2.0
>> > NX> 105 SET SHELL_MODE SHELL
>> > NX> 105 SET AUTH_MODE PASSWORD
>> > NX> 105 login
>> > NX> 101 User: user1
>> > NX> 102 Password:
>> > Info: Auth method: passdb
>> > NX> 103 Welcome to: n13 user: user1
>> > NX> 105 listsession --user="user1" --status="suspended,running"
>> > --geometry="1280x1024x24+render" --type="unix-gnome"
>> > NX> 127 Sessions list of user 'user1' for reconnect:
>> >
>> > Display Type Session ID Options Depth
>> > Screen Status Session Name
>> > ------- ---------------- -------------------------------- -------- -----
>> > -------------- ----------- ------------------------------
>> >
>> >
>> > NX> 148 Server capacity: not reached for user: user1
>> > NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
>> > --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>> > --composite="1" --media="0" --session="n13" --type="unix-gnome"
>> > --geometry="1280x976" --client="linux" --keyboard="pc105/us"
>> > --screeninfo="1280x976x24+render"
>> >
>> &link=adsl&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&media=0&session=n13&type=unix-gnome&geometry=1280x976&client=linux&keyboard=pc105/us&screeninfo=1280x976x24+render&clientproto=3.2.0&user=user1&userip=9.53.53.24&uniqueid=F6FE4D16BFDC70C709477C971A036B8F&display=2100&host=127.0.0.1
>> 1
>> >
>> > NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.5.0)
>> > server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using
>> backend:
>> > 3.5.0)
>> > NX> 700 Session id: n13-2100-F6FE4D16BFDC70C709477C971A036B8F
>> > NX> 705 Session display: 2100
>> > NX> 703 Session type: unix-gnome
>> > NX> 701 Proxy cookie: 5bf1cf7a0f95f12002befe2cccda846e
>> > NX> 702 Proxy IP: 127.0.0.1
>> > NX> 706 Agent cookie: 5bf1cf7a0f95f12002befe2cccda846e
>> > NX> 704 Session cache: unix-gnome
>> > NX> 707 SSL tunneling: 1
>> > server_nxnode_echo: NX> 700 Session id:
>> > n13-2100-F6FE4D16BFDC70C709477C971A036B8F
>> > server_nxnode_echo: NX> 705 Session display: 2100
>> > server_nxnode_echo: NX> 703 Session type: unix-gnome
>> > server_nxnode_echo: NX> 701 Proxy cookie:
>> 5bf1cf7a0f95f12002befe2cccda846e
>> > server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
>> > server_nxnode_echo: NX> 706 Agent cookie:
>> 5bf1cf7a0f95f12002befe2cccda846e
>> > server_nxnode_echo: NX> 704 Session cache: unix-gnome
>> > server_nxnode_echo: NX> 707 SSL tunneling: 1
>> > NX> 1009 Session status: starting
>> > server_nxnode_echo: NX> 1009 Session status: starting
>> > NX> 710 Session status: running
>> > NX> 1002 Commit
>> > NX> 1006 Session status: running
>> > server_nxnode_echo: NX> 710 Session status: running
>> > server_nxnode_echo: NX> 1002 Commit
>> > session_status F6FE4D16BFDC70C709477C971A036B8F Running
>> > NX> 105 server_nxnode_echo: NX> 1006 Session status: running
>> > bye
>> > Bye
>> > NX> 999 Bye
>> > NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
>> > SESSION_LOG_CLEAN=0 in node.conf and investigate
>> >
>> "/home/user1/.nx/F-C-n13-2100-F6FE4D16BFDC70C709477C971A036B8F/session".
>> You
>> > might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent
>> to test the
>> > basic functionality. Session log follows:
>> > NX> 1006 Session status: closed
>> > server_nxnode_echo: NX> 596 Session startup failed.
>> >
>> > content of
>> > /home/user1/.nx/F-C-n13-2100-F6FE4D16BFDC70C709477C971A036B8F/session:
>> >
>> > NXAGENT - Version 3.5.0
>> >
>> > Copyright (C) 2001, 2011 NoMachine.
>> > See http://www.nomachine.com/ for more information.
>> >
>> > Info: Agent running with pid '8957'.
>> > Session: Starting session at 'Wed Jul 27 09:48:39 2011'.
>> > Info: Proxy running in server mode with pid '8957'.
>> > 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:
>> >
>> > Did a lot of searchings online and tried numerous suggestions including:
>> > -change default display number from 1000 to a different value (2100)
>> > -create /tmp/.X11-unix and set its permission to 1777 (also noticed
>> it needs to
>> > be owned by root)
>> >
>> > None seemed to work.
>> >
>> > Any ideas/help? Anything I need to do/send along to get this working
>> please let
>> > me know.
>> >
>> > Andy
>> > ________________________________________________________________
>> > 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
>> <mailto:FreeNX-kNX at kde.org>
>> > https://mail.kde.org/mailman/listinfo/freenx-knx
>> > ________________________________________________________________
>>
>>
>> ________________________________________________________________
>> 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
>> ________________________________________________________________
>
> ________________________________________________________________
> 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
> ________________________________________________________________
>
> ________________________________________________________________
> 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