All of the frontends (clients) are identical hardware? If so, are the BIOS
video settings identical in terms of memory size, onboard vs add-on
priority? Sounds like X.Org locking up is the root of your problem. The log
you might want to check is /var/logs/X.org.log from your frontend or
whatever it is named on your distro.
The first change you cite on 05/03/2013 was when the problem started, just
after you changed the network switch? Or that was the remedy you tried
after having had problems with this client.
Cheers,
On Thu, Mar 21, 2013 at 9:15 PM, Michael Pope <mich...@dtcorp.com.au> wrote:
> I'm running LTSP 5.2.1 under Ubuntu 10.04 with 9 frontends and in the
> last few months there is one frontend which is freezing within the GUI
> (Gnome2) about once a day sometimes. What I mean by frozen is, we can
> move the mouse but not use the keyboard and cannot click on any window
> or menu within the system. I cannot jump to a virtual terminal using
> <ctrl><alt><F1> or any other VT.
>
> Here is what I've tried (in order and the problem still exists after
> each change)
> 05/03/2013 - Swapped hardware
> - [X] Change over network switch with new
> - [X] Change over thin client with a known working thin client
>
> 06/03/2013 - Froze
> - [X] Change port used on wall plate to the new network switch
> (This involved switching the cables in the patch panel around so
> different patch cable is used here).
> - [X] Change cable from Netgear 5-port router to wall plate
> - [X] Change patch cable used for terminal
>
> 07/03/2013 @ 8:20 - Froze
> - [X] Swap Red cable between Netgear router & thin client.
>
> 22/03/2013 @ 11:45 - Froze
> - It showed up disconnected in Epoptes, but I could still get the IP &
> connect via SSH
> - I could reboot the machine over that ssh link.
>
> So I've changed all the cables between the server and thin client now
> and the actual thin client itself. I've changed the switch that was used
> next the thin client.
>
> When I ssh into the thin client whilst in it's 'frozen' state I can see
> that Xorg is using 100% of the CPU.
>
> What else can I try?
> There is nothing obvious in the syslog or messages log, are there other
> log files or ltsp specific logs which I should check?
>
>
> Michael Pope
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
--
Jay Goldberg | AvianBLUE Network Systems
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
