DCC version 1.3.104/2.3.104 released

Petar Bogdanovic petar@smokva.net
Wed May 27 14:50:24 UTC 2009


On Wed, May 27, 2009 at 03:08:18PM +0200, Petar Bogdanovic wrote:
> On Wed, May 27, 2009 at 02:32:15PM +0200, Petar Bogdanovic wrote:
> > 
> > (...)
> > 
> > Ok, makes sense.  He'll retry on 16:04:27.  `cdcc RTT' will trigger the
> > re-resolve immediately, so I'll run that from somewhere..
> 
> 
> Sorry for the monologue but even if `cdcc RTT' re-resolves all
> hostnames, I still get errors in the maillog:
> 
> 	dccifd[329]: no DCC answer from dcc1.dcc-servers.net (209.169.14.26,6277) after 6050 ms
> 	dccifd[329]: write(MTA socket,75): Broken pipe
> 	dccifd[329]: no DCC answer from dcc2.dcc-servers.net (203.81.36.6,6277) after 8641 ms
> 	dccifd[329]: write(MTA socket,72): Broken pipe
> 	dccifd[329]: no DCC answer from dcc4.dcc-servers.net (152.20.253.5,6277) after 13910 ms
> 	dccifd[329]: write(MTA socket,71): Broken pipe
> 	dccifd[329]: no DCC answer from dcc3.dcc-servers.net (194.228.41.73,6277) after 6050 ms
> 	dccifd[329]: write(MTA socket,71): Broken pipe
> 
> 
> I tried "IPv6 off" (since the local packet filter drops all IPv6
> traffic)..
> 
> 	IPv6 off   version=3
> 
> 	dcc1.dcc-servers.net,-      RTT+1000 ms  anon
> 	#  137.208.8.26,-                                             wuwien ID 1290
> 	#     protocol version 8
> 	#     100% of  4 requests ok  667.04+1000 ms RTT       100 ms queue wait
> 	#  209.169.14.26,-                                     x.dcc-servers ID 104
> 	#      33% of  6 requests ok 2604.78+1000 ms RTT       100 ms queue wait
> 	#  209.169.14.29,-                                     x.dcc-servers ID 104
> 	#      33% of  6 requests ok 2604.76+1000 ms RTT       100 ms queue wait
> 
> 	dcc2.dcc-servers.net,-      RTT+1000 ms  anon
> 	#  195.20.8.232,-                                          EATSERVER ID 1166
> 	#      33% of  6 requests ok 2533.57+1000 ms RTT       100 ms queue wait
> 	#  203.81.36.6,-                                           PacNet-SG ID 1358
> 	#      50% of  8 requests ok 4000.00+1000 ms RTT       200 ms queue wait
> 
> 	dcc3.dcc-servers.net,-      RTT+1000 ms  anon
> 	# *194.228.41.73,-                                          CTc-dcc1 ID 1030
> 	#     protocol version 8
> 	#     100% of  2 requests ok  135.03+1000 ms RTT       100 ms queue wait
> 	#  209.169.14.27,-                                     x.dcc-servers ID 104
> 	#      33% of  6 requests ok 4000.00+1000 ms RTT       100 ms queue wait
> 
> 	dcc4.dcc-servers.net,-      RTT+1000 ms  anon
> 	#  152.20.253.5,-                                       dcc.uncw.edu ID 1201
> 	#      33% of  6 requests ok 2638.36+1000 ms RTT       100 ms queue wait
> 	#  194.228.41.13,-                                          CTc-dcc2 ID 1031
> 	#     protocol version 8
> 	#     100% of  2 requests ok  135.52+1000 ms RTT       100 ms queue wait
> 
> 	dcc5.dcc-servers.net,-      RTT+1000 ms  anon
> 	#  209.34.225.42,-                                 
> 	#      not answering
> 	#  216.240.97.12,-                                           dmv.com ID 1181
> 	#     protocol version 8
> 	#     100% of  2 requests ok  211.64+1000 ms RTT       100 ms queue wait
> 
> 
> ..but no luck:
> 
> 	dccifd[208]: no DCC answer from dcc1.dcc-servers.net (209.169.14.26,6277) after 6050 ms
> 	dccifd[208]: write(MTA socket,75): Broken pipe
> 	dccifd[208]: no DCC answer from dcc2.dcc-servers.net (203.81.36.6,6277) after 8722 ms
> 	dccifd[208]: write(MTA socket,71): Broken pipe
> 
> 
> What's wrong here?  1.3.103 still runs fine..


FYI, cdcc-1.3.103 info:

	# cdcc info
	# 05/27/09 16:47:58 CEST  /var/dcc/map
	# Re-resolve names after 17:11:44  
	# 1225.45 ms threshold, 1222.13 ms average    12 total, 10 working servers
	IPv6 off

	dcc1.dcc-servers.net,-      RTT+1000 ms  anon
	#  137.208.8.26,-                                             wuwien ID 1290
	#     protocol version 8
	#     100% of  1 requests ok  125.45+1000 ms RTT       100 ms queue wait
	#  209.169.14.26,-                                     x.dcc-servers ID 104
	#     100% of  1 requests ok  244.98+1000 ms RTT       100 ms queue wait
	#  209.169.14.29,-                                     x.dcc-servers ID 104
	#     100% of  1 requests ok  244.26+1000 ms RTT       100 ms queue wait

	dcc2.dcc-servers.net,-      RTT+1000 ms  anon
	# *195.20.8.232,-                                          EATSERVER ID 1166
	#     100% of 13 requests ok  123.01+1000 ms RTT       100 ms queue wait
	#  203.81.36.6,-                                           PacNet-SG ID 1358
	#     100% of  2 requests ok  619.84+1000 ms RTT       200 ms queue wait

	dcc3.dcc-servers.net,-      RTT+1000 ms  anon
	#  194.228.41.73,-                                          CTc-dcc1 ID 1030
	#     protocol version 8
	#     100% of  1 requests ok  135.40+1000 ms RTT       100 ms queue wait
	#  209.169.14.27,-                                     x.dcc-servers ID 104
	#     100% of  1 requests ok  244.91+1000 ms RTT       100 ms queue wait

	dcc4.dcc-servers.net,-      RTT+1000 ms  anon
	#  152.20.253.5,-                                       dcc.uncw.edu ID 1201
	#     100% of  1 requests ok  227.51+1000 ms RTT       100 ms queue wait
	#  194.228.41.13,-                                          CTc-dcc2 ID 1031
	#     protocol version 8
	#     100% of  1 requests ok  135.43+1000 ms RTT       100 ms queue wait

	dcc5.dcc-servers.net,-      RTT+1000 ms  anon
	#  209.34.225.42,-                                 
	#      not answering
	#  216.240.97.12,-                                           dmv.com ID 1181
	#     protocol version 8
	#     100% of  1 requests ok  213.90+1000 ms RTT       100 ms queue wait


No failed requests, much lower RTTs.



More information about the DCC mailing list

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