Message boards : Questions and problems : Problem uploading results
Message board moderation
Author | Message |
---|---|
Send message Joined: 10 Jun 09 Posts: 3 ![]() |
Hi, I've recently installed BOINC on my computer at work, but I don't seem to be able to upload any of my results. I have ~ 20 tasks which are "uploading", however in my "transfers" list they are all above 0% (some at 100%), but are listed as "retry in xx:xx". I've had BOINC running on this machine for a couple of weeks, and I'm pretty sure I've never been able to successfully upload any work units from it. It's running Windows XP and BOINC 6.6.28. If I go to http://srv4.bakerlab.org/rosetta_cgi/file_upload_handler from Firefox it seems to work, I get <data_server_reply> <status>-1</status> <message>no command</message> </data_server_reply> so it at least seems that I can reach the server. I've turned on debugging and here's the output: 6/10/2009 11:25:41 AM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle 'D:\apps\BOINC\ca-bundle.crt' 6/10/2009 11:25:41 AM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle set 6/10/2009 11:25:41 AM [proxy_debug] HTTP_OP::no_proxy_for_url(): http://srv4.bakerlab.org/rosetta_cgi/file_upload_handler 6/10/2009 11:25:41 AM [proxy_debug] returning false 6/10/2009 11:25:41 AM [proxy_debug]: setting up proxy www-proxy.cse.unsw.edu.au:3128 6/10/2009 11:25:41 AM rosetta@home Started upload of lb_dk_ksync__full_hb_t363__IGNORE_THE_REST_12661_4148_0_0 6/10/2009 11:25:41 AM [http_debug] [ID#33] info: timeout on name lookup is not supported 6/10/2009 11:25:41 AM [http_debug] [ID#33] info: About to connect() to proxy www-proxy.cse.unsw.edu.au port 3128 (#0) 6/10/2009 11:25:41 AM [http_debug] [ID#33] info: Trying 129.94.242.47... 6/10/2009 11:25:41 AM [http_debug] [ID#33] info: Connected to www-proxy.cse.unsw.edu.au (129.94.242.47) port 3128 (#0) 6/10/2009 11:25:41 AM [http_debug] [ID#33] Sent header to server: POST http://srv4.bakerlab.org/rosetta_cgi/file_upload_handler HTTP/1.1 User-Agent: BOINC client (windows_intelx86 6.6.28) Host: srv4.bakerlab.org Accept: */* Accept-Encoding: deflate, gzip Proxy-Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded Content-Length: 310 6/10/2009 11:25:42 AM [http_debug] [ID#33] info: HTTP 1.0, assume close after body 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: HTTP/1.0 200 OK 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: Date: Wed, 10 Jun 2009 01:28:25 GMT 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: Server: Apache/2.2.3 (Red Hat) 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: Content-Type: text/plain; charset=UTF-8 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: X-Cache: MISS from score.orchestra.cse.unsw.EDU.AU 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: X-Cache-Lookup: MISS from score.orchestra.cse.unsw.EDU.AU:3128 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: Proxy-Connection: close 6/10/2009 11:25:42 AM [http_debug] [ID#33] Received header from server: 6/10/2009 11:25:42 AM [http_xfer_debug] HTTP: wrote 93 bytes 6/10/2009 11:25:42 AM [http_debug] [ID#33] info: Expire cleared 6/10/2009 11:25:42 AM [http_debug] [ID#33] info: Closing connection #0 6/10/2009 11:25:42 AM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle set 6/10/2009 11:25:42 AM [proxy_debug] HTTP_OP::no_proxy_for_url(): http://srv4.bakerlab.org/rosetta_cgi/file_upload_handler 6/10/2009 11:25:42 AM [proxy_debug] returning false 6/10/2009 11:25:42 AM [proxy_debug]: setting up proxy www-proxy.cse.unsw.edu.au:3128 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: timeout on name lookup is not supported 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: About to connect() to proxy www-proxy.cse.unsw.edu.au port 3128 (#0) 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: Trying 129.94.242.47... 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: Connected to www-proxy.cse.unsw.edu.au (129.94.242.47) port 3128 (#0) 6/10/2009 11:25:42 AM [http_debug] [ID#34] Sent header to server: POST http://srv4.bakerlab.org/rosetta_cgi/file_upload_handler HTTP/1.1 User-Agent: BOINC client (windows_intelx86 6.6.28) Host: srv4.bakerlab.org Accept: */* Accept-Encoding: deflate, gzip Proxy-Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded Content-Length: 105521 Expect: 100-continue 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: Expire cleared 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: HTTP 1.0, assume close after body 6/10/2009 11:25:42 AM [http_debug] [ID#34] Received header from server: HTTP/1.0 100 Continue 6/10/2009 11:25:42 AM [http_debug] [ID#34] Received header from server: X-Cache: MISS from score.orchestra.cse.unsw.EDU.AU 6/10/2009 11:25:42 AM [http_debug] [ID#34] Received header from server: X-Cache-Lookup: MISS from score.orchestra.cse.unsw.EDU.AU:3128 6/10/2009 11:25:42 AM [http_debug] [ID#34] info: HTTP/1.0 proxy connection set to keep alive! 6/10/2009 11:25:42 AM [http_debug] [ID#34] Received header from server: Proxy-Connection: keep-alive 6/10/2009 11:26:42 AM [http_debug] [ID#34] info: Expire cleared 6/10/2009 11:26:42 AM [http_debug] [ID#34] info: Empty reply from server 6/10/2009 11:26:42 AM [http_debug] [ID#34] info: Connection #0 to host www-proxy.cse.unsw.edu.au left intact 6/10/2009 11:26:42 AM [http_debug] HTTP error: Server returned nothing (no headers, no data) 6/10/2009 11:26:43 AM Project communication failed: attempting access to reference site 6/10/2009 11:26:43 AM [http_debug] HTTP_OP::init_get(): http://www.google.com/ 6/10/2009 11:26:43 AM [http_debug] HTTP_OP::libcurl_exec(): ca-bundle set 6/10/2009 11:26:43 AM [proxy_debug] HTTP_OP::no_proxy_for_url(): http://www.google.com/ 6/10/2009 11:26:43 AM [proxy_debug] returning false 6/10/2009 11:26:43 AM [proxy_debug]: setting up proxy www-proxy.cse.unsw.edu.au:3128 6/10/2009 11:26:43 AM rosetta@home Temporarily failed upload of lb_dk_ksync__full_hb_t363__IGNORE_THE_REST_12661_4148_0_0: HTTP error 6/10/2009 11:26:43 AM rosetta@home Backing off 2 hr 39 min 31 sec on upload of lb_dk_ksync__full_hb_t363__IGNORE_THE_REST_12661_4148_0_0 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Connection #0 seems to be dead! 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Closing connection #0 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: timeout on name lookup is not supported 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: About to connect() to proxy www-proxy.cse.unsw.edu.au port 3128 (#0) 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Trying 129.94.242.47... 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Connected to www-proxy.cse.unsw.edu.au (129.94.242.47) port 3128 (#0) 6/10/2009 11:26:43 AM [http_debug] [ID#35] Sent header to server: GET http://www.google.com/ HTTP/1.1 User-Agent: BOINC client (windows_intelx86 6.6.28) Host: www.google.com Accept: */* Accept-Encoding: deflate, gzip Proxy-Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: HTTP 1.0, assume close after body 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: HTTP/1.0 302 Moved Temporarily 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Location: http://www.google.com.au/ 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Cache-Control: private 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Content-Type: text/html; charset=UTF-8 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Date: Wed, 10 Jun 2009 01:26:45 GMT 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Server: gws 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Content-Length: 222 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Set-Cookie: PREF=ID=e75eb6b5e11eeb22:TM=1244597205:LM=1244597205:S=mV9m5g1E2s32XTF_; expires=Fri, 10-Jun-2011 01:26:45 GMT; path=/; domain=.google.com 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: X-Cache: MISS from score.orchestra.cse.unsw.EDU.AU 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: X-Cache-Lookup: MISS from score.orchestra.cse.unsw.EDU.AU:3128 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: HTTP/1.0 proxy connection set to keep alive! 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Proxy-Connection: keep-alive 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Ignoring the response-body 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Expire cleared 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Connection #0 to host www-proxy.cse.unsw.edu.au left intact 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Issue another request to this URL: 'http://www.google.com.au/' 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Re-using existing connection! (#0) with host www-proxy.cse.unsw.edu.au 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Connected to www-proxy.cse.unsw.edu.au (129.94.242.47) port 3128 (#0) 6/10/2009 11:26:43 AM [http_debug] [ID#35] Sent header to server: GET http://www.google.com.au/ HTTP/1.0 User-Agent: BOINC client (windows_intelx86 6.6.28) Host: www.google.com.au Accept: */* Accept-Encoding: deflate, gzip Referer: http://www.google.com/ Proxy-Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: HTTP 1.0, assume close after body 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: HTTP/1.0 200 OK 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Cache-Control: private, max-age=0 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Date: Wed, 10 Jun 2009 01:26:45 GMT 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Expires: -1 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Content-Type: text/html; charset=ISO-8859-1 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Server: gws 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Set-Cookie: PREF=ID=c03796a13ad57dfa:TM=1244597205:LM=1244597205:S=yLCHlYaNRZuB52YS; expires=Fri, 10-Jun-2011 01:26:45 GMT; path=/; domain=.google.com.au 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: X-Cache: MISS from score.orchestra.cse.unsw.EDU.AU 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: X-Cache-Lookup: MISS from score.orchestra.cse.unsw.EDU.AU:3128 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: Proxy-Connection: close 6/10/2009 11:26:43 AM [http_debug] [ID#35] Received header from server: 6/10/2009 11:26:43 AM [http_xfer_debug] HTTP: wrote 1112 bytes 6/10/2009 11:26:43 AM [http_xfer_debug] HTTP: wrote 1460 bytes 6/10/2009 11:26:43 AM [http_xfer_debug] HTTP: wrote 1460 bytes 6/10/2009 11:26:43 AM [http_xfer_debug] HTTP: wrote 1125 bytes 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Expire cleared 6/10/2009 11:26:43 AM [http_debug] [ID#35] info: Closing connection #0 6/10/2009 11:26:44 AM Internet access OK - project servers may be temporarily down. I get similar results for seti@home, and have done for the last few weeks so I don't think it's just a transient issue. Any ideas as to what's going on? Cheers, - Rob |
![]() Send message Joined: 29 Aug 05 Posts: 15625 ![]() |
Are you allowed to run BOINC at work? Did you ask your boss or the IT people for permission? If you did and you got their permission, you have to ask the IT people what changed in the proxy or firewall. When you do not have permission, we can't help you any further. The first rule of using BOINC is to use it on computers you own or that you have permission for to use. |
Send message Joined: 10 Jun 09 Posts: 3 ![]() |
Yeah I'm allowed to run BOINC on my machine, and the IT guys are friendly so they'll probably help me set it up. What firewall settings does BOINC need to be able to run? I thought it did all of its communication through HTTP / POST, which shouldn't be blocked. Also it seems I can at least connect to the sites as the uploads are starting, they just never actually complete ... |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
That's quite strange. If POSTs weren't getting through, you wouldn't have been able to get work either. I think the problem is the presence of extra headers after the 100 Continue. |
![]() Send message Joined: 20 Dec 07 Posts: 1069 ![]() |
You could try switching from htt protocol version 1.1 to version 1.0. To do so, you must create a text file named cc_config.xml in your BOINC data directory (if it doesn't exist already). The data directory is mentioned in the message tab of BOINC manager. With a texteditor, enter (copy&paste) the following into that file: <cc_config> <options> <http_1_0>1</http_1_0> </options> </cc_config>There are no lower case 'L' characters in that code, only digits '1'. More information to cc_config you can find here. In BOINC Manager (Advanced view) select menu 'Advanced->Read config file' to activate the new configuration. Hope that helps. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
I thought he already had that because I saw HTTP1.0 mentioned in his log; but you're right. That will help. HTTP/1.0 didn't have "100 Continue" at all. |
Send message Joined: 14 Jun 09 Posts: 6 ![]() |
I've just had the same problem, but don't know how to debug it. I've run projects all the way to 100% for SETI, MilkyWay and Rosetta. All of them sat on "Uploading" for hours and never uploading anything, I'm running Mac OS X. Here's a link to one of the jobs. The first one on this list went to 100% and never uploaded. http://milkyway.cs.rpi.edu/milkyway/results.php?userid=46415 Thanks, Scott |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
I've just had the same problem, but don't know how to debug it. You may want to try Gundolf's suggestion. Here's a link to one of the jobs. The first one on this list went to 100% and never uploaded. That task expired from MilkyWay database already. |
Send message Joined: 14 Jun 09 Posts: 6 ![]() |
Thanks!!! It worked. http://milkyway.cs.rpi.edu/milkyway/results.php?userid=46415 I did everything indicated in Gundolf's suggestion, but a couple obvious questions: I'm running a brand new mac iBook. Why doesn't this software just run and talk back to the server automatically when it's ready to upload results? I understand it might be easier said than done, but come on. For one, I didn't there was no "data" directory created for the BOINC app. I do some programming for my job, so I am used to work-arounds and hacks, but how could this platform ever make it to 'casual' users if it doesn't work like a turn-key app? ANyway, today's my first day, so I'm sure I've missed a lot of conversation and reasons for the way things are. But my first impression is, "how many people have downloaded it, failed to upload results, and therefore did not get 'credit' and then stopped using?" Thanks again. Looking forward to seeing more of the projects moving forward. It's really cool. Scott |
![]() Send message Joined: 29 Aug 05 Posts: 15625 ![]() |
I'm running a brand new mac iBook. Why doesn't this software just run and talk back to the server automatically when it's ready to upload results? I understand it might be easier said than done, but come on. Normally Internet Service Providers (ISPs) use HTTP 1.1 for their communications. Some run an incorrect or incomplete implementation of HHTP 1.1, whereby falling back to HTTP 1.0 is the only way to get communications done. To translate that to BOINC, you have to use its cc_config.xml (core client configuration) file for the 'special' options. It's not found under a drop-down menu in the GUI as its use is for the (normally) advanced and debug people only. |
Send message Joined: 25 Nov 05 Posts: 1654 ![]() |
Scott wrote: But my first impression is, "how many people have downloaded it, failed to upload results, and therefore did not get 'credit' and then stopped using?" Probably quite a few, if they didn't bother to ask what was wrong. And most of the time it's something that THEY're doing wrongly. But the number of people who download, run, attach, and have no problems at all is far greater. The word "huge" might be a suitable descriptor for this group. |
Send message Joined: 25 Nov 05 Posts: 1654 ![]() |
There are 2 different parts to this: 1) Getting everything set up and working in the first place 2) Eventually getting bored with it and dropping out Decades ago, I read somewhere that hobbies generally only last about 3 years before people move on to something else. |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
|
Send message Joined: 10 Jun 09 Posts: 3 ![]() |
I too thought that I was using HTTP 1.0 from the log, but applying that setting in my cc_config.xml file has done the trick. Thanks! |
Send message Joined: 31 Jul 09 Posts: 1 ![]() |
Hmmm, is there another remedy for uploads than switching to http protocol version 1.0? I changed my cc_config.xml file accordingly, but there was no success, even rebooting didn't help. Oh, the problem is that I cannot upload files - boinc starts uploads but transfers only tiny pieces of the files and then tries the next file. Last time there were 25 files for WCG and 4 files for GPUGRID. If new WUs are requested the download succeeds immediately but upload retries and retries... (It succeeds sometimes, but if 1-2 files are uploaded per day the result files are generated too fast to keep pace) This happens with Boinc 6.6.36 (64-bit) on Intel i7 (920) with Vista home premium 64 bit. Then I copied all files to an existing boinc 5.10.45 (32-bit) installation and all files were uploaded and reported successfully immediately after I started it (on the same computer), so it should not be a general network issue unless 6.6.36 handles the connection more strictly. So I can process all WUs with 6.6.36, then copy the result files to 5.10.45, upload them, copy the changed project files to 6.6.36, download new WUs, process them etc... But this is not very satisfying, so I'd be glad to have another way to get 6.6.36 to upload all files itself. And i need it because of GPU working... Any ideas? Or did I miss the posting with a solution? Thanks! Matthias |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.