<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Hi Dick,<br>
<br>
See my comments below:<br>
<br>
Dick Trump schreef:
<blockquote cite="mid138617650.20060907202736@triadav.com" type="cite">
<pre wrap="">Maarten makes some poses some valid questions:
</pre>
<blockquote type="cite">
<pre wrap="">Did you check the Linux machines for system and/or update logs at the
given time?
</pre>
</blockquote>
<pre wrap=""><!---->
I'm afraid I don't know all the places to look for logs that might tell me something. My script that keeps MPG123 running keeps a log of all reboots and outages. A reconnect that lasts less than one minute is counted as continuous outage.
</pre>
</blockquote>
Do you mean 'more than one minute?'.<br>
<blockquote cite="mid138617650.20060907202736@triadav.com" type="cite">
<pre wrap="">
Looking more closely at my server's error.log, sorting the entries by client, during that 10 minute span (actually only 7 minute), the actual outages recorded as only a second long and from 2 to 4 drops per client. One of the drops occurred within a second of each other on 5 machines.
</pre>
</blockquote>
Ok, this points to a problem on the machine running Icecast. It is very
unlikely that remote machines would disconnect at almost exact the same
time while they are not related/coordinated other than being connected
to the same icecast instance. The question of course is why only the
Linux clients would be disconnected. One explanation could be that by
coincidence they share some piece of networking equipment that failed
on their network path to your icecast box while the windows machines
didn't.<br>
<br>
Are the machines running a cron job to SYNC time (e.g. using ntpdate)?
Could you detection procedure be fooled by a jump forward/backward in
time?<br>
<br>
I think that's about all I can think of ...<br>
<br>
Regards,<br>
KJ
</body>
</html>