DebuggingLTSP

Differences between revisions 12 and 26 (spanning 14 versions)
⇤ ← Revision 12 as of 2008-09-13 07:50:56 →
Size: 2903
Editor: a80-126-233-153
Comment:
← Revision 26 as of 2008-10-03 07:10:32 → ⇥
Size: 4456
Editor: ip51cffcc4
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 * Please tell how to reproduce the bug.
 * See also: HelpingWithBugs
Line 31: Line 33:
 * LatencyTop (http://www.latencytop.org/); This tools monitors on what actions give the most latency in a process
 * SystemTap (http://sourceware.org/systemtap/) (aptitude install systemtap); Very flexible/scriptable diagnostics tool		  * LatencyTop (http://www.latencytop.org) This tools monitors on what actions give the most latency in a process
 * PowerTop (http://lesswatts.org/projects/powertop) (aptitude install powertop); PowerTOP is a Linux tool that helps you find those programs that are misbehaving while your computer is idle.
 * SystemTap (http://sourceware.org/systemtap) (aptitude install systemtap); Very flexible/scriptable diagnostics tool
Line 36: Line 39:
 * Darkstat (http://dmr.ath.cx/net/darkstat/) (aptitude install darkstat); For network traffic monitoring per port.  * ntop(http://www.ntop.org/) (aptitude install ntop); For network traffic monitoring.
 * BootChart (aptitude install bootchart); For monitoring bootup speed. See also: http://www.hamilton.ie/gavinmc/edubuntu/bootchart.html and LtspBootPerformance
 * See also: DebuggingProcedures
Line 40: Line 45:

 * Video drivers on the server (are they installed correctly?). You can check that via the /var/log/Xorg.0.log if the drivers are loaded correctly. Search for (WW), (EE) and (!!). The command `cat /var/log/Xorg.0.log | egrep '(\(EE\)|\(WW\)|\(!!\))'` should help you filter it.
 * Video drivers on the client. Same as for the server, but now on a running LTSP client.
 * Check if disk/file indexing is turned on on the server. This will give some disk usage. Which can slow the system down.
 * Memory per client
 * Disk usage per client
 * For locking with sound, you could try to use PulseAudio fully. (in lts.conf: SOUND_DAEMON=pulse)
 * Try another Window Manager (like ICEWM). It could be that Gnome is very slow. If that speeds up, you know what might be the problem.
 * Check the load average with the command uptime.
Line 49: Line 63:
 * bonobo-activation-server
Line 50: Line 65:

See also: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/49594

=== Workarounds / Solutions ===
 
 * Workaround: For the ophrane processes, you can install gnome-watchdog (http://logicalnetworking.net/other/gnome-watchdog_0.9.2_i386.deb)

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

This page lists some helpful steps when filing an ltsp bug

  • It is very helpful if you include version numbers of the ltsp (or ltspfs) packages in your bug report (see below how to get the right version numbers for the various packages).
  • If you modified any defaults in your thin client chroot, please mention this.
  • Did you change anything in your lts.conf file (until gutsy in /opt/ltsp/i386/etc/, later in /var/lib/tftpboot/ltsp/i386/), if so, please attach it.
  • Architecture: x86 or amd64
  • Please tell how to reproduce the bug.

  • See also: HelpingWithBugs

Get the versions of the packages: 

dpkg -l ltsp-server
dpkg -l ltsp-server-standalone
dpkg -l --root=/opt/ltsp/i386 ldm
dpkg -l --root=/opt/ltsp/i386 ltsp-client
dpkg -l --root=/opt/ltsp/i386 ltsp-client-core # gutsy only

Is your bug related to local devices: 

dpkg -l ltspfs
dpkg -l --root=/opt/ltsp/i386 ltspfsd

Debugging speed problems

Debugging tools

These tools you could use to monitor some speed problems, so you could find the bottlenecks:

Configuration check

These things you need to check if they are working correctly on your system:

  • Video drivers on the server (are they installed correctly?). You can check that via the /var/log/Xorg.0.log if the drivers are loaded correctly. Search for (WW), (EE) and (!!). The command cat /var/log/Xorg.0.log | egrep '(\(EE\)|\(WW\)|\(!!\))' should help you filter it.

  • Video drivers on the client. Same as for the server, but now on a running LTSP client.
  • Check if disk/file indexing is turned on on the server. This will give some disk usage. Which can slow the system down.
  • Memory per client
  • Disk usage per client

  • For locking with sound, you could try to use PulseAudio fully. (in lts.conf: SOUND_DAEMON=pulse)

  • Try another Window Manager (like ICEWM). It could be that Gnome is very slow. If that speeds up, you know what might be the problem.
  • Check the load average with the command uptime.

Bugs not directly with LTSP, but affect LTSP environments

  • Policykit not allowing remote sessions (Both ssh -X that ltsp uses, and NX sessions) to access admin functionality:

https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/221363

Orphane processes

See also: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/49594

Workarounds / Solutions

CategoryBugSquad CategoryDebugging

DebuggingLTSP (last edited 2008-10-03 07:10:32 by ip51cffcc4)