Message boards : BOINC Manager : Mysterious error 500 still with me
Message board moderation
Author | Message |
---|---|
Send message Joined: 14 Nov 05 Posts: 49 |
Hi everybody! Today I tried to install BOINC 5.2.12 and hope I will see the light on other cside of tunnel. No. Still darkness surrounds me. In other words: still cannot communicate through company http proxy server (authorisation required). If I use BOINC version 4.71, everything is OK. When I try to install version 5.2.x, everytime I get messages like this: 28.11.2005 15:01:54|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 28.11.2005 15:01:54|SETI@home|Reason: Requested by user 28.11.2005 15:01:54|SETI@home|Requesting 175073 seconds of new work, and reporting 1 results 28.11.2005 15:02:04|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 28.11.2005 15:02:04|SETI@home|No schedulers responded 28.11.2005 15:25:36|SETI@home|Started upload of 03no03ab.9712.27474.323574.228_3_0 28.11.2005 15:25:41|SETI@home|Temporarily failed upload of 03no03ab.9712.27474.323574.228_3_0: error 500 28.11.2005 15:25:41|SETI@home|Backing off 3 hours, 15 minutes, and 8 seconds on upload of file 03no03ab.9712.27474.323574.228_3_0 Tried many different 5.2.x versions, last 5.2.12. My home computer (directly connected to internet) have no problem with 5.2.x clients. |
Send message Joined: 25 Sep 05 Posts: 62 |
Hi everybody! Interesting observation. Same as another fella here. I have seen this before also and it has yet to be fixed. I have mailed the devs to let them know. If I hear anything I will post here. This is affecting quite a few people by the looks of it. |
Send message Joined: 25 Sep 05 Posts: 62 |
Hi Trying to rule in or out the IPX protocol. Just reading a bit on IPX/TCP/IP mixing = potentially bad news. Would be interested to know if anyone with server 500 error problems is running IPX or NetBEUI please? This may be related but need to gather some evidence. Sorry to repeat across threads but need the thread owner to take a look thanks. Thanks. |
Send message Joined: 29 Aug 05 Posts: 15561 |
It's a Seti problem, Ian. People can attach to Einstein and other projects without a problem. Only Seti gives the problem. So don't ask people to attach IPX/SPX and Netbeui when on XP. It won't help! |
Send message Joined: 14 Nov 05 Posts: 49 |
Hi So far I can understand, I'm not using IPX or NetBEUI. If you want to be 100% sure, point me where to check it. I checked it in Control panel / Network connections / Local Area Network / Properties - went through all settings and didn't found any appearance of IPX/SPX or NetBEUI. Btw - BOINC 5.2.13 - Still have error 500. Interesting (at least for me) is, although I cannot upload results and contact scheduler, I CAN download "Master file" 30.11.2005 6:37:38|SETI@home|Started upload of 14ja04ab.14943.18673.717330.138_3_0 30.11.2005 6:37:41|SETI@home|Temporarily failed upload of 14ja04ab.14943.18673.717330.138_3_0: error 500 30.11.2005 6:37:41|SETI@home|Backing off 2 hours, 3 minutes, and 16 seconds on upload of file 14ja04ab.14943.18673.717330.138_3_0 30.11.2005 6:37:52||request_reschedule_cpus: project op 30.11.2005 6:37:54|SETI@home|Fetching master file 30.11.2005 6:37:59|SETI@home|Master file download succeeded 30.11.2005 6:38:04|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 30.11.2005 6:38:04|SETI@home|Reason: Requested by user 30.11.2005 6:38:04|SETI@home|Requesting 223287 seconds of new work, and reporting 1 results 30.11.2005 6:38:09|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 30.11.2005 6:38:09|SETI@home|No schedulers responded Spok |
Send message Joined: 2 Sep 05 Posts: 103 |
Btw - BOINC 5.2.13 - Still have error 500. Interesting (at least for me) is, although I cannot upload results and contact scheduler, I CAN download "Master file" I've seen one report of the same problem with the CPDN spinup project. Exactly the same as yourself - master file fetch works, scheduler requests return HTTP error 500. "The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer |
Send message Joined: 30 Nov 05 Posts: 1 |
I got the same issue, here is my log if it helps. Ive seperated the error with ******. It looks like it does connect, but it cant download the requested work. I thought it might be port blocking on my router, but I have 2 other PC's on the network that are doing just fine! The only difference is this PC with the "issue" is "Windows 2000 Adv" and the other 2 are "Windows XP pro" All PC's have the latest SP's and updates. BOINC client LOG ---------------- 30/11/2005 12:24:37||Starting BOINC client version 5.2.13 for windows_intelx86 30/11/2005 12:24:37||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3 30/11/2005 12:24:37||Data directory: C:\\Program Files\\BOINC 30/11/2005 12:24:38||Processor: 1 GenuineIntel x86 Family 6 Model 7 Stepping 3 449MHz 30/11/2005 12:24:38||Memory: 255.49 MB physical, 1.23 GB virtual 30/11/2005 12:24:38||Disk: 5.86 GB total, 982.00 MB free 30/11/2005 12:24:38||No general preferences found - using BOINC defaults 30/11/2005 12:24:39||Remote control not allowed; using loopback address 30/11/2005 12:24:39||This computer is not attached to any projects. 30/11/2005 12:24:39||There are several ways to attach to a project: 30/11/2005 12:24:39||1) Run the BOINC Manager and click Projects. 30/11/2005 12:24:39||2) (Unix/Mac) Use boinc_cmd --project_attach 30/11/2005 12:24:39||3) (Unix/Mac) Run this program with the -attach_project command-line option. 30/11/2005 12:24:39||Visit http://boinc.berkeley.edu for more information 30/11/2005 12:24:46||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php 30/11/2005 12:25:19|http://setiathome.berkeley.edu/|Master file download succeeded 30/11/2005 12:25:19|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 30/11/2005 12:25:19|http://setiathome.berkeley.edu/|Reason: Requested by user 30/11/2005 12:25:19|http://setiathome.berkeley.edu/|Requesting 8640 seconds of new work ******************* 30/11/2005 12:27:40|http://setiathome.berkeley.edu/|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 ******************* 30/11/2005 12:27:40|http://setiathome.berkeley.edu/|No schedulers responded 30/11/2005 12:27:40|http://setiathome.berkeley.edu/|Couldn't connect to URL http://setiathome.berkeley.edu/.Please check URL. 30/11/2005 12:27:40|http://setiathome.berkeley.edu/|Resetting project 30/11/2005 12:27:40||request_reschedule_cpus: exit_tasks 30/11/2005 12:27:40|http://setiathome.berkeley.edu/|Detaching from project |
Send message Joined: 30 Aug 05 Posts: 297 |
As I just posted in the other "500" error thread: I am as far from a network guru as you can get, but on the SETI Number Crunching forum, it appears someone has found the solution to the "500" errors, or at least most of them. Somewhere between you and Berkeley, something is choking on "too large" an MTU... someone who has a clue will have to explain what that is and how to make it smaller on your PC... One thread is http://setiathome.berkeley.edu/forum_thread.php?id=23088 and there are others. |
Send message Joined: 8 Sep 05 Posts: 74 |
when i had some problems with MTU sizes this article solved my problem, i'm sure it can be used/adapted to serve the needs here |
Send message Joined: 14 Nov 05 Posts: 49 |
...also with BOINC 5.3.2. And although I maybe can adjust settings as describes Lee Carre's link, I will not do it. Just because BOINC should run without hacking "something else". If it will not run, I will not use it. Now downgrading to last working version 4.71 and continue crunching. *********************** 7.12.2005 14:38:09||Rescheduling CPU: project op 7.12.2005 14:38:09|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi 7.12.2005 14:38:09|LHC@home|Reason: Requested by user 7.12.2005 14:38:09|LHC@home|Reporting 7 results 7.12.2005 14:38:14|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi failed: error 500 7.12.2005 14:38:14|LHC@home|No schedulers responded 7.12.2005 14:38:39||Rescheduling CPU: project op 7.12.2005 14:38:40|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7.12.2005 14:38:40|SETI@home|Reason: Requested by user 7.12.2005 14:38:40|SETI@home|(not requesting new work or reporting results) 7.12.2005 14:38:45|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: error 500 7.12.2005 14:38:45|SETI@home|No schedulers responded *********************** For BOINC developers - if you need some help with testing, don't hesitate to contact me. I can try to run some nightbuild or some utility just for testing this issue. Spok |
Send message Joined: 2 Sep 05 Posts: 103 |
I suspect this is probably related to an HTTP 500 error condition I investigated on the CPDN coupled model spinup project. When a request is sent to the scheduler you can get an HTTP 100-continue intermediate response indicating that the scheduler has received your request and is working on it. When the scheduler finishes processing the request it sends the reply, which you receive as an HTTP 200-OK message. BOINC was generating the 500 error and closing the socket after receiving the 100-continue message. This prevented the 200-OK message from getting through. I submitted a change to fix this a couple of days ago, but it hasn't been checked in yet. One user is experiencing this all the time on all hosts, others are getting it intermittently but most never get it. "The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer |
Send message Joined: 25 Nov 05 Posts: 55 |
I also have this problem! I am using Boinc 5.2.13. But the Error 500 Message appears only when Seti@Home try to upload a result... Stefan BOINC@Austria |
Send message Joined: 8 Dec 05 Posts: 3 |
well, since others are getting the same thing like me, where I can not upload finished units, I supect a server problem. I remember some time back when I was still a SETI classic user, all of us were getting the "mysterious fatal error thing" and we all had to do a work around by hiding our results in a new folder so, it could download new work. When the server was working again we just moved them back one by one restarting SETI so, it would up load them. For the time being I am still working on one, and still have another unit still left to go, so I guess I won't panic this time <grin> If I remember what happened that time, I believe someone hack into the server and messed things up; and worse yet, it was at a start of a weekend... why do intelligent people do such stupid things? |
Send message Joined: 25 Nov 05 Posts: 55 |
One of the things that David Anderson did when designing BOINC, from his experience with SETI@H classic, was to make it much more tolerant of times when the servers were down. Another was to make it multi-project, so that there should always be at least one able to supply work. From memory there is a problem if BOINC has been unable to upload work after two weeks of trying, but the software may have been amended since then. At any rate, if you check the SETI site from time to time you will be told the situation, and there is no point in worrying about it. |
Send message Joined: 8 Dec 05 Posts: 3 |
well, checking at the SETI Project site, it IS a server problem! http://setiathome.berkeley.edu/tech_news.php however, nothing was lost teaking my MTU settings on my router and PC... It needed it anyhow.... LOL |
Send message Joined: 14 Nov 05 Posts: 49 |
Hello Tried BOINC 5.3.3 Messages changed, but still cannot connect to server. **************************** 23.12.2005 9:08:54|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 23.12.2005 9:08:54|SETI@home|Reason: Requested by user 23.12.2005 9:08:54|SETI@home|Reporting 1 results 23.12.2005 9:08:59||Network error: Send failed since rewinding of the data stream failed 23.12.2005 9:08:59|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: http error 23.12.2005 9:08:59|SETI@home|No schedulers responded **************************** Downgrading back to 4.71 Spok |
Send message Joined: 29 Aug 05 Posts: 225 |
Downgrading back to 4.71 Thanks for the good log snippet... Did downgrading work? |
Send message Joined: 23 Dec 05 Posts: 1 |
I'm running Boinc version 5.2.13 and I'm getting the same basic error 12/23/2005 6:19:23 AM||Fetching config info from http://boinc.bakerlab.org/rosetta/get_project_config.php 12/23/2005 6:19:36 AM|http://boinc.bakerlab.org/rosetta/|Master file download succeeded 12/23/2005 6:19:36 AM|http://boinc.bakerlab.org/rosetta/|Sending scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi 12/23/2005 6:19:36 AM|http://boinc.bakerlab.org/rosetta/|Reason: Requested by user 12/23/2005 6:19:36 AM|http://boinc.bakerlab.org/rosetta/|Requesting 8640 seconds of new work 12/23/2005 6:19:38 AM|http://boinc.bakerlab.org/rosetta/|Scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi failed with a return value of 500 12/23/2005 6:19:38 AM|http://boinc.bakerlab.org/rosetta/|No schedulers responded 12/23/2005 6:19:38 AM|http://boinc.bakerlab.org/rosetta/|Couldn't connect to URL http://boinc.bakerlab.org/rosetta/.Please check URL. 12/23/2005 6:19:38 AM|http://boinc.bakerlab.org/rosetta/|Resetting project 12/23/2005 6:19:38 AM||request_reschedule_cpus: exit_tasks 12/23/2005 6:19:38 AM|http://boinc.bakerlab.org/rosetta/|Detaching from project |
Send message Joined: 14 Nov 05 Posts: 49 |
Downgrading back to 4.71 Yes, you have to just install Boinc 4.71 twice. Don't know why, after first installation there are no *.exe files. During second installation choose 'Repair' and then it runs OK. Spok |
Send message Joined: 14 Nov 05 Posts: 49 |
Hello BOINC 5.3.6 have exactly same error messages as BOINC 5.3.3 Still cannot see through proxy. Spok |
Copyright © 2024 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.