[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    Re: [FreeNX-kNX] problems w/ freenx 0.7.3 w/ latest nomachine
From:       Matt Nicholson <sjoeboo () sjoeboo ! com>
Date:       2009-02-02 15:35:46
Message-ID: 15da49710902020735r3a2b582bl7d8b2e30b45f542e () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Got it!. It was the /tmp/X11-tmp dir, but it needed the mode of 1777 to
work. Thanks!


Matthew Nicholson
nicholson@eps.harvard.edu
Harvard University
FAS IT Research Computing
Dept. Of Earth and Planetary Science


On Mon, Feb 2, 2009 at 8:42 AM, Matt Nicholson <sjoeboo@sjoeboo.com> wrote:

> mmm, no luck so far, even after creating /tmp/.X11-tmp :
>
> nxnode_reader: NX> 1004 Error: NX Agent exited with exit status 1. To
> troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate
> "/n/home/nichols2/.nx/F-C-iliadaccess04-1001-5CA0A5908B985B50EFBCD3BB4ACA772A/session".
> You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent to
> test the basic functionality. Session log follows:
> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
> SESSION_LOG_CLEAN=0 in node.conf and investigate
> "/n/home/nichols2/.nx/F-C-iliadaccess04-1001-5CA0A5908B985B50EFBCD3BB4ACA772A/session".
> You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent to
> test the basic functionality. Session log follows:
> NX> 105 server_nxnode_echo: NX> 596 Session startup failed.
> NX> 596 Session startup failed.
> server_nxnode_echo: NX> 1004 Error: NX Agent exited with exit status 1. To
> troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate
> "/n/home/nichols2/.nx/F-C-iliadaccess04-1001-5CA0A5908B985B50EFBCD3BB4ACA772A/session".
> You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent to
> test the basic functionality. Session log follows:
> nxnode_reader: Error: Aborting session with 'Cannot establish any listening
> sockets - Make sure an X server isn't already running'.
> nxnode_reader: Session: Aborting session at 'Mon Feb  2 08:41:47 2009'.
> nxnode_reader: Session: Session aborted at 'Mon Feb  2 08:41:47 2009'.
> nxnode_reader: NX> 1006 Session status: closed
> Error: Aborting session with 'Cannot establish any listening sockets - Make
> sure an X server isn't already running'.
> Session: Aborting session at 'Mon Feb  2 08:41:47 2009'.
> Session: Session aborted at 'Mon Feb  2 08:41:47 2009'.
> NX> 1006 Session status: closed
> session_close 5CA0A5908B985B50EFBCD3BB4ACA772A
> server_nxnode_echo: NX> 1006 Session status: closed
> Info: Closing connection to slave with pid 9176.
> nxnode_reader: 1001 Bye.
> 1001 Bye.
> nxnode_reader: NX> 1001 Bye.
> NX> 1001 Bye.
> server_nxnode_echo: NX> 1001 Bye.
> Info: Closing connection to slave with pid 9176.
>
>
> Matthew Nicholson
> nicholson@eps.harvard.edu
> Harvard University
> FAS IT Research Computing
> Dept. Of Earth and Planetary Science
>
>
> On Mon, Feb 2, 2009 at 4:17 AM, Florian Schmidt <fschmidt@gmx.at> wrote:
>
>> Hi,
>>
>> please check if /tmp/.X11-unix dir is created. Nxagent doesn't create it
>> but depends on it. If on the machine a local X11 server is running the dir
>> is created by this X11 server but if not (e.g.: Runlevel 3) nxagent doesn't
>> create it but depends on it. The error message in the log files is the same
>> as mentioned.
>>
>> Cheers Florian
>> -------- Original-Nachricht --------
>> > Datum: Sat, 31 Jan 2009 10:09:57 +0100
>> > Von: "Verner Kjærsgaard" <vk@os-academy.dk>
>> > An: User Support for FreeNX Server and kNX Client <freenx-knx@kde.org>
>> > Betreff: Re: [FreeNX-kNX] problems w/ freenx 0.7.3 w/ latest nomachine
>>      sources on RHEL5...
>>
>> >
>> >
>> > Mario Becroft skrev:
>> > > Matt Nicholson <sjoeboo@sjoeboo.com> writes:
>> > >
>> > >> Mario, what port would that be? I assume we're talking a unix socket,
>> > not a tcp
>> > >> port?
>> > >
>> > > I had in mind the error "Cannot establish any listening sockets" which
>> > > seems to imply that it was trying to listen. Presumably a TCP socket
>> on
>> > > the X11 display port 6000 + screen number. Mind you, I think by
>> default
>> > > freenx disables tcp connections to the nxagent, so maybe not.
>> > >
>> > > I don't actually know what is wrong, sorry, just suggesting a possible
>> > > avenue for diagnosis.
>> > >
>> >
>> > A wild shot in the dark...I don't really know if this (info below) is of
>> > any help or will just cause further confusion :-)
>> >
>> > I ran into a problem with NX and VirtualBOX, a clash/fight over
>> > available ports. I solved it by editing the /etc/nxserver/node.conf like
>> > this:
>> >
>> > # The base display number from which sessions are started.
>> > #DISPLAY_BASE=1000
>> > DISPLAY_BASE=1100
>> >
>> >
>> >
>> > --
>> > ------------------------------
>> > Med venlig hilsen/Best regards
>> > Verner Kjærsgaard
>> > Open Source Academy
>> > +45 56964223
>> >
>> > Novell Certified Linux
>> > Professional 10035701
>> > ------------------------------
>> > ________________________________________________________________
>> >      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@kde.org
>> >       https://mail.kde.org/mailman/listinfo/freenx-knx
>> > ________________________________________________________________
>>
>> --
>> Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL
>> für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a
>> ________________________________________________________________
>>     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@kde.org
>>      https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>
>

[Attachment #5 (text/html)]

Got it!. It was the /tmp/X11-tmp dir, but it needed the mode of 1777 to work. \
Thanks!<br><br><br clear="all">Matthew Nicholson<br><a \
href="mailto:nicholson@eps.harvard.edu">nicholson@eps.harvard.edu</a><br>Harvard \
University<br> FAS IT Research Computing<br>Dept. Of Earth and Planetary Science<br>
<br><br><div class="gmail_quote">On Mon, Feb 2, 2009 at 8:42 AM, Matt Nicholson <span \
dir="ltr">&lt;<a href="mailto:sjoeboo@sjoeboo.com">sjoeboo@sjoeboo.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> mmm, no luck so far, even after \
creating /tmp/.X11-tmp :<br><br>nxnode_reader: NX&gt; 1004 Error: NX Agent exited \
with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and \
investigate &quot;/n/home/nichols2/.nx/F-C-iliadaccess04-1001-5CA0A5908B985B50EFBCD3BB4ACA772A/session&quot;. \
You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent to test the \
basic functionality. Session log follows:<br>

NX&gt; 1004 Error: NX Agent exited with exit status 1. To troubleshoot set \
SESSION_LOG_CLEAN=0 in node.conf and investigate \
&quot;/n/home/nichols2/.nx/F-C-iliadaccess04-1001-5CA0A5908B985B50EFBCD3BB4ACA772A/session&quot;. \
You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent to test the \
basic functionality. Session log follows:<div class="Ih2E3d"> <br>
NX&gt; 105 server_nxnode_echo: NX&gt; 596 Session startup failed.<br>NX&gt; 596 \
Session startup failed.<br></div>server_nxnode_echo: NX&gt; 1004 Error: NX Agent \
exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and \
investigate &quot;/n/home/nichols2/.nx/F-C-iliadaccess04-1001-5CA0A5908B985B50EFBCD3BB4ACA772A/session&quot;. \
You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent to test the \
basic functionality. Session log follows:<div class="Ih2E3d"> <br>
nxnode_reader: Error: Aborting session with &#39;Cannot establish any listening \
sockets - Make sure an X server isn&#39;t already \
running&#39;.<br></div>nxnode_reader: Session: Aborting session at &#39;Mon Feb&nbsp; \
2 08:41:47 2009&#39;.<br>

nxnode_reader: Session: Session aborted at &#39;Mon Feb&nbsp; 2 08:41:47 \
2009&#39;.<div class="Ih2E3d"><br>nxnode_reader: NX&gt; 1006 Session status: \
closed<br></div>Error: Aborting session with &#39;Cannot establish any listening \
sockets - Make sure an X server isn&#39;t already running&#39;.<br>

Session: Aborting session at &#39;Mon Feb&nbsp; 2 08:41:47 2009&#39;.<br>Session: \
Session aborted at &#39;Mon Feb&nbsp; 2 08:41:47 2009&#39;.<div \
class="Ih2E3d"><br>NX&gt; 1006 Session status: closed<br></div>session_close \
5CA0A5908B985B50EFBCD3BB4ACA772A<div class="Ih2E3d"> <br>
server_nxnode_echo: NX&gt; 1006 Session status: closed<br></div>Info: Closing \
connection to slave with pid 9176.<div class="Ih2E3d"><br>nxnode_reader: 1001 \
                Bye.<br>1001 Bye.<br>nxnode_reader: NX&gt; 1001 Bye.<br>NX&gt; 1001 \
                Bye.<br>
server_nxnode_echo: NX&gt; 1001 Bye.<br></div>
Info: Closing connection to slave with pid 9176.<div class="Ih2E3d"><br><br><br \
clear="all">Matthew Nicholson<br><a href="mailto:nicholson@eps.harvard.edu" \
target="_blank">nicholson@eps.harvard.edu</a><br>Harvard University<br> FAS IT \
Research Computing<br>Dept. Of Earth and Planetary Science<br>

<br><br></div><div><div></div><div class="Wj3C7c"><div class="gmail_quote">On Mon, \
Feb 2, 2009 at 4:17 AM, Florian Schmidt <span dir="ltr">&lt;<a \
href="mailto:fschmidt@gmx.at" target="_blank">fschmidt@gmx.at</a>&gt;</span> \
wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi,<br>
<br>
please check if /tmp/.X11-unix dir is created. Nxagent doesn&#39;t create it but \
depends on it. If on the machine a local X11 server is running the dir is created by \
this X11 server but if not (e.g.: Runlevel 3) nxagent doesn&#39;t create it but \
depends on it. The error message in the log files is the same as mentioned.<br>


<br>
Cheers Florian<br>
-------- Original-Nachricht --------<br>
&gt; Datum: Sat, 31 Jan 2009 10:09:57 +0100<br>
&gt; Von: &quot;Verner Kjærsgaard&quot; &lt;<a href="mailto:vk@os-academy.dk" \
target="_blank">vk@os-academy.dk</a>&gt;<br> &gt; An: User Support for FreeNX Server \
and kNX Client &lt;<a href="mailto:freenx-knx@kde.org" \
target="_blank">freenx-knx@kde.org</a>&gt;<br> &gt; Betreff: Re: [FreeNX-kNX] \
problems w/ freenx 0.7.3 w/ latest nomachine &nbsp; &nbsp; &nbsp; &nbsp;sources on \
RHEL5...<br> <div><div></div><div><br>
&gt;<br>
&gt;<br>
&gt; Mario Becroft skrev:<br>
&gt; &gt; Matt Nicholson &lt;<a href="mailto:sjoeboo@sjoeboo.com" \
target="_blank">sjoeboo@sjoeboo.com</a>&gt; writes:<br> &gt; &gt;<br>
&gt; &gt;&gt; Mario, what port would that be? I assume we&#39;re talking a unix \
socket,<br> &gt; not a tcp<br>
&gt; &gt;&gt; port?<br>
&gt; &gt;<br>
&gt; &gt; I had in mind the error &quot;Cannot establish any listening sockets&quot; \
which<br> &gt; &gt; seems to imply that it was trying to listen. Presumably a TCP \
socket on<br> &gt; &gt; the X11 display port 6000 + screen number. Mind you, I think \
by default<br> &gt; &gt; freenx disables tcp connections to the nxagent, so maybe \
not.<br> &gt; &gt;<br>
&gt; &gt; I don&#39;t actually know what is wrong, sorry, just suggesting a \
possible<br> &gt; &gt; avenue for diagnosis.<br>
&gt; &gt;<br>
&gt;<br>
&gt; A wild shot in the dark...I don&#39;t really know if this (info below) is of<br>
&gt; any help or will just cause further confusion :-)<br>
&gt;<br>
&gt; I ran into a problem with NX and VirtualBOX, a clash/fight over<br>
&gt; available ports. I solved it by editing the /etc/nxserver/node.conf like<br>
&gt; this:<br>
&gt;<br>
&gt; # The base display number from which sessions are started.<br>
&gt; #DISPLAY_BASE=1000<br>
&gt; DISPLAY_BASE=1100<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; ------------------------------<br>
&gt; Med venlig hilsen/Best regards<br>
&gt; Verner Kjærsgaard<br>
&gt; Open Source Academy<br>
&gt; +45 56964223<br>
&gt;<br>
&gt; Novell Certified Linux<br>
&gt; Professional 10035701<br>
&gt; ------------------------------<br>
&gt; ________________________________________________________________<br>
&gt; &nbsp; &nbsp; &nbsp;Were you helped on this list with your FreeNX problem?<br>
&gt; &nbsp; &nbsp; Then please write up the solution in the FreeNX Wiki/FAQ:<br>
&gt;<br>
&gt; <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" \
target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
 &gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Don&#39;t forget to check the NX Knowledge \
Base:<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a \
href="http://www.nomachine.com/kb/" \
target="_blank">http://www.nomachine.com/kb/</a><br> &gt;<br>
&gt; ________________________________________________________________<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;FreeNX-kNX mailing list --- <a \
href="mailto:FreeNX-kNX@kde.org" target="_blank">FreeNX-kNX@kde.org</a><br> &gt; \
&nbsp; &nbsp; &nbsp; <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" \
target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br> &gt; \
________________________________________________________________<br> <br>
</div></div><font color="#888888">--<br>
Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL<br>
für nur 17,95 Euro/mtl.!* <a href="http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a" \
target="_blank">http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a</a><br> \
</font><div><div></div><div>________________________________________________________________<br>
  &nbsp; &nbsp; Were you helped on this list with your FreeNX problem?<br>
 &nbsp; &nbsp;Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" \
target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
 <br>
 &nbsp; &nbsp; &nbsp; &nbsp; Don&#39;t forget to check the NX Knowledge Base:<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a \
href="http://www.nomachine.com/kb/" \
target="_blank">http://www.nomachine.com/kb/</a><br> <br>
________________________________________________________________<br>
 &nbsp; &nbsp; &nbsp; FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org" \
target="_blank">FreeNX-kNX@kde.org</a><br>  &nbsp; &nbsp; &nbsp;<a \
href="https://mail.kde.org/mailman/listinfo/freenx-knx" \
target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br> \
________________________________________________________________<br> \
</div></div></blockquote></div><br> </div></div></blockquote></div><br>



________________________________________________________________
     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@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic