Problem connecting to server:


2009-03-09 19:17:52 GPUGRID Sending scheduler request: Requested by project.
2009-03-09 19:17:52 GPUGRID Requesting new tasks
2009-03-09 19:17:57 GPUGRID Scheduler request failed: HTTP internal server error

this has been all day

I've got the same error here :(

I've been getting the same error since 8:40 this morning (GMT-4:00).

However, that error only seems to occur when the server decides NOT to give me a new workunit (i.e., when I already have 4 WUs).

At the expected times, when I report a completed WU, it does send me a new one. Then, next time around, I get the http error again.

So, in the end, the server appears to be doing exactly what it was doing before: Serving up WUs and processing returned units. But it's throwing that http internal server error message instead of giving me the per-cpu limit message.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

this error cause latest version of boinc manager to malfunction 6.6.14
report sent to boinc team

I am seeing the same as Michael G. with success in reporting and downloading a new task to fill my queue, the next request gets the error. Are we seeing an issue when we should be seeing a message telling us we are at the limit of our downloads?

What I mean is that the scheduler may have lost its link to database?

Whatever, I would suspect that a server restart would clear this up ... though I would not bet my lunch on it ... well, maybe I would ... forgot to eat lunch today so ... :)

haha I feel with you. I hope i will find my lunch tomorrow.

Theres still an Server error

2009-03-10 10:01:39 GPUGRID Sending scheduler request: Requested by project.
2009-03-10 10:01:39 GPUGRID Requesting new tasks
2009-03-10 10:01:44 GPUGRID Scheduler request failed: HTTP internal server
2009-03-10 10:01:49 GPUGRID Sending scheduler request: Requested by project.
2009-03-10 10:01:49 GPUGRID Requesting new tasks
2009-03-10 10:01:54 GPUGRID Scheduler request failed: HTTP internal server error
2009-03-10 10:01:59 GPUGRID Fetching scheduler list
2009-03-10 10:02:04 GPUGRID Master file download succeeded
2009-03-10 10:02:09 GPUGRID Sending scheduler request: Requested by project.
2009-03-10 10:02:09 GPUGRID Requesting new tasks
2009-03-10 10:02:14 GPUGRID Scheduler request failed: HTTP internal server error
2009-03-10 10:02:19 GPUGRID Sending scheduler request: Requested by project.
2009-03-10 10:02:19 GPUGRID Requesting new tasks
2009-03-10 10:02:24 GPUGRID Scheduler request failed: HTTP internal server error

I've restarted it.

Let's see if Paul gets his lunch today :)

ignasi

sORRY TO SAY - YOUR RESTART DIDNT SUCCESS

2009-03-10 13:24:20 GPUGRID Sending scheduler request: To fetch work.
2009-03-10 13:24:20 GPUGRID Requesting new tasks
2009-03-10 13:24:25 GPUGRID Scheduler request failed: HTTP internal server error

I am also getting this error, but only on one of my computers. It seems to be in an endless loop. neither re-booting my computer, nor suspending the task and resuming breaks the loop. Has anyone found an answer? Rick

---

I've restarted it.

Let's see if Paul gets his lunch today :)

I wish ...

I have not looked at my logs today ... and missed lunch anyway ... damn depression ...

{edit}

I just forced an update, asked for 48,666 seconds work, report none, get the internal server error rather than the message that I have all the tasks I am going to get ...

Still getting the looped same error messages:
3/10/2009 5:37:41 PM GPUGRID Sending scheduler request: To fetch work.
3/10/2009 5:37:41 PM GPUGRID Requesting new tasks
3/10/2009 5:37:46 PM GPUGRID Scheduler request failed: HTTP internal server error
3/10/2009 5:38:51 PM GPUGRID Sending scheduler request: To fetch work.
3/10/2009 5:38:51 PM GPUGRID Requesting new tasks
3/10/2009 5:38:56 PM GPUGRID Scheduler request failed: HTTP internal server error
I still managed to get work in between the error loop, but then it went right back to the sequence above.
Rick

---

I still managed to get work in between the error loop, but then it went right back to the sequence above.
Rick

It looks like some change on the server side has broken the system ... this error is being reported instead of the message that says that you are at your limits...

I wonder if the last minor tweaks to the server side have caused this NEW Issue ... we changed the back off parameter and something else I forget just before that ...

Still no success from crew finding the HTTP error?

This should be solved now.

gdf