<br><tt><font size=2>freenx-knx-bounces@kde.org wrote on 14/10/2011 10:31:55:<br>
<br>
> Hi,<br>
> <br>
> I've just upgraded my server from CentOS 5.6 to 5.7 with yum
<br>
> update, which replaced lots of packages, but I believe, the freenx
<br>
> package was not touched.</font></tt>
<br>
<br><tt><font size=2>FreeNX and the NX libraries were updated in centos/extra
in May,</font></tt>
<br><tt><font size=2>but not as part of the base update to 5.7</font></tt>
<br>
<br><tt><font size=2>> After the upgrade I rebooted the server.
<br>
> Since then, though I can start a new nx session, I can't reconnect
<br>
> to it if I suspend it. The client (OpenNX on OSX Lion) simply
<br>
</font></tt>
<br><tt><font size=2>So, sounds like a server issue (but don't bet on it
just yet)</font></tt>
<br>
<br><tt><font size=2>> segfaults, when trying to reconnect. If
I restart the freenx <br>
> server, or kill my all nxagent process, I can start a new session
again.<br>
</font></tt>
<br><tt><font size=2>Try reconnectiong with a different client conbination
. . .</font></tt>
<br><tt><font size=2> e.g. nxclient
or from linux/windows</font></tt>
<br><tt><font size=2>else</font></tt>
<br><tt><font size=2>try connecting locally, on the server</font></tt>
<br><tt><font size=2> i.e. server
to 127.0.0.1 with the linux nxclient.</font></tt>
<br><tt><font size=2>> <br>
> The freenx version installed is the default freenx-0.7.3-7.el5.centos.rpm.<br>
> <br>
> See below the server log during a reconnection trial.<br>
> <br>
> Anyone has the idea what has happened and how to cure it?<br>
> <br>
> Thanks,<br>
> <br>
> Tamás <br>
[SNIP]</font></tt>
<br><tt><font size=2>> > <br>
> > NX> 148 Server capacity: not reached for user: pusztai<br>
> > NX> 105 quit<br>
> > Quit<br>
> > NX> 999 Bye<br>
> > Info: Closing connection to slave with pid 25007.<br>
</font></tt>
<br><tt><font size=2>Hmmm, not much to go on here.</font></tt>
<br>
<br><tt><font size=2>You could just re-install the NX rpms from extra,</font></tt>
<br><tt><font size=2>(or fsck)</font></tt>
<br><tt><font size=2>but</font></tt>
<br><tt><font size=2>it's good to try to find out what's going wrong</font></tt>
<br><tt><font size=2> (or at least where)
first . . . .</font></tt>
<br>
<br>
<br>
<br>
<br>