World Community Grid - View Thread - Reporting problem [RESOLVED]

World Community Grid Forums

Category: Support

Forum: Website Support

Thread: Reporting problem [RESOLVED]

Quick Go »

No member browsing this thread

Thread Status: Active
Total posts in this thread: 57

[ ]

Author

This topic has been viewed 4157 times and has 56 replies

motech
Cruncher
Joined: Mar 30, 2007
Post Count: 23
Status: Offline
Project Badges:

90 day badge for Human Proteome Folding - Phase 2

14 day badge for Discovering Dengue Drugs - Together

45 day badge for Nutritious Rice for the World

90 day badge for Help Fight Childhood Cancer

14 day badge for Influenza Antiviral Drug Search

90 day badge for Help Cure Muscular Dystrophy - Phase 2

180 day badge for The Clean Energy Project - Phase 2

90 day badge for Computing for Clean Water

90 day badge for Drug Search for Leishmaniasis

90 day badge for GO Fight Against Malaria

180 day badge for Uncovering Genome Mysteries

1 year badge for Outsmart Ebola Together

180 day badge for FightAIDS@Home - Phase 2

2 year badge for Microbiome Immunity Project

14 day badge for Africa Rainfall Project

5 year badge for OpenPandemics - COVID-19


Re: Reporting problem

Update: I have been able to report tasks but am now getting a "500 Internal Server Error" when trying to download new tasks.

[Jul 1, 2012 2:00:27 AM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

2012/07/01 08:31:59 | World Community Grid | Sending scheduler request: Requested by user.
2012/07/01 08:31:59 | World Community Grid | Reporting 1 completed tasks, requesting new tasks for CPU
2012/07/01 08:32:14 | World Community Grid | Scheduler request failed: HTTP internal server error

I have a dial-up connection.

I forwarded a failed scheduler request to Kevin.

Hope it will help.

[Jul 1, 2012 6:39:02 AM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

I have the same problem :(
нд, 01-лип-2012 09:58:35 +0300 | World Community Grid | Sending scheduler request: To report completed tasks.
нд, 01-лип-2012 09:58:35 +0300 | World Community Grid | Reporting 150 completed tasks, not requesting new tasks
нд, 01-лип-2012 09:59:17 +0300 | World Community Grid | Scheduler request failed: HTTP internal server error
Linux, BOINC 7.0.25

[Jul 1, 2012 7:06:06 AM]

B2I
Senior Cruncher
usa
Joined: Jan 23, 2011
Post Count: 232
Status: Offline
Project Badges:

10 year badge for Human Proteome Folding - Phase 2

5 year badge for Help Fight Childhood Cancer

2 year badge for Help Cure Muscular Dystrophy - Phase 2

14 day badge for Discovering Dengue Drugs - Together - Phase 2

50 year badge for The Clean Energy Project - Phase 2

2 year badge for Computing for Clean Water

5 year badge for Drug Search for Leishmaniasis

5 year badge for GO Fight Against Malaria

2 year badge for Computing for Sustainable Water

10 year badge for Mapping Cancer Markers

10 year badge for Uncovering Genome Mysteries

180 day badge for Outsmart Ebola Together

90 day badge for FightAIDS@Home - Phase 2

20 year badge for Microbiome Immunity Project

90 day badge for OpenPandemics - COVID-19


Re: Reporting problem

Out of 6 machines running I have two with this problem, one running Win 7 and one MINT 12. the only common denominator between the two is both the problem machines are using Hughesnet satellite system to connect to the internet. Here's a few lines from the Win 7 unit:

7/1/2012 6:23:29 AM | World Community Grid | Started upload of X0930064800115200603131616_0_0
7/1/2012 6:23:51 AM | World Community Grid | Finished upload of X0930064800115200603131616_0_0
7/1/2012 6:24:00 AM | World Community Grid | Scheduler request failed: HTTP internal server error
7/1/2012 6:24:01 AM | World Community Grid | Computation for task cfsw_6311_06311208_0 finished
7/1/2012 6:24:01 AM | World Community Grid | Starting task X0930064560487200602091101_1 using hcc1 version 642
7/1/2012 6:24:03 AM | World Community Grid | Started upload of cfsw_6311_06311208_0_0
7/1/2012 6:24:11 AM | World Community Grid | Finished upload of cfsw_6311_06311208_0_0
7/1/2012 6:25:31 AM | World Community Grid | Sending scheduler request: To report completed tasks.
7/1/2012 6:25:31 AM | World Community Grid | Reporting 372 completed tasks, requesting new tasks for CPU
7/1/2012 6:26:13 AM | World Community Grid | Scheduler request failed: HTTP internal server error
7/1/2012 6:29:05 AM | World Community Grid | Sending scheduler request: To report completed tasks.
7/1/2012 6:29:05 AM | World Community Grid | Reporting 372 completed tasks, requesting new tasks for CPU
7/1/2012 6:29:52 AM | World Community Grid | Scheduler request failed: HTTP internal server error
7/1/2012 6:32:32 AM | World Community Grid | Computation for task X0930064800471200603060942_1 finished
7/1/2012 6:32:32 AM | World Community Grid | Starting task X0930064560441200602091101_1 using hcc1 version 642
7/1/2012 6:32:34 AM | World Community Grid | Started upload of X0930064800471200603060942_1_0
7/1/2012 6:32:47 AM | World Community Grid | Finished upload of X0930064800471200603060942_1_0
7/1/2012 6:34:21 AM | World Community Grid | Sending scheduler request: To report completed tasks.
7/1/2012 6:34:21 AM | World Community Grid | Reporting 373 completed tasks, requesting new tasks for CPU
7/1/2012 6:35:03 AM | World Community Grid | Scheduler request failed: HTTP internal server error
7/1/2012 6:45:39 AM | World Community Grid | Sending scheduler request: To report completed tasks.
7/1/2012 6:45:39 AM | World Community Grid | Reporting 373 completed tasks, requesting new tasks for CPU
7/1/2012 6:46:21 AM | World Community Grid | Scheduler request failed: HTTP internal server error
7/1/2012 6:52:10 AM | World Community Grid | Computation for task X0930064720529200602241643_1 finished
7/1/2012 6:52:10 AM | World Community Grid | Starting task X0930064560433200602091101_0 using hcc1 version 642
7/1/2012 6:52:12 AM | World Community Grid | Started upload of X0930064720529200602241643_1_0
7/1/2012 6:52:24 AM | World Community Grid | Finished upload of X0930064720529200602241643_1_0
7/1/2012 6:56:41 AM | World Community Grid | Computation for task cfsw_6311_06311614_1 finished
7/1/2012 6:56:41 AM | World Community Grid | Starting task X0930064560412200602091102_0 using hcc1 version 642
7/1/2012 6:56:43 AM | World Community Grid | Started upload of cfsw_6311_06311614_1_0
7/1/2012 6:56:50 AM | World Community Grid | Computation for task X0930064561386200602031214_0 finished
7/1/2012 6:56:50 AM | World Community Grid | Starting task X0930064560155200602091106_1 using hcc1 version 642
7/1/2012 6:56:52 AM | World Community Grid | Started upload of X0930064561386200602031214_0_0
7/1/2012 6:56:53 AM | World Community Grid | Finished upload of cfsw_6311_06311614_1_0
7/1/2012 6:57:05 AM | World Community Grid | Finished upload of X0930064561386200602031214_0_0

----------------------------------------

[Jul 1, 2012 1:07:16 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

Ouch... 373 to upload.

Maybe another certificate info mangling [WCG the only one using https], but stepping through his expanded debug log indicates the CA part is all fine.

But for the one time I've reported in this thread [Linux], not had it. One W7-32 machine was booted twice in the past 72 hours and just connects fine. Router, not on UPS, has been booted many a time due the frequent power blips we have [grid overload at searing 40+C]. At any rate, lets fare on the trust that knreed will be able to root out something from the various sched. files that have been mailed to him, so he can correlate those to his server logs to trace the root cause back.

What I've noticed with him/hosting moving the GPFS file manager system is, that when navigating to the Result Status pages and clicking on the WU quorum detail link, these pages load faster than ever before... instant almost i.e. there is performance and service quality progress.

--//--

P.S. Just curious [random guess], if this line intended for proxies, would do something:

<http_1_0>1</http_1_0>

Add to <options> section of cc_config.xml, then read config in. (client restart makes sure it's taking effect).

There's 2 more lines for 6.12.27 and up:

<http_transfer_timeout>seconds</http_transfer_timeout>
    abort HTTP transfers if idle for this many seconds; default 300. New in 6.12.27 
<http_transfer_timeout_bps>bps</http_transfer_timeout_bps>
    an HTTP transfer is considered idle if its transfer rate is below this many bits per second. New in 6.12.27

Some parms to play. Docu:

http://boinc.berkeley.edu/trac/changeset/23579/boinc

[Jul 1, 2012 1:40:43 PM]

knreed
Former World Community Grid Tech
Joined: Nov 8, 2004
Post Count: 4504
Status: Offline
Project Badges:

180 day badge for Human Proteome Folding

45 day badge for Help Cure Muscular Dystrophy - Phase 2

14 day badge for Uncovering Genome Mysteries

45 day badge for Outsmart Ebola Together

1 year badge for Microbiome Immunity Project

1 year badge for Africa Rainfall Project

180 day badge for OpenPandemics - COVID-19


Re: Reporting problem

I have changed the scheduler back to being a regular cgi executable. People who are experiencing this issue, please try again and report your experiences.

[Jul 1, 2012 2:08:23 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

I have just send my copy of sched_request_www.worldcommunitygrid.org.xml .
As my 1st of 6 to report tasks has as deadline July 7th, I have good hope the problem will be solved in time for me.

Just wondering: I use a quite old Client 6.10.58. I assume that I better wait with upgrading to 7.0.28 till after the problem is solved, right?
I am afraid that upgrading while there is this communication problem (Scheduler request failed: HTTP internal server error), my results may get lost in the process.

Win 7, x64.

[Jul 1, 2012 2:14:43 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

I have at least a couple machines doing this... I use 8.8.8.8 (run by Google) for DNS, for what it's worth.
Here's the output from one (the one I'm posting this from, by the way) with work_fetch_debug and http_debug enabled...


Sun 01 Jul 2012 09:56:06 AM EDT	World Community Grid	Reporting 25 completed tasks, requesting new tasks
Sun 01 Jul 2012 09:56:06 AM EDT		[http_debug] HTTP_OP::init_post(): https://grid.worldcommunitygrid.org/boinc/wcg_cgi/fcgi
Sun 01 Jul 2012 09:56:14 AM EDT		[http_debug] [ID#1] Info:  About to connect() to grid.worldcommunitygrid.org port 443 (#0)
Sun 01 Jul 2012 09:56:14 AM EDT		[http_debug] [ID#1] Info:    Trying 198.20.8.241... 
Sun 01 Jul 2012 09:56:17 AM EDT		[http_debug] [ID#1] Info:  Connected to grid.worldcommunitygrid.org (198.20.8.241) port 443 (#0)
Sun 01 Jul 2012 09:56:17 AM EDT		[http_debug] [ID#1] Info:  Initializing NSS with certpath: /etc/pki/nssdb
Sun 01 Jul 2012 09:56:17 AM EDT		[http_debug] [ID#1] Info:    CAfile: /etc/pki/tls/certs/ca-bundle.crt
Sun 01 Jul 2012 09:56:17 AM EDT		[http_debug] [ID#1] Info:    CApath: none
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  SSL connection using SSL_RSA_WITH_3DES_EDE_CBC_SHA
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  Server certificate:
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  	subject: CN=*.worldcommunitygrid.org,O="Sea Blue, Inc",L=Jasper,ST=Georgia,C=US
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  	start date: Jun 23 00:00:00 2011 GMT
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  	expire date: Jun 22 23:59:59 2013 GMT
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  	common name: *.worldcommunitygrid.org
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Info:  	issuer: CN=Thawte SSL CA,O="Thawte, Inc.",C=US
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: POST /boinc/wcg_cgi/fcgi HTTP/1.1
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: User-Agent: BOINC client (i686-pc-linux-gnu 6.10.45)
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: Host: grid.worldcommunitygrid.org
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: Accept: */*
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: Content-Length: 93409
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: Expect: 100-continue
Sun 01 Jul 2012 09:56:21 AM EDT		[http_debug] [ID#1] Sent header to server: 
Sun 01 Jul 2012 09:56:22 AM EDT		[http_debug] [ID#1] Info:  Done waiting for 100-continue
Sun 01 Jul 2012 09:56:24 AM EDT		[http_debug] [ID#1] Received header from server: HTTP/1.1 100 Continue
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: HTTP/1.1 500 Internal Server Error
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: Date: Sun, 01 Jul 2012 13:56:27 GMT
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: Server: IBM_HTTP_Server
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: Content-Length: 550
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: Connection: close
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: Content-Type: text/html; charset=iso-8859-1
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Received header from server: 
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Info:  Expire cleared
Sun 01 Jul 2012 09:56:56 AM EDT		[http_debug] [ID#1] Info:  Closing connection #0
Sun 01 Jul 2012 09:57:01 AM EDT	World Community Grid	Scheduler request failed: HTTP internal server error
Sun 01 Jul 2012 09:57:01 AM EDT		[wfd] Request work fetch: RPC complete
Sun 01 Jul 2012 09:57:06 AM EDT		[wfd]: work fetch start
Sun 01 Jul 2012 09:57:06 AM EDT		[wfd] ------- start work fetch state -------
Sun 01 Jul 2012 09:57:06 AM EDT		[wfd] target work buffer: 12960.00 + 64800.00 sec
Sun 01 Jul 2012 09:57:06 AM EDT		[wfd] CPU: shortfall 155520.00 nidle 2.00 saturated 0.00 busy 0.00 RS fetchable 0.00 runnable 0.00
Sun 01 Jul 2012 09:57:06 AM EDT	World Community Grid	[wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
Sun 01 Jul 2012 09:57:06 AM EDT	World Community Grid	[wfd] overall LTD 0.00
Sun 01 Jul 2012 09:57:06 AM EDT		[wfd] ------- end work fetch state -------

Hope that helps.

[Jul 1, 2012 2:17:06 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

First time upgrade from 6 to *latest* 7 could turn out poof [though from recollection that was supposed to have been fixed when that started happening with early 7.0.xx versions. Depleting buffer first is the safest route.

Going back from 7 to 6, no doubt, you'll see your cache emptying, and later maybe get some, not all "lost results recovered".

But for now, don't bother... 7.0.30 is out and 7.0.31 is already in the pipeline, and who knows will a 7.0.xx build get additional work fetch messaging. Put in a request for that on 4 conditions. Summary: Just wait, best wait till WCG says it's good to go, unless you must, for none WCG related reasons.

--//--

[Jul 1, 2012 2:23:16 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Reporting problem

This in reply to: knreed [Jul 1, 2012 2:08:23 PM]

That seems to have solved the problem, at least for me.
My 6 tasks have now been reported as usual - and fast.

Thanks a lot!

----------------------------------------
[Edit 1 times, last edit by Former Member at Jul 1, 2012 2:36:01 PM]

[Jul 1, 2012 2:30:42 PM]

[ ]