Problem reporting tasks |
![]() |
| log in |
Message boards : Number crunching : Problem reporting tasks
1 · 2 · 3 · 4 . . . 7 · Next
| Author | Message |
|---|---|
|
Hi. I seem to be having a problem reporting tasks from one of my machines (currently 30 tasks) | |
| ID: 1020128 · | |
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! | |
| ID: 1020129 · | |
|
This message already started to appear in my logs 8 hours ago. Ooh well, the early bird gets.... | |
| ID: 1020131 · | |
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 ____________ | |
| ID: 1020132 · | |
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! | |
| ID: 1020136 · | |
|
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! | |
| ID: 1020138 · | |
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! | |
| ID: 1020139 · | |
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. | |
| ID: 1020155 · | |
|
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. | |
| ID: 1020159 · | |
|
I have not been able to report work since yesterday 26-06-2010 20:00 UTC | |
| ID: 1020169 · | |
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 :) ____________ | |
| ID: 1020170 · | |
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! | |
| ID: 1020180 · | |
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. | |
| ID: 1020368 · | |
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 | |
| ID: 1020424 · | |
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." | |
| ID: 1020489 · | |
|
Looks like I have been getting the same error as OP. | |
| ID: 1020912 · | |
|
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). | |
| ID: 1021131 · | |
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 | |
| ID: 1021132 · | |
|
Hi John | |
| ID: 1021135 · | |
|
Tim, | |
| ID: 1021143 · | |
Message boards : Number crunching : Problem reporting tasks
| Copyright © 2013 University of California |