| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 45
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I had the exact same problem, and updating from 6.10.17 to 6.10.58 solved everything.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've got little doubt that the mere ''upgrading'' is enough to flush the [BOINC] DNS caches, but going to 6.10.58 is perfect. Makes support easier, for that's the code-base WCG knows intimately and was tested extensively. At that, 6.10.17 had a benchmark flaw... often way too low [which with the server 700 implementation is mostly ignored].
Crunch On --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The world of coincidence is too small. There were no mail list discussions, but this was checked in as a fix for the current developer client:
3111 David 27 Mar 2012 Quick look, one place the host IP address is stored is the client_state.xml, near the top. All my hosts have a router pre-assigned IP address i.e. the IP inside the LAN is always same. Anyone who's got random LAN IP addresses assigned to the devices who's had troubles? This IP address is known to WCG. I've got netinfo suppressed since a very long time which is why my computers appear with their numerical ID on the statistics pages which is why I never have duplicates whenever some mishap causes a new device to be registered at WCG. Just throwing out ideas if what this might cause. --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
3112 - scheduler: zero host.nsame_ip_addr if IP addr differs from previous
----------------------------------------Indeed that was the problem for me. I stopped the boinc service, axed the client-state* files restarted and almost immediately started getting workunits downloaded again. Sadly the IP address that had changed from the address which was recorded in these files wasn't even for the adapter that handles traffic for WCG. [Edit 1 times, last edit by Former Member at Mar 29, 2012 5:30:14 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for strengthening me in [my] confirmation bias. Dr. Spock Logic.
http://en.wikipedia.org/wiki/Confirmation_bias --//-- |
||
|
|
astrolabe.
Senior Cruncher Joined: May 9, 2011 Post Count: 496 Status: Offline |
Thanks for strengthening me in [my] confirmation bias. Dr. Spock Logic. Hence the oft used: Since you (the computer technician) were here yesterday, what did you do to make the dishwasher stop working? You must have changed something because it worked before you arrived!http://en.wikipedia.org/wiki/Confirmation_bias |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Are there members still encountering the download issue? If so please let me know.
There was an issue over the past weekend on the 25th where one of our download servers crashed. Most members were able to download from the redundant server. (I say most because apparently not all did, but stats about work unit flow were within range for the weekend). I was able to get another instance up and running for the download server and removed the bad ip from rotation in the dns round robin. Most of these issues should have cleared on their own within 24 hours but generally within 5 minutes depending on the dns server you use to get server addresses. If you are still having trouble, please try to go to "Start -> Run" then type in 'ipconfig /flushdns' and press ok. Thanks, -Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've been monitoring myWUs and my wingWUs on account of this thread covering the matter of cruncher-reported failure initially cruncher-associated with the WU-downloading_process. On myWUs: no issue.
On my wingWUs, after the uplinger [Mar 29, 2012 8:19:19 PM] post datime, I get only one wingWU with an error for a statusReport, which error may or may not have anything directly to do with the issue on hand: 1] SN2S_ AAW88545_ 0000000_ 0304_ 0-- 613 Error 3/29/12 22:25:25 3/29/12 22:25:46 0.00 0.0 / 0.0 2] SN2S_ AAW88545_ 0000000_ 0304_ 1-- 613 Error 3/29/12 22:25:24 3/29/12 22:32:31 0.00 131.8 / 0.0 Error report: 1] Result Name: SN2S_ AAW88545_ 0000000_ 0304_ 0-- <core_client_version>6.12.34</core_client_version> 2] Result Name: SN2S_ AAW88545_ 0000000_ 0304_ 1-- <core_client_version>6.10.17</core_client_version> <![CDATA[ <message> too many exit(0)s </message> ]]> Notes: a] I was expecting a TME ("too many exits") in wingWU#1 errorReport above, TME being the predominant stated errorExplanation I've been seeing lately from my wingWUs errorReport -- but there was no stated errorExplanation this time. b] BOINC_v6.10.17 is indicated as figuring in a majority of my wingWU's TME errorExplanation (days before the datime of the uplinger post). c] All times in none-DST utc. ; |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
1] Did not do anything, [no processing time logged] hence the empty log.
--//-- P.S. is the twice typed 'datime' a newly invented word? English use Date and other use Datum. The urban dict has "do da time" and "daytime". Oh, and 6.10.17 is an expired release counseled to be replaced soonest with 6.10.58. It's seen in an ueber-proportionate number of problem reports. |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
I agree with SekeRob, if you are running a version less than 6.10.58 as recommended on our site, then please update. There are multiple fixes involved with this as well as some security fixes.
Thanks, -Uplinger |
||
|
|
|