Log message from WLIST tracing

Gary Mills mills@cc.umanitoba.ca
Fri Mar 26 14:29:28 UTC 2010


On Thu, Mar 25, 2010 at 07:35:15PM +0000, Vernon Schryver wrote:
> 
> To find the cause of those messages, first search for the checksum
> "28855f6f 882a9a62 5dea098c 544d7fd9" in the DCC client log files in
> /var/dcc/log on 130.179.16.64.
> 
> If that does not discover the cause, then determine the IP address that
> corresponds to the checksum by feeding IP addresses that are in dccd's
> /var/dcc/whitelist or any included files such as whitecommon, as in
> 
>     dccproc -QC -a 130.179.16.34 <<EOF
>     header:asdf
> 
>     asdf
>     EOF 

Thanks for explaining that technique.

> That gives me:
> 
>     X-DCC-Rhyolite-Metrics: calcite.rhyolite.com 101; Body=0 rep=20%
> 				reported: 0               checksum  server
> 			   IP: 28855f6f 882a9a62 5dea098c 544d7fd9
> 		   Message-ID: d41d8cd9 8f00b204 e9800998 ecf8427e
> 		    rep-total: 28855f6f 882a9a62 5dea098c 544d7fd9     491
> 			  rep: 28855f6f 882a9a62 5dea098c 544d7fd9     102
> 
> So it seems that 130.179.16.34 needs to be added to /var/dcc/whiteclnt
> (or perhaps an included file such as /var/dcc/whitecommon) on
> 130.179.16.64

I have all of the local IP addresses (512 /24 networks) defined in the
file localnets.wh that's included into the whitelist file.  So, they
are defined on the server side, not on the client side.  Is that
alright?

-- 
-Gary Mills-        -Unix Group-        -Computer and Network Services-



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.