Message boards :
Number crunching :
Problem reporting tasks
Message board moderation
Author | Message |
---|---|
Ronald Send message Joined: 15 May 99 Posts: 8 Credit: 1,562,838 RAC: 0 |
Hi. I seem to be having a problem reporting tasks from one of my machines (currently 30 tasks) I get the following messages : scheduler request failed: HTTP internal server error or scheduler request failed: Couldn't connect to server Internet access OK - project servers may be temporarily down It has no problems uploading tasks This machine is using an anonymous platform cheers dlanor |
hiamps Send message Joined: 23 May 99 Posts: 4292 Credit: 72,971,319 RAC: 0 |
Hi. I seem to be having a problem reporting tasks from one of my machines (currently 30 tasks) Most of us are the servers are maxed getting ready to shut down. Peole are trying to get last minute work. Official Abuser of Boinc Buttons... And no good credit hound! |
OfficeDude Send message Joined: 7 Jul 99 Posts: 8 Credit: 2,322,928 RAC: 0 |
This message already started to appear in my logs 8 hours ago. Ooh well, the early bird gets.... |
Ronald Send message Joined: 15 May 99 Posts: 8 Credit: 1,562,838 RAC: 0 |
Most of us are the servers are maxed getting ready to shut down. Peole are trying to get last minute work. That's a pity as some of it will have gone past the report deadline before i'll be able to get back online. thanks dlanor |
hiamps Send message Joined: 23 May 99 Posts: 4292 Credit: 72,971,319 RAC: 0 |
Most of us are the servers are maxed getting ready to shut down. Peole are trying to get last minute work. You have a bit of time yet, keep hitting update I got a few in.... Official Abuser of Boinc Buttons... And no good credit hound! |
hiamps Send message Joined: 23 May 99 Posts: 4292 Credit: 72,971,319 RAC: 0 |
Didn't help that the first project backoff for my machine started at 1 hour 12 minutes and went up from there. If boinc couldn't report sometimes it would try and back off for 2 or 3 hours...With the small amount of time we have to report and get work, project backoffs should be less not more! Official Abuser of Boinc Buttons... And no good credit hound! |
hiamps Send message Joined: 23 May 99 Posts: 4292 Credit: 72,971,319 RAC: 0 |
Most of us are the servers are maxed getting ready to shut down. Peole are trying to get last minute work. 7/27/2010 8:32:40 AM | SETI@home | update requested by user 7/27/2010 8:32:44 AM | SETI@home | Sending scheduler request: Requested by user. 7/27/2010 8:32:44 AM | SETI@home | Reporting 5 completed tasks, requesting new tasks for CPU and GPU 7/27/2010 8:33:08 AM | SETI@home | Scheduler request completed: got 0 new tasks Official Abuser of Boinc Buttons... And no good credit hound! |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
Most of us are the servers are maxed getting ready to shut down. Peole are trying to get last minute work. Cricket shows the last hour not being maxed out, still there's often no connect or no tasks available. This has been going on I think most of the time after last outage, I *think* there's some other problem going on. |
hiamps Send message Joined: 23 May 99 Posts: 4292 Credit: 72,971,319 RAC: 0 |
The last hour I got quite a bit of work, probably will need a new client as my "update" button is probably getting pretty worn...LOL But with that and the reschedule I might make it. EDIT: 7/27/2010 9:09:43 AM | SETI@home | update requested by user 7/27/2010 9:09:44 AM | SETI@home | Sending scheduler request: Requested by user. 7/27/2010 9:09:44 AM | SETI@home | Reporting 3 completed tasks, requesting new tasks for CPU and GPU 7/27/2010 9:10:15 AM | SETI@home | Scheduler request completed: got 0 new tasks 7/27/2010 9:10:15 AM | SETI@home | Message from project server: Project has no tasks available 7/27/2010 9:10:30 AM | SETI@home | Sending scheduler request: To fetch work. 7/27/2010 9:10:30 AM | SETI@home | Requesting new tasks for CPU Official Abuser of Boinc Buttons... And no good credit hound! |
S@NL - XP_Freak Send message Joined: 10 Jul 99 Posts: 99 Credit: 6,248,265 RAC: 0 |
I have not been able to report work since yesterday 26-06-2010 20:00 UTC That's now for about 20 hours. I did not get any new WU's during that time. Therefore I think I will be out of work in a little more then two days. 27-7-2010 17:47:41 SETI@home Reporting 3 completed tasks, requesting new tasks 27-7-2010 17:48:04 SETI@home Scheduler request failed: HTTP internal server error Goodbye Seti Classic |
Bearcat Send message Joined: 10 Sep 99 Posts: 106 Credit: 10,778,506 RAC: 0 |
Cricket shows the last hour not being maxed out, still there's often no connect or no tasks available. This has been going on I think most of the time after last outage, I *think* there's some other problem going on. That problem has been explained a few times before, but I cannot find the right thread right now. It has something to do with the scheduler or the feeder only having 100 units every 6 seconds, and if those are used/taken/send to someone else, you'll get the msg no work available althought there might be thousands of units shown on the server status page or the cricket graph not being maxed out. In other words, keep trying , it'll work eventually :) |
hiamps Send message Joined: 23 May 99 Posts: 4292 Credit: 72,971,319 RAC: 0 |
I have not been able to report work since yesterday 26-06-2010 20:00 UTC Yep, they are making you work for them now a days.... Official Abuser of Boinc Buttons... And no good credit hound! |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
That problem has been explained a few times before, but I cannot find the right thread right now. It has something to do with the scheduler or the feeder only having 100 units every 6 seconds, and if those are used/taken/send to someone else, you'll get the msg no work available althought there might be thousands of units shown on the server status page or the cricket graph not being maxed out. In other words, keep trying , it'll work eventually :) Yes I know about that, I just think it has been happening much more lately, as if there's some other problem going on. |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 |
Most of us are the servers are maxed getting ready to shut down. Peole are trying to get last minute work. The "no tasks available" part is fairly easy. There are long stretches of the resultID sequence which have no AP tasks, so the Feeder only fills the 96 (my guess) slots for MB tasks. Those 96 represent about 296 Mbits to be downloaded, and if the Feeder is using the default 5 second sleep periods then the average download rate cannot be more than about 59.2 Mbits/second. Meanwhile, those 96 get assigned to hosts quickly, and during the remainder of the 5 second sleep period other hosts get "no tasks available". Note that parts of the resultID sequence which do have 3 AP tasks for each Feeder run add about 206.5 Mbits to the downloads each time, giving somewhat more than 100 Mbits/sec assigned download rate and leading to those bursts where the line is saturated. The "no connect" is much more difficult to diagnose. Essentially it just means that the handshaking required to establish a connection is failing someplace. Given about 260000 active hosts and estimating each trying to get work 4 times a day, that's 12 scheduler requests a second and shouldn't be difficult to handle. But when a host does get a successful work request in which gets less work than the host wants, the request backoff is cleared and the host does additional requests at one minute intervals. In effect more successful requests may greatly increase the overall rate of requests. I don't know whether that contributes to connect failures, but it seems it might. Joe |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
But when a host does get a successful work request in which gets less work than the host wants, the request backoff is cleared and the host does additional requests at one minute intervals. If host gets some work on a work-request, there's only the project-specified backoff, this is atleast 6 seconds (if project haven't specified anything). For SETI@home the deferral is 11 seconds, so a host can max manage making 5 work-requests per minute. In practice every step in a scheduler-request will take a little time, so would guess 3 work-requests per minute is the practical max, if all of them is successful that is. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
Searcher Send message Joined: 26 Jun 99 Posts: 139 Credit: 9,063,168 RAC: 15 |
Looks like I have been getting the same error as OP. I have 57 ready to report. :( |
S@NL - John van Gorsel Send message Joined: 5 Jul 99 Posts: 193 Credit: 139,673,078 RAC: 0 |
I still get the HTTP internal server error or Couldn't connect to server on two of my pc's. Both pc's have not been able to report any tasks since Monday (30 hours before the server outage). Uploads worked fine on these pc's and 4 other pc's on the same physical network have no problem reporting. The things I tried so far: - Be patient and wait for network traffic jam to clear - Upgrade to Boinc 6.10.58 - Restart the pc - ipconfig /flushdns None of it helped and I really would like to report those 523 work units.. Any suggestions on how to diagnose this? Seti@Netherlands website |
S@NL - XP_Freak Send message Joined: 10 Jul 99 Posts: 99 Credit: 6,248,265 RAC: 0 |
I still get the HTTP internal server error or Couldn't connect to server on two of my pc's. Both pc's have not been able to report any tasks since Monday (30 hours before the server outage). No, I have no suggestions. I have got the same problem and tried the same things you did, except IPconfig. Goodbye Seti Classic |
Tim Norton Send message Joined: 2 Jun 99 Posts: 835 Credit: 33,540,164 RAC: 0 |
Hi John looking at you PC are we talking about linux or windows? - i guess windows few ideas or thinks to check - you may have already done this :) i assume you do have network activity enabled and no odd settings in your preferences in BM etc do you have any other boinc projects on the affected machines and do the report/connect ok? and you can connect to the internet from the affected machines ok? affected machines can see and be seen by others on your network etc as you have a reasonably large number to report - if you suspend most of them an leave a few to report and see if that makes any difference - unlikely but... one thing you might try is power cycle you router as it may be a glitch but as your other pc's are ok - unlikley but... see how you go with that :) [edit] sorry the suspend idea does not work - thought i had done this successfully myself - lol [/edit] Tim |
S@NL - XP_Freak Send message Joined: 10 Jul 99 Posts: 99 Credit: 6,248,265 RAC: 0 |
Tim, The problem of not being able to report started on 26 of July. That is true for Ronald, OfficeDude, John van Gorsel and me. Same problem is also reported by others on our forum of SETI@Netherlands. So I don't think the problem is in our PC's. This is something that Berkeley has to solve. Goodbye Seti Classic |
©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.