Folding Forum

I used the recommendations I was given when I set v7 up over 2 years ago. This machine is setup for SMP folding and has worked fine for all that time. The only thing that has changed is that I moved about 4 months ago and am now too far from the CO to get better than 256k uplink speed. Things have b...

I suspected that was at play here but could not find that little gem of information anywhere on the forum. Thre are multiple issues going on here. The situation had snowballed into 8 WUs trying to upload and failing simultaneously as you can see from this excerpt showing WU01 failing midway through ...

Looking through the threads I see that this problem has been reported on a couple different servers in the last few months. I have 8 27MB WUs stacked up here that the client has tried over 20 times each to upload getting 1/4 to 1/2 done before failing. 05:10:31:WU03:FS00:Upload 6.05% 05:10:37:WU08:F...

I look forward to the new client. I knew that the getaddress request returned IPv6 then IPv4 but I did not know you could specifically request just IPv4.

The fah client can upload completed WU's and download new WU's because the assigment servers do not have IPv6 addresses. ; <<>> DiG 9.8.1-P1 <<>> aaaa assign3.stanford.edu ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28411 ;; flags: qr rd ra; QUERY: 1, A...

No the client fails still to retrieve a core. It finished the WU, downloaded a new WU and uploaded the finished WU but if I move the core file forcing the client to retrieve it again that fails. Looking at the network with Wireshark I see no activity from the client after the DNS request so the clie...

Point taken.

Thank You to whoever got this taken care of.

I was not looking forward to shutting down my IPv6 connectivity every time fah wanted to phone home.

I don't think anyone suggested disabling IPv6 at all of Stanford, just on that one donor's computer having this "minor" issue. It wouldn't be minor to me if it prevented me from folding... :twisted: You must know some people in high places 7im, it seems that http://www.stanford.edu now ha...

Stanford is not likely to disable IPv6 for the entire campus just because of a minor problem with one server. They're more likely to find and fix the underlying problem. The underlying problem is that the DNS records tell the world that http://www.stanford.edu is at 2607:f6d0:0:925a::ab43:d7c8. but...

And where is the OS IPv6 failover functionality to IPv4?. I would have to see the code to see exactly what the error message means. ERROR:WU00:FS00:Exception: Failed to connect to www.stanford.edu:80: The requested address is not valid in its context. Actually looks like the code may be confused by...

Kind of a head in the sand fix isn't it? Talk to Microsoft. Not a fah problem. I run Linux and have been struggling with installation of the V7 client and this is the last stumbling block. http://www.stanford.edu is CNAMEd to www-v6.stanford.edu which has an IPv6 address. MOST Linux distros give IP...

Kind of a head in the sand fix isn't it?

I seem to be missing credit for the following WU's. I fold for the cause but it is still fun to watch the credits build. At the same time I can sympathize with a server issue of this magnitude. Best of luck to all. Project: 7153 December 11 02:05:38 UTC Connecting to http://128.143.199.96:8080/ Proj...