PDA

View Full Version : Diagnosing dropouts



Michael Haan
2004-12-23, 20:16
Ok, this is running.  Any pointers as to what to look at when a skip happens?









>From: Jack Coates <jack (AT) monkeynoodle (DOT) org>



>Reply-To: Slim Devices Discussion <discuss (AT) lists (DOT) slimdevices.com>



>To: Slim Devices Discussion <discuss (AT) lists (DOT) slimdevices.com>



>Subject: [slim] Diagnosing dropouts



>Date: Thu, 23 Dec 2004 07:47:37 -0800



>



>Michael Haan wrote:



>>I've been trying to track down this ghost in the machine as well.  



>>Last night, I had squeeze running while I monitored the buffer and



>>ran KDE monitor on the linux box running slimserver.  For the most



>>part, everything was fine, but twice (when the drop-out occurred) I



>>saw the buffer go to zero.  The CPU showed no appreciable increase



>>in load (in fact, it decreasedduring the dropout), there was zero



>>swap, no increase in physical memory and no increase in average



>>load.  In the first case, a few seconds later the buffer refilled



>>and the cpu rose to it's pre-dropout level.  In the second case,



>>the buffer dropped to zero and stayed there, the cpu dropped, and



>>all other indications were the same as the first.  Eventually, the



>>squeeze reported it couldn't find slimserver even though I verified



>>it was running.  Powering-off and on the squeeze caused it to be



>>able to find slimserver.  In this instance, I was streaming FLAC



>>over powerline to a squeezeG from slimserver 5.4.  Any thoughts



>>anyone?



>>



>



>did the network traffic actually stop during the drop out? iptraf is



>a good tool for watching this, or tcpdump -n -i eth0 tcp port 3843



>



>--



>Jack at Monkeynoodle dot Org: It's a Scientific Venture...



>Riding the Emergency Third Rail Power Trip since 1996!



>_______________________________________________



>Discuss mailing list



>Discuss (AT) lists (DOT) slimdevices.com



>http://lists.slimdevices.com/lists/listinfo/discuss

Jack Coates
2004-12-24, 00:05
Michael Haan wrote:
> Ok, this is running. Any pointers as to what to look at when a skip
> happens?

there's going to be a counter for port 3843 -- if it stops all by itself
when the buffer starts to drain, then slimserver or the squeezebox are
at fault. If all counters plus the UDP/ICMP noise at the bottom stop
when the buffer starts to drain, you have a more general network problem.

--
Jack at Monkeynoodle dot Org: It's a Scientific Venture...
Riding the Emergency Third Rail Power Trip since 1996!