| 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: 14
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
...others can learn from this. I'd like to, but...A week ago my FAAH result couldn't upload. I was surprised not to see any similar news on the forum, but well, we can wait... Past few days I was waiting for any related message to pop up, until now: Since 9.4.2008 my client is not able to upload to WCG (actually no cheduler communication with WCG), any other project can be communicated fine: 16.04.2008 15:20:48|| Resuming network activity 16.04.2008 15:20:48|WCG| Started upload of faah3415_ZINC01561939_xMut_md02130_00_1_0 16.04.2008 15:20:48|WCG| Started upload of faah3415_ZINC01561939_xMut_md02130_00_1_1 16.04.2008 15:20:50|| Project communication failed: attempting access to reference site 16.04.2008 15:20:50|WCG| Temporarily failed upload of faah3415_ZINC01561939_xMut_md02130_00_1_0: http error 16.04.2008 15:20:50|WCG| Backing off 1 hr 27 min 53 sec on upload of faah3415_ZINC01561939_xMut_md02130_00_1_0 16.04.2008 15:20:50|WCG| Temporarily failed upload of faah3415_ZINC01561939_xMut_md02130_00_1_1: http error 16.04.2008 15:20:50|WCG| Backing off 3 hr 56 min 35 sec on upload of faah3415_ZINC01561939_xMut_md02130_00_1_1 16.04.2008 15:20:51|| Access to reference site succeeded - project servers may be temporarily down. 16.04.2008 15:21:04|WCG| [sched_op_debug] Starting scheduler request 16.04.2008 15:21:04|WCG| Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 16.04.2008 15:21:05|| Project communication failed: attempting access to reference site 16.04.2008 15:21:06|| Access to reference site succeeded - project servers may be temporarily down. 16.04.2008 15:21:09|WCG| Scheduler request failed: Unsupported protocol 16.04.2008 15:21:09|WCG| [sched_op_debug] Deferring communication for 1 min 0 sec 16.04.2008 15:21:09|WCG| [sched_op_debug] Reason: scheduler request failed 16.04.2008 15:22:16|WCG| [sched_op_debug] Fetching master file 16.04.2008 15:22:16|WCG| Fetching scheduler list 16.04.2008 15:22:21|WCG| [sched_op_debug] Got master file; parsing 16.04.2008 15:22:21|WCG| [sched_op_debug] Found 1 scheduler URLs in master file 16.04.2008 15:22:21|WCG| Master file download succeeded 16.04.2008 15:23:14|WCG| [sched_op_debug] Starting scheduler request 16.04.2008 15:23:14|WCG| Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 16.04.2008 15:23:15|| Project communication failed: attempting access to reference site 16.04.2008 15:23:16|| Access to reference site succeeded - project servers may be temporarily down. 16.04.2008 15:23:19|WCG| Scheduler request failed: Unsupported protocol 16.04.2008 15:23:19|WCG| [sched_op_debug] Deferring communication for 1 min 0 sec 16.04.2008 15:23:19|WCG| [sched_op_debug] Reason: scheduler request failed 16.04.2008 15:23:35|| Suspending network activity - user request During these 2-3 minutes, additional 8-9 projects were successfully contacted. I'm contacting the project servers over two different networks at diferent times of day, but just WCG is unavailable for me. Maybe I should try to look for any garbage in Boinc XML files? (Using WinXP client 5.10.45 - ahaaaa, it is self compiled client with self compiled libcurl.dll, this could be the culprit... Maybe I did indeed learn something :-) But still makes me wondering, why just WCG refuses to communicate with my client? I've tried to restore the original Boinc executable and dll - no, my version was not the fault, still WCG is the only project scheduler, which refuses to communicate: 16-Apr-2008 16:14:00|WCG| [sched_op_debug] Starting scheduler request 16-Apr-2008 16:14:01|WCG| Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 16-Apr-2008 16:14:06|WCG| Scheduler request failed: Failure when receiving data from the peer 16-Apr-2008 16:14:06|WCG| [sched_op_debug] Deferring communication for 1 min 0 sec 16-Apr-2008 16:14:06|WCG| [sched_op_debug] Reason: scheduler request failed Anyone an idea? [Edit 1 times, last edit by Former Member at Apr 16, 2008 2:26:19 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, you have compiled libcurl without SSL support. Simple.
This line shows the error: 16.04.2008 15:23:19|WCG| Scheduler request failed: Unsupported protocol Using the official client, it looks like your proxy settings are still wrong. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, you have compiled libcurl without SSL support. Simple. This line shows the error: 16.04.2008 15:23:19|WCG| Scheduler request failed: Unsupported protocol Simple as it is, this is most probably true. Thanks, David! (To reply my own question "But still makes me wondering, why just WCG refuses to communicate with my client?" - in contrary to (most of) other projects, WCG apparently communicates over SSL.) Using the official client, it looks like your proxy settings are still wrong. Right, adding <force_auth>basic</force_auth> did the job (I'm now behind an auth proxy). Thanks again. I've indeed learned my lesson From testing the 5.10.40 I've remembered "I did not need to set the <force_ntlm> flag". BUT later it got renamed to (optional) <force_auth>, which I've probably had to set for WCG back then ![]() |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Well.... what does one do when the taught is forgotten
----------------------------------------![]() (just added 2 more questions to ask to my checklist for the future like....'do you / did you use your computer in multiple places for instance at home & work & school & lanparty?)
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|