• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cannot fetch or flush RC5 - - - - - HELP ! ? !

X

xrayman

Member
[Nov 28 17:55:19 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Nov 28 17:55:19 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 28 17:55:22 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Nov 28 17:55:22 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 28 17:55:25 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Nov 28 17:55:25 UTC] Could not update to/from the net. Network down?

This has been going on for several days. I've tried about every '-config' setting that might affect '-update'. The herd is crunching empty calories (randoms) and I've run out of ideas.

Dial-up works okay, I get the email and, obviously, the web. Usually connects at 50,666b/s! Turned off ZoneAlarm and anything else that might possibly interfere and got no improvement.
Have not tried re-installing the client, but that's next I suppose.

Could this be a bug in the client? Here's my beta ver.
dnetc v2.8010-463-CTR-00071213 for Win32 (WindowsNT 4.0)

Please help me, I drowning in processed keys!

Geoff
 
xrayman:

Try updating to the RoundRobin... proxy.teamanandtech.com or the port 80 RR proxy80.teamanandtech.com or the port 23 RR proxy23.teamanandtech.com

Hope this works otherwise you can email me the blocks and I'll send you new buffers and flush for ya!

With love and respect your fellow TA member

Two-Face
 
Use the TeAm proxy.

Bring up the configure menu
Select 2, Buffer and Buffer update options
Select 6, Keyserver<->client connectivity options
Select 2, Automatically select a distributed.net keyserver
Set the value to no
Select 3, keyserver hostname
set it to www.teamanandtech.com
Keep selecting 0 until you are out of the config menu.

Extra benefit - you can check your stats at
www.teamanandtech.com
select distributed.net from left column
select RC5 fullstats
page through stats for yours!

Enjoy!

 
Geoff,
It could indeed be your beta. If that's not the latest (version g) then try downloading and installing the latest. If it is the latest, try the production version. I'm using the production version with Zone Alarm and have had no problems yet.

Could someone email Geoff some high-calorie feed? I'm not in a position to do so, or else I would offer.
 
Does changing to use the proxy fix it?
If not I can at least e-mail you a juicy buff-in
while you work on the problem.

LMK

[Edit]
Actually, I do remember dnet having some network
problems with the new client when it first came out.
[/Edit]
 
I'm more than willing to mail you some feed xrayman, I just need to know how big a buffer you want, or if you want more than one how big they should be...

just lemme know!

Oh and btw, 463 isn't a beta that's the latest released client... at least if it's 463b and it should be... 464g is the latest beta!

Good luck!

With love and respect your fellow TA member

Two-Face
 
if it is a DNS problem, try using the IP address of the keyserver instead of the DNS name. I have to do that with my work herd.
 
xrayman,

I have to agree with what's been said earlier. The only times I've ever seen this problem with the client is when either a DNS server died or was unreachable or the client computer had an incorrect or missing DNS server entry.

I'd check first of all to make sure that your ISP/Corporate LAN didn't up and move their DNS server to another IP. Then, check to make sure that it's still set correctly on the client machine.

-Brian

[EDIT]Of course, in retrospect, it's impossible that you'd be getting web pages brought up by name rather than IP if it is a DNS issue. It's possible that by some really, truly strange fluke that us.v27.distributed.net is not in the DNS lookup table of your DNS server, but I can't imagine how. If it's a beta client, go back to the latest full release version, otherwise, I agree that trying the team proxies would be an interim solution.[/EDIT]
 
Hey guys, thanks for the input! Sorry for the lag in my response, but I had to go to work (again).
Nothing worked 🙁
Right now I am d/l the latest client, will install and get back to ya. Can't tell if the full ver.# is different until I install it I guess.

Here are the results of each suggestion in the order they were tried:
---------------
dnetc v2.8010-463-CTR-00071213 for Win32 (WindowsNT 4.0).
Please provide the *entire* version descriptor when submitting bug reports.
The distributed.net bug report pages are at http://www.distributed.net/bugs/
Using email address (distributed.net ID) 'gxxbxw@bxgfxxt.com'

(divide_by_zero)
[Nov 29 06:40:21 UTC] Network::failed to resolve name &quot;www.teamanandtech.com&quot;
[Nov 29 06:40:21 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 06:40:24 UTC] Network::failed to resolve name &quot;www.teamanandtech.com&quot;
[Nov 29 06:40:24 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 06:40:28 UTC] Network::failed to resolve name &quot;us.v27.distributed.net&quot;
[Nov 29 06:40:28 UTC] Could not update to/from the net. Network down?
----------------------------------

(BoberFett)
Pinging us.v27.distributed.net [204.152.186.139]: bytes=32 (best)time=218ms TTL=238
Pinging us.v27.distributed.net [128.104.18.148]: bytes=32 (best)time=157ms TTL=244
-----------------------------------
(TwoFace)
[Nov 29 07:05:36 UTC] Network::failed to resolve name &quot;proxy23.teamanandtech.com&quot;
[Nov 29 07:05:36 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 07:05:39 UTC] Network::failed to resolve name &quot;proxy23.teamanandtech.com&quot;
[Nov 29 07:05:39 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 07:05:42 UTC] Network::failed to resolve name &quot;us.v27.distributed.net&quot;
[Nov 29 07:05:42 UTC] Could not update to/from the net. Network down?
----------------
[Nov 29 07:08:34 UTC] Network::failed to resolve name &quot;proxy.teamanandtech.com&quot;
[Nov 29 07:08:34 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 07:08:37 UTC] Network::failed to resolve name &quot;proxy.teamanandtech.com&quot;
[Nov 29 07:08:37 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 07:08:40 UTC] Network::failed to resolve name &quot;us.v27.distributed.net&quot;
[Nov 29 07:08:40 UTC] Could not update to/from the net. Network down?
----------------
(RaySun2Be)
[Nov 29 07:12:56 UTC] Connect to host 128.104.18.148:2064 failed.
Error 10060 (Attempt to connect timed out)
[Nov 29 07:12:56 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 07:13:30 UTC] Connect to host 128.104.18.148:2064 failed.
Error 10060 (Attempt to connect timed out)
[Nov 29 07:13:30 UTC] Network:😱pen Error - sleeping for 3 seconds
[Nov 29 07:13:33 UTC] Network::failed to resolve name &quot;us.v27.distributed.net&quot;
[Nov 29 07:13:33 UTC] Could not update to/from the net. Network down?
----------------

Thanks again,

Geoff

 
Can you post your log file?

I am assuming that you used to be able to connect to the keyservers. what has changed recently in your setup?
 
Hmm-m, New install of the same ver. client into the same directory w/o deleting old files(retained previous settings which I changed back after testing ideas). /RUN> -update/ got the job done. But WTH is this &quot;Error 13: Permission denied&quot; stuff? AND before the new install there were almost 700 packets to flush!
Oh well, at least it -updated the buffers. Now to see if it will flush out-buffs from the rest of the little herd....

sciencewhiz
Thanks for reminding me to re-enable logging!

dnetc v2.8010-463-CTR-00071213 for Win32 (WindowsNT 4.0).
Please provide the *entire* version descriptor when submitting bug reports.
The distributed.net bug report pages are at http://www.distributed.net/bugs/
Using email address (distributed.net ID) 'xxxx@xxxxxcom'

[Nov 29 08:09:42 UTC] Buffer open failed for 'D:\RC5\buff-in.rc5'
Error 13: Permission denied
[Nov 29 08:04:31 UTC] Automatic processor type detection found
an Intel Celeron-A processor.
[Nov 29 08:04:31 UTC] RC5: using core #2 (RG class 6).
[Nov 29 08:04:36 UTC] Connected to distributed.net 128.104.18.148:2064...
[Nov 29 08:04:36 UTC] The keyserver says: &quot;It's a trick. Get an axe. (bob)&quot;
[Nov 29 08:04:53 UTC] Retrieved RC5 work unit 2015 of 2015 (100.00% transfe ...
[Nov 29 08:04:53 UTC] Retrieved OGR work unit 1 of 1 (100.00% transferred)
[Nov 29 08:06:15 UTC] Sent RC5 packet 305 of 306 (99.67% transferred)



 
You are probably confusing work units and packets. Each packet can contain up to 32 work units. The three hundred or so packets that it flushed could easily have 700 work units. It is likely that since you downloaded 2015 work units, that you also uploaded aproximately 2000 work units.

Edit: I haven't seen the permission denied error before. I would shutdown the computer and then try restarting the client and see if you still get the error.
 
Permission denied would be caused by the prior client not unlocking the buffin after using it, so the new one cant open it. Either rebooting or starting dnetc -forceunlock buff-in.rc5 should take care of that.
 
WHO,...ME?,..Confused?
uhm, well maybe just a little, most of the time 😱

That -forceunlock works great. Guess I could read the HELP FILES once in a while, eh? Thanks LeBlatt! That error has been popping up every so often for about 4 months. *duh*
Anyway thanks to you folks my cows are now happily chewing cuds of fresh work after having thrown a whole bunch of pies at Dnet. Just hope the randoms don't hurt too much...

I love this place! Where else could you get all this friendly help at 4am?
Can I move in with y'all? 😀

Geoff
 
You are welcome to move in, as long as my little brother moves out at the same time 😛

Glad to know you have everything working! 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top