[FreeNX-kNX] Freenx Disconnecting Inmediatelly

Wed Feb 25 23:02:57 UTC 2009

Yes, I did have gnome-session installed.

Here is what I did:
Installed ubuntu 8.10 server 32 bits.
Added the repositories for freenx.
Installed freenx with apt-get install freenx.
Just in case installed gnome-core with apt-get install gnome-core.

I did check that I had gnome-session available, but as I did not
install an xserver because it wasn't necessary, on the local display
gnome-session exits with cant open display.

The weird thing is that I tried this in a VMWare Server 2.0 machine
and it did work. My production machine is actually a virtual server
inside VMWare ESXi.
I don't thing the problem is VMWare since installing the whole desktop
with apt-get install gnome, solved it.

On Wed, Feb 25, 2009 at 6:52 PM, Marcelo Boveto Shima
<marceloshima at gmail.com> wrote:
> Actually it depends on gnome-session | kdebase-workspace-bin | ksmserver |
> xfce4-session | freenx-rdp | freenx-vnc.
> So for gnome you need gnome-session.
> Did you had gnome-session installed?
>
> Regards.
>
> On Wed, Feb 25, 2009 at 7:39 PM, Alfred Rapozo <alfred.rapozo at gmail.com>
> wrote:
>>
>> Solved installing the package gnome on the server, shamefully, that
>> package comes with a lot of programs i don't want and have to remove
>> afterward.
>>
>> On Wed, Feb 25, 2009 at 8:50 AM, Alfred Rapozo <alfred.rapozo at gmail.com>
>> wrote:
>> > I did some testing on both my virtual lab and my real machine.
>> > In both machines i couldn't start a local gnome-session since I don't
>> > have an xserver installed. But on the client when I connect to my lab
>> > machine I can remotely create a session, in the real one i cant.
>> > How can I track what programs is freenx running on my lab machine and
>> > my real one to see what's causing this problem?
>> >
>> >
>> > On Tue, Feb 24, 2009 at 6:39 PM, Freerk Kalsbeek
>> > <f.kalsbeek at mindswitch.nl> wrote:
>> >> Usuably this kind of terminates happen if you try to start a session
>> >> that
>> >> does not exist on the server, eg starting a gnome-session on a server
>> >> where
>> >> gnome-desktop is not installed.
>> >>
>> >> In your log it states that it cannot find /usr/lib/python2.5/os.py.
>> >> On ubuntu that's part of python-minimal.
>> >>
>> >> 1st. Make sure you can start a gnome session on the server. (Does
>> >> /usr/bin/gnome-session exist?)
>> >> 2nd. Try installing python-minimal and see what happens
>> >>
>> >> Regards,
>> >>
>> >> Freerk
>> >>
>> >> On Tue, Feb 24, 2009 at 7:54 PM, Alfred Rapozo
>> >> <alfred.rapozo at gmail.com>
>> >> wrote:
>> >>>
>> >>> Just adding the output of the session file.
>> >>>
>> >>> Info: Agent running with pid '4851'.
>> >>> Session: Starting session at 'Mon Feb 23 09:50:46 2009'.
>> >>> Info: Proxy running in server mode with pid '4851'.
>> >>> Info: Waiting for connection from '127.0.0.1' on port '5001'.
>> >>> Info: Accepted connection from '127.0.0.1'.
>> >>> Info: Connection with remote proxy completed.
>> >>> Info: Using WAN link parameters 768/24/1/0.
>> >>> Info: Using agent parameters 5000/5/50/0/0.
>> >>> Info: Using cache parameters 4/4096KB/65536KB/65536KB.
>> >>> Info: Using pack method 'adaptive-9' with session 'gnome'.
>> >>> Info: Using product 'LFE/None/LFEN/None'.
>> >>> Info: Using ZLIB data compression 1/1/32.
>> >>> Info: Using ZLIB stream compression 1/1.
>> >>> Info: No suitable cache file found.
>> >>> Info: Listening to X11 connections on display ':1001'.
>> >>> Info: Established X client connection.
>> >>> Info: Using shared memory parameters 1/1/0/0K.
>> >>> Info: Using alpha channel in render extension.
>> >>> Info: Using local device configuration changes.
>> >>> Failed to create the keyboard file
>> >>> Session: Session started at 'Mon Feb 23 09:50:48 2009'.
>> >>> Session: Terminating session at 'Mon Feb 23 09:50:48 2009'.
>> >>> Info: Watchdog running with pid '4886'.
>> >>> Info: Waiting the watchdog process to complete.
>> >>> 2.5/os.py", line 354, in execvp
>> >>>    _execvpe(file, args)
>> >>>  File "/usr/lib/python2.5/os.py", line 378, in _execvpe
>> >>>    func(file, *argrest)
>> >>> OSError: [Errno 2] No such file or directory
>> >>>
>> >>> On Tue, Feb 24, 2009 at 2:14 PM, Alfred Rapozo
>> >>> <alfred.rapozo at gmail.com>
>> >>> wrote:
>> >>> > Im using ubuntu 8.10 and followed the simple howto at the page:
>> >>> >
>> >>> > https://help.ubuntu.com/community/FreeNX
>> >>> >
>> >>> > Everything works good on my lab environment, but when I did it on
>> >>> > the
>> >>> > server that's supposed to be for production the weirdest thing
>> >>> > happens. I'm using nomachine client from windows and If I connect to
>> >>> > the gnome session, it authenticates me and opens the window but it
>> >>> > closes it automatically. But if i set it to run a specific program,
>> >>> > like firefox, it works perfectly.
>> >>> >
>> >>> > This is the relevant portion of the nxserver.log file:
>> >>> >
>> >>> > NX> 1009 Session status: starting
>> >>> > nxnode_reader: NX> 710 Session status: running
>> >>> > nxnode_reader: NX> 1002 Commit
>> >>> > nxnode_reader: NX> 1006 Session status: running
>> >>> > server_nxnode_echo: NX> 710 Session status: running
>> >>> > server_nxnode_echo: NX> 1002 Commit
>> >>> > session_status D05BF952C728B84036665F60847899C8 Running
>> >>> > NX> 105 NX> 710 Session status: running
>> >>> > NX> 1002 Commit
>> >>> > NX> 1006 Session status: running
>> >>> > server_nxnode_echo: NX> 1006 Session status: running
>> >>> > bye
>> >>> > Bye
>> >>> > NX> 999 Bye
>> >>> > nxnode_reader: NX> 1009 Session status: terminating
>> >>> > NX> 1009 Session status: terminating
>> >>> > session_status D05BF952C728B84036665F60847899C8 Terminating
>> >>> > server_nxnode_echo: NX> 1009 Session status: terminating
>> >>> > Info: Closing connection to slave with pid 988.
>> >>> > nxnode_reader: 1001 Bye.
>> >>> > 1001 Bye.
>> >>> > nxnode_reader: NX> 1006 Session status: closed
>> >>> > NX> 1006 Session status: closed
>> >>> > session_close D05BF952C728B84036665F60847899C8
>> >>> > server_nxnode_echo: NX> 1006 Session status: closed
>> >>> > nxnode_reader: NX> 1001 Bye.
>> >>> > NX> 1001 Bye.
>> >>> > server_nxnode_echo: NX> 1001 Bye.
>> >>> > Info: Closing connection to slave with pid 988.
>> >>> >
>> >>> > This is the output of the nomachine client when it closes:
>> >>> >
>> >>> > Info: Display running with pid '5164' and handler '0x1206b0'.
>> >>> >
>> >>> > NXPROXY - Version 3.3.0
>> >>> >
>> >>> > Copyright (C) 2001, 2007 NoMachine.
>> >>> > See http://www.nomachine.com/ for more information.
>> >>> >
>> >>> > Info: Proxy running in client mode with pid '5040'.
>> >>> > Session: Starting session at 'Tue Feb 24 14:19:30 2009'.
>> >>> > Info: Connection with remote proxy completed.
>> >>> > Info: Using WAN link parameters 768/24/1/0.
>> >>> > Info: Using cache parameters 4/4096KB/65536KB/65536KB.
>> >>> > Info: Using pack method 'adaptive-9' with session 'gnome'.
>> >>> > Info: Using ZLIB data compression 1/1/32.
>> >>> > Info: Using ZLIB stream compression 1/1.
>> >>> > Info: No suitable cache file found.
>> >>> > Info: Forwarding X11 connections to display ':0'.
>> >>> > Info: Listening to font server connections on port '11001'.
>> >>> > Session: Session started at 'Tue Feb 24 14:19:30 2009'.
>> >>> > Info: Established X server connection.
>> >>> > Info: Using shared memory parameters 0/0K.
>> >>> > Session: Terminating session at 'Tue Feb 24 14:19:31 2009'.
>> >>> > Session: Session terminated at 'Tue Feb 24 14:19:31 2009'.
>> >>> >
>> >>> ________________________________________________________________
>> >>>     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
>> ________________________________________________________________
>
>
> ________________________________________________________________
>     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
> ________________________________________________________________
>