http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500

Author	Message
Andrea Piccioni Send message Joined: 17 Jun 99 Posts: 8 Credit: 558,381 RAC: 1	Message 241484 - Posted: 3 Feb 2006, 13:22:54 UTC Hi, I have updated my Boinc to release 5.2.13 (on windows xp professional) Now I'm unable to upload completed work and download new works. Message reported by boinc are: 03/02/2006 14.19.05\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 03/02/2006 14.19.05\|SETI@home\|No schedulers responded Who can help me? Thanks ID: 241484 ·

Andrea Piccioni Send message Joined: 17 Jun 99 Posts: 8 Credit: 558,381 RAC: 1	Message 241563 - Posted: 3 Feb 2006, 17:19:26 UTC Other info I'm using HTTP proxy on port 8080 I'm using domain user and password The past release has no problem. The complete log messages are: 03/02/2006 16.08.01\|\|Starting BOINC client version 5.2.13 for windows_intelx86 03/02/2006 16.08.01\|\|libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3 03/02/2006 16.08.01\|\|Executing as a daemon 03/02/2006 16.08.01\|\|Data directory: C:\\Program Files\\BOINC 03/02/2006 16.08.01\|\|BOINC is running as a service and as a non-system user. 03/02/2006 16.08.01\|\|No application graphics will be available. 03/02/2006 16.08.02\|\|Processor: 2 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz 03/02/2006 16.08.02\|\|Memory: 1.98 GB physical, 3.82 GB virtual 03/02/2006 16.08.02\|\|Disk: 76.69 GB total, 6.64 GB free 03/02/2006 16.08.02\|SETI@home\|Computer ID: 1547529; location: work; project prefs: default 03/02/2006 16.08.02\|\|General prefs: from SETI@home (last modified 2005-10-19 14:23:06) 03/02/2006 16.08.02\|\|General prefs: no separate prefs for work; using your defaults 03/02/2006 16.08.03\|\|Remote control not allowed; using loopback address 03/02/2006 16.31.28\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 03/02/2006 16.31.28\|SETI@home\|Reason: Requested by user 03/02/2006 16.31.28\|SETI@home\|Requesting 17280 seconds of new work 03/02/2006 16.31.33\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 03/02/2006 16.31.33\|SETI@home\|No schedulers responded 03/02/2006 16.39.16\|SETI@home\|Started upload of 28fe05ab.24354.25602.779818.1.59_2_0 03/02/2006 16.39.19\|SETI@home\|Temporarily failed upload of 28fe05ab.24354.25602.779818.1.59_2_0: error 500 03/02/2006 16.39.19\|SETI@home\|Backing off 4 minutes and 23 seconds on upload of file 28fe05ab.24354.25602.779818.1.59_2_0 03/02/2006 16.43.43\|SETI@home\|Started upload of 28fe05ab.24354.25602.779818.1.59_2_0 03/02/2006 16.43.47\|SETI@home\|Temporarily failed upload of 28fe05ab.24354.25602.779818.1.59_2_0: error 500 03/02/2006 16.43.47\|SETI@home\|Backing off 3 hours, 8 minutes, and 9 seconds on upload of file 28fe05ab.24354.25602.779818.1.59_2_0 03/02/2006 18.15.38\|SETI@home\|Started upload of 14ap04aa.23664.11601.617326.1.94_3_0 03/02/2006 18.15.41\|SETI@home\|Temporarily failed upload of 14ap04aa.23664.11601.617326.1.94_3_0: error 500 03/02/2006 18.15.41\|SETI@home\|Backing off 1 hours, 56 minutes, and 36 seconds on upload of file 14ap04aa.23664.11601.617326.1.94_3_0 03/02/2006 18.17.05\|SETI@home\|Started upload of 28fe05ab.24354.25602.779818.1.59_2_0 03/02/2006 18.17.09\|SETI@home\|Temporarily failed upload of 28fe05ab.24354.25602.779818.1.59_2_0: error 500 03/02/2006 18.17.09\|SETI@home\|Backing off 3 hours, 40 minutes, and 55 seconds on upload of file 28fe05ab.24354.25602.779818.1.59_2_0 ID: 241563 ·

dmbott Send message Joined: 15 Mar 00 Posts: 9 Credit: 116,795 RAC: 0	Message 241592 - Posted: 3 Feb 2006, 18:21:31 UTC Last modified: 3 Feb 2006, 18:22:05 UTC After reading several other threads addressing similar problems, I found an answer for me that worked like a charm for ALL my computers: Windows 2000 Professional and Windows XP Professional: MS Knowledgebase article See Solution 1 Essentially the problem seems to be with a "black hole router" somewhere between my computers and the setiathome server. The three solutions include 1) a simple registry edit, 2) asking the router to be changed, or 3) limiting all packet sizes with a universal MTU size that will pass through the black hole router. Of these, the first is simplest and best. Solution 1: 1. Start Registry Editor (Regedit.exe). 2. Locate the following key in the registry: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\tcpip\\parameters 3. On the Edit menu, click Add Value, and then add the following registry value: Value Name: EnablePMTUBHDetect Data Type: REG_DWORD Value: 1 4. Quit Registry Editor, and then restart the computer. Here's the description from the Microsoft Knowledgebase: "On a TCP/IP-based wide area network (WAN), communication over some routes may fail if an intermediate network segment has a maximum packet size that is smaller than the maximum packet size of the communicating hosts--and if the router does not send an appropriate Internet Control Message Protocol (ICMP) response to this condition or if a firewall on the path drops such a response. Such a router is sometimes known as a "black hole" router. You can locate a black hole router by using the Ping utility, which is a standard utility that is installed with the Microsoft Windows TCP/IP protocol. You can then use one of three methods of fixing or working around black hole routers. When a network router receives a packet that is larger than the size of the Maximum Transmission Unit (MTU) of the next segment of a communications network, and that packet's IP layer "don't fragment" bit is flagged, the router is expected to send an ICMP "destination unreachable" message back to the sending host. If the router does not send a message, the packet might be dropped, causing a variety of errors that vary with the program that is communicating over the unsuccessful link. (These errors do not occur if a program connects to a computer on a local subnet.) The behavior may seem intermittent, but closer examination shows that the behavior can be reproduced, for example, by having a client read a large file that is sent from a remote host. " There were a few -106 errors when the SetiatHome servers were actually down, but then all clients were able to report finished workunits and download new ones! Yippee! ID: 241592 ·

Andrea Piccioni Send message Joined: 17 Jun 99 Posts: 8 Credit: 558,381 RAC: 1	Message 243577 - Posted: 6 Feb 2006, 13:10:58 UTC - in response to Message 241592. Thank you very much for the infomations. I' am in windows domain with active directory then I ask to my system administrator. For now I try to reinstall the old version of boinc. ID: 243577 ·

Andrea Piccioni Send message Joined: 17 Jun 99 Posts: 8 Credit: 558,381 RAC: 1	Message 243599 - Posted: 6 Feb 2006, 15:13:58 UTC - in response to Message 243577. I'have tried to install old version but it doesn't work because there are conflict between version. I'have reinstalled the new version but in configuration shared installation (not service) and the message has changed (but it doesent work). Please somebody Help me... Here the new messages: 06/02/2006 14.22.10\|\|Starting BOINC client version 4.45 for windows_intelx86 06/02/2006 14.22.10\|\|Data directory: C:\\Program Files\\BOINC 06/02/2006 14.22.10\|SETI@home\|Computer ID: 1547529; location: work; project prefs: default 06/02/2006 14.22.10\|\|General prefs: from SETI@home (last modified 2005-10-19 14:23:06) 06/02/2006 14.22.10\|\|General prefs: no separate prefs for work; using your defaults 06/02/2006 14.22.10\|\|Remote control not allowed; using loopback address 06/02/2006 14.22.10\|\|Insufficient work; requesting more 06/02/2006 14.22.10\|SETI@home\|Deferring communication with project for 1 hours, 16 minutes, and 25 seconds 06/02/2006 14.24.40\|\|request_reschedule_cpus: project op 06/02/2006 14.24.40\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 06/02/2006 14.24.40\|SETI@home\|Requesting 17280 seconds of work, returning 0 results 06/02/2006 14.24.42\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded 06/02/2006 14.24.42\|SETI@home\|No work from project 06/02/2006 14.24.43\|SETI@home\|Deferring communication with project for 58 seconds 06/02/2006 14.25.25\|\|request_reschedule_cpus: project op 06/02/2006 14.25.28\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 06/02/2006 14.25.28\|SETI@home\|Requesting 17280 seconds of work, returning 0 results 06/02/2006 14.25.30\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded 06/02/2006 14.25.30\|SETI@home\|Message from server: Not sending work - last RPC too recent: 47 sec ID: 243599 ·

RRipley Volunteer tester Send message Joined: 18 Apr 01 Posts: 880 Credit: 23,005,843 RAC: 0	Message 243618 - Posted: 6 Feb 2006, 16:03:32 UTC - in response to Message 243599. Last modified: 6 Feb 2006, 16:03:59 UTC 06/02/2006 14.22.10\|\|Starting BOINC client version 4.45 for windows_intelx86 06/02/2006 14.24.40\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 06/02/2006 14.24.40\|SETI@home\|Requesting 17280 seconds of work, returning 0 results 06/02/2006 14.24.42\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded 06/02/2006 14.24.42\|SETI@home\|No work from project 06/02/2006 14.24.43\|SETI@home\|Deferring communication with project for 58 seconds 06/02/2006 14.25.25\|\|request_reschedule_cpus: project op Everything's fine with your BOINC. There's wasn't work at that moment available. Just be patient. The Scheduler request itself was fine. But ... you said, you've installed the new version. So why there's v4.45 at start message? ID: 243618 ·

Andrea Piccioni Send message Joined: 17 Jun 99 Posts: 8 Credit: 558,381 RAC: 1	Message 244053 - Posted: 7 Feb 2006, 9:07:34 UTC - in response to Message 243618. [/quote] Everything's fine with your BOINC. There's wasn't work at that moment available. Just be patient. The Scheduler request itself was fine. But ... you said, you've installed the new version. So why there's v4.45 at start message?[/quote] There's v.4.45 because I have tried to use the old version Now: - I have reinstalled the new version. - I' have reset my project - BOINC has dowloaded 2 unit - I' have completed the new 2 unit But I' have the same problem uploading the completed unit and downloading other unit. Is everything fine ? Here the new messages with "return value of 500" Thank you 07/02/2006 7.01.07\|\|Starting BOINC client version 5.2.13 for windows_intelx86 07/02/2006 7.01.07\|\|libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3 07/02/2006 7.01.07\|\|Data directory: C:\\Program Files\\BOINC 07/02/2006 7.01.08\|\|Processor: 2 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz 07/02/2006 7.01.08\|\|Memory: 1.98 GB physical, 3.82 GB virtual 07/02/2006 7.01.08\|\|Disk: 76.69 GB total, 6.47 GB free 07/02/2006 7.01.08\|\|Version change detected (4.45.0 -> 5.2.13); running CPU benchmarks 07/02/2006 7.01.08\|SETI@home\|Computer ID: 1547529; location: work; project prefs: default 07/02/2006 7.01.08\|\|General prefs: from SETI@home (last modified 2005-10-19 14:23:06) 07/02/2006 7.01.08\|\|General prefs: no separate prefs for work; using your defaults 07/02/2006 7.01.09\|\|Remote control not allowed; using loopback address 07/02/2006 7.01.13\|\|Running CPU benchmarks 07/02/2006 7.02.10\|\|Benchmark results: 07/02/2006 7.02.10\|\| Number of CPUs: 2 07/02/2006 7.02.10\|\| 1325 double precision MIPS (Whetstone) per CPU 07/02/2006 7.02.10\|\| 1173 integer MIPS (Dhrystone) per CPU 07/02/2006 7.02.10\|\|Finished CPU benchmarks 07/02/2006 7.02.11\|SETI@home\|Resuming computation for result 02ja05ab.1236.33378.173580.1.164_0 using setiathome version 418 07/02/2006 7.02.11\|SETI@home\|Resuming computation for result 25ja04aa.1947.27216.1047168.1.64_3 using setiathome version 418 07/02/2006 7.02.11\|\|Resuming computation and network activity 07/02/2006 7.02.11\|\|request_reschedule_cpus: Resuming activities 07/02/2006 8.31.59\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.31.59\|SETI@home\|Reason: To fetch work 07/02/2006 8.31.59\|SETI@home\|Requesting 8 seconds of new work 07/02/2006 8.32.04\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.32.04\|SETI@home\|No schedulers responded 07/02/2006 8.33.08\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.33.08\|SETI@home\|Reason: To fetch work 07/02/2006 8.33.08\|SETI@home\|Requesting 662 seconds of new work 07/02/2006 8.33.13\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.33.13\|SETI@home\|No schedulers responded 07/02/2006 8.34.13\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.34.13\|SETI@home\|Reason: To fetch work 07/02/2006 8.34.13\|SETI@home\|Requesting 1301 seconds of new work 07/02/2006 8.34.18\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.34.18\|SETI@home\|No schedulers responded 07/02/2006 8.35.18\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.35.18\|SETI@home\|Reason: To fetch work 07/02/2006 8.35.18\|SETI@home\|Requesting 2002 seconds of new work 07/02/2006 8.35.23\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.35.23\|SETI@home\|No schedulers responded 07/02/2006 8.36.25\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.36.25\|SETI@home\|Reason: To fetch work 07/02/2006 8.36.25\|SETI@home\|Requesting 2706 seconds of new work 07/02/2006 8.36.30\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.36.30\|SETI@home\|No schedulers responded 07/02/2006 8.38.10\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.38.10\|SETI@home\|Reason: To fetch work 07/02/2006 8.38.10\|SETI@home\|Requesting 3886 seconds of new work 07/02/2006 8.38.15\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.38.15\|SETI@home\|No schedulers responded 07/02/2006 8.44.44\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.44.44\|SETI@home\|Reason: To fetch work 07/02/2006 8.44.44\|SETI@home\|Requesting 8739 seconds of new work 07/02/2006 8.44.49\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.44.49\|SETI@home\|No schedulers responded 07/02/2006 8.53.40\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 8.53.40\|SETI@home\|Reason: To fetch work 07/02/2006 8.53.40\|SETI@home\|Requesting 14412 seconds of new work 07/02/2006 8.53.45\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 8.53.45\|SETI@home\|No schedulers responded 07/02/2006 9.00.43\|\|request_reschedule_cpus: process exited 07/02/2006 9.00.43\|SETI@home\|Computation for result 02ja05ab.1236.33378.173580.1.164_0 finished 07/02/2006 9.00.45\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.00.49\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.00.49\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.01.49\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.01.53\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.01.53\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.02.54\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.02.57\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.02.57\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.03.58\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.04.01\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.04.01\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.05.01\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.05.04\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.05.04\|SETI@home\|Backing off 1 minutes and 55 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.07.01\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.07.05\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.07.05\|SETI@home\|Backing off 3 minutes and 0 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.10.05\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.10.08\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.10.08\|SETI@home\|Backing off 1 minutes and 43 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.11.52\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.11.55\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.11.55\|SETI@home\|Backing off 41 minutes and 33 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.25.33\|\|request_reschedule_cpus: process exited 07/02/2006 9.25.33\|SETI@home\|Computation for result 25ja04aa.1947.27216.1047168.1.64_3 finished 07/02/2006 9.25.35\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.25.38\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.25.38\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.26.39\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.26.42\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.26.42\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.27.43\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.27.45\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.27.45\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.28.46\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.28.50\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.28.50\|SETI@home\|Backing off 1 minutes and 0 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.29.50\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.29.53\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.29.53\|SETI@home\|Backing off 2 minutes and 25 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.32.19\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.32.22\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.32.22\|SETI@home\|Backing off 2 minutes and 4 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.34.27\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.34.30\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.34.30\|SETI@home\|Backing off 9 minutes and 32 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.41.21\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 07/02/2006 9.41.21\|SETI@home\|Reason: To fetch work 07/02/2006 9.41.21\|SETI@home\|Requesting 17280 seconds of new work 07/02/2006 9.41.26\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 07/02/2006 9.41.26\|SETI@home\|No schedulers responded 07/02/2006 9.44.04\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.44.07\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.44.07\|SETI@home\|Backing off 9 minutes and 13 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.53.21\|SETI@home\|Started upload of 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.53.25\|SETI@home\|Temporarily failed upload of 25ja04aa.1947.27216.1047168.1.64_3_0: error 500 07/02/2006 9.53.25\|SETI@home\|Backing off 1 hours, 21 minutes, and 49 seconds on upload of file 25ja04aa.1947.27216.1047168.1.64_3_0 07/02/2006 9.53.31\|SETI@home\|Started upload of 02ja05ab.1236.33378.173580.1.164_0_0 07/02/2006 9.53.35\|SETI@home\|Temporarily failed upload of 02ja05ab.1236.33378.173580.1.164_0_0: error 500 07/02/2006 9.53.35\|SETI@home\|Backing off 1 hours, 40 minutes, and 22 seconds on upload of file 02ja05ab.1236.33378.173580.1.164_0_0 ID: 244053 ·

MJKelleher Volunteer tester Send message Joined: 1 Jul 99 Posts: 2048 Credit: 1,575,401 RAC: 0	Message 244307 - Posted: 8 Feb 2006, 2:18:00 UTC Part of your problem today would be that the servers were down for backup and maintenance for about four hours, starting at about 20:00 UTC. Nobody could get through, and there is always a traffic jam for several hours afterwards as the backlogged work keeps pounding at the gates. If this is still happening in the morning, though, one solution that has helped some is to use a public proxy to connect. You can find a list of them at this web site, you may have to experiment before you get one that would work for you. The proxy settings in the BOINC manager are under Options in the menu bar, find the HTTP Proxy tab. MJ ID: 244307 ·

Buckeye4LF Send message Joined: 19 Jun 00 Posts: 173 Credit: 54,916,209 RAC: 833	Message 247791 - Posted: 14 Feb 2006, 4:24:02 UTC You are awesome dmbott. I tried reinstalling and everything but nothing worked. I tried your registry edit and I am now back up and number crunching. Thanks again! ID: 247791 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.