dccproc eating up 98% of the CPU

Vernon Schryver vjs@calcite.rhyolite.com
Sat Oct 2 02:19:08 UTC 2004

> From: Ruben Safir Secretary NYLXS 

> I'll look, but there is no firewall

It is extremely likely that something in or near your system
is filtering the DCC/UDP/IP traffic like a firewall.
There are at least 30,000 sites using the public DCC servers.

Previous version of the DCC clients have had rare infinite loops, but
none are known today.  I assume you have used `cdcc -V` and 
`dccproc -V` to ensure that you are running the version 1.2.54 that
you said you are running.

> I do get this result at leaste from one if the IP addresses listed in the 
> cdcc info command
> www2:~ # ping
> PING ( from : 56(84) bytes of data.
> >From icmp_seq=1 Destination Host Unreachable

I do not see in 
Perhaps you meant or

> Traceroute does this
> traceroute to (, 30 hops max, 40 byte packets

>  12  * eth2.dist1-1.sr.sonic.net (  1101 ms !H *
> I'd try it on port 6277 if it would go through

The usual problems are with the UDP responses from the DCC server's
UDP port 6277 to your emphemeral UDP port.

There is something odd near judging from traceroute
from out here:
    traceroute to (, 64 hops max, 44 byte packets

    10  nycmnyzlce1-covad-gige.wcg.net (  77.989 ms
    11  *
    12  *
    13  www2.mrbrklyn.com (  95.704 ms

] From: Ruben Safir Secretary NYLXS 

] > Those consistent "not answering" results imply that you have some
] > kind of firewall that is blocking UDP port 6277.
] > See http://www.dcc-servers.net/dcc/firewall.html
] Oct  1 01:07:04 www2 named[12577]: lame server resolving 'ns.dcc-servers.net' (in 'dcc-servers.NET'?):

It works for me:

    % nslookup ns.dcc-servers.net.
    Server:  ns1.neonova.net

    Non-authoritative answer:
    Name:    ns.dcc-servers.net

Vernon Schryver    vjs@rhyolite.com

More information about the DCC mailing list

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