Since you&#39;ve deleted 99% of the debug log, I can&#39;t tell.  Since you<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">


don&#39;t know what to look for in the logs, you can&#39;t tell, either.<br></blockquote></div><br>Yes, I have no idea what to look for. If I did, I&#39;d have been looking for it, rather than asking the list.<br><br>Not withstanding your replies, I *still* am no closer to knowing *what* to look for. (which is odd, because that was my original question)<br>

<br>So , ignoring the previous discussion, I&#39;ll ask specific questions.<br>(anyone please fee free to chip in)<br><br>Exactly how does freeradius identify a downstream radius as &#39;dead&#39; ?<br><br>Clearly that&#39;s not as trivial as &quot;no replies are received&quot; because there clearly are replies being received; tcpdump shows replies coming back (ie the network stack sees acct-reply packets coming back from the downstream server), the log shows replies coming back (so freeradius sees them too).<br>

<br>Is a server declared &#39;dead&#39; because one single request did not get a reply?<br><br>More than one?<br><br>More than two?<br><br>Should I keep counting?<br><br>Is there any  way to find out how many &#39;missed&#39; replies a downstream server has?<br>

<br>Is there any way to tell freeradius to log in the debug messages *when* it has given up and decided &quot;ok, we&#39;ve obviously missed that request&quot;. (because there&#39;s no messages showing that with -X -xx)<br>

<br>Thanks,<br> Phil P<br>