PDA

View Full Version : Diagnosing dropouts



Michael Haan
2004-12-23, 12:12
I will try that later tonight and see what the results are.  It may not matter however, the sb is now having intermittant issues connecting to the sb.  Just now, it said it couldn't find it, though I confirmed it was running and that I could send net traffic over the same link it is using (albeit suprisingly slowly).  Then, I did an FTP upload over that link to the slimserver and *boom*, the sb was now connected.  That lasted about 15 seconds, then it lost it again.  About 45 seconds later, reconnect and has stayed that was for a few minutes now.  Any ideas?  The link goes sb-->d-link switch-->powerline-->linksys router-->slimserver.









>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-23, 12:22
Michael Haan wrote:
> I will try that later tonight and see what the results are. It may not
> matter however, the sb is now having intermittant issues connecting to
> the sb. Just now, it said it couldn't find it, though I confirmed it
> was running and that I could send net traffic over the same link it is
> using (albeit suprisingly slowly). Then, I did an FTP upload over that
> link to the slimserver and *boom*, the sb was now connected. That
> lasted about 15 seconds, then it lost it again. About 45 seconds later,
> reconnect and has stayed that was for a few minutes now. Any ideas?
> The link goes sb-->d-link switch-->powerline-->linksys router-->slimserver.

Ooh, that sounds very fishy. I'm thinking OSI layer 1 interference. Any
el cheapo wall-warts on the same powerline circuit?

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