Yet I also found that forcing BOINC to use HTTP 1.0 can solve this as well (was a couple of versions before 6.10.58 though). It doesn't hurt to try. It won't interfere with the speed of your internet connection, it's just a different protocol that the client uses to communicate with the projects. It's not a magical thing though and if it doesn't work, then it doesn't work. ;-)

I already tried it on my XP machine as you can see a few posts back and it didn't work. I will try the same on my Vista 64 pc and see what happens.

John

sorry have had another think

as the connection (appears) is made to the seti server, if we take the debug trace as correct, then its possible that the data being sent that is either not being understood or is corrupted - hence the

Received header from server: HTTP/1.1 500 Internal Server Error

the server is having a problem with what it is seeing from boinc

i doubt its too many reports at once as i have seen people quote a lot more than 350 in one go - unless you have a very slow upload speed - did the other pc's who did report have anywhere near the same number of task to report when the outage stopped at seti yesterday - if they did then that would eliminate this

---

Tim

I've been getting "Scheduler request failed: Couldn't connect to server" almost constantly since last week. The same on all 5 of my machines that are otherwise working normally. Abusing the buttons eventually connects but it can take quite a few retries sometimes.

IIRC they had a network problem last week right before they turned on the taps. Perhaps someone with the ear of the guys in the lab could suggest to them that they bounce a router or two . . . ? I couldn't hurt to try.

[edit] On second thought, UL's and DL's are working very well so perhaps the routers are not to blame, but there is indeed a problem there somewhere.

John

sorry have had another think

as the connection (appears) is made to the seti server, if we take the debug trace as correct, then its possible that the data being sent that is either not being understood or is corrupted - hence the

Received header from server: HTTP/1.1 500 Internal Server Error

the server is having a problem with what it is seeing from boinc

i doubt its too many reports at once as i have seen people quote a lot more than 350 in one go - unless you have a very slow upload speed - did the other pc's who did report have anywhere near the same number of task to report when the outage stopped at seti yesterday - if they did then that would eliminate this

Tim,

Your suggestions are certainly appreciated!

The other pc's reported similar amounts. I wrote down the amounts just prior to the servers coming back online: 347 (problem pc #1), 190 (Linux64), 157 (problem pc #2), 263 (XP32), 490 (Linux64), and 269 (Linux64).

The other pc's did have some problems getting through but they all reported within a few hours after the servers came back to life.
Also, the problems already started on Monday (around 19:00 UTC) when both pc's only had a few dozen tasks to report.

I will try the same on my Vista 64 pc and see what happens.

The Vista 64 pc also still gets the error 500 with HTTP1.0

I was having problems reporting work, although uploading was fine. Did the http_1_0 trick and its fine now. Every now and again I get a message about not being able to connect, but with a bit of patience, it does get there.

---

I was having problems reporting work, although uploading was fine. Did the http_1_0 trick and its fine now. Every now and again I get a message about not being able to connect, but with a bit of patience, it does get there.

Didn't do anything but most of my requests go thru.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I struggled to report yesterday, but did finally manage it. Then today, I was always getting the couldn't connect message. Of course, it could be coincidence that I've now been able to trickle report tasks as they complete after making the http_1_0 change...!

---

I have also been having problems reporting results since just before the last weekly outage. This computer is working fine. It uploads results and reports fine. This computer uploads fine but is unable to report. It gets the HTTP error. This is getting very frustrating.

I have 2 computers that can reach Seti and 3 that can't this is getting odd

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

I've returned early having left my computer on while i was away for 5 days. All my tasks have completed (71 tasks) but still non have reported. I'm off again early monday for two weeks and won't be leaving it on during this period.

And I don't seem to have a cc_config.xml file. Is this needed?

dlanor

---

And I don't seem to have a cc_config.xml file. Is this needed?

You need a cc_config file if you want to use certain features or special settings of Boinc, like the debugging info.
This file is not present as a default.

Ronald,
Did you set it to no new tasks? Try hitting the update button a couple of times if needed to see if that will send them in.

---

PROUD MEMBER OF Team Starfire World BOINC

I have also been having problems reporting results since just before the last weekly outage. This computer is working fine. It uploads results and reports fine. This computer uploads fine but is unable to report. It gets the HTTP error. This is getting very frustrating.

Looks as if something happened on the server(s) on Monday. Looking at the last time your problem pc reported:
26 Jul 2010 18:04:53 UTC

The last time my problem pc's reported:
26 Jul 2010 18:47:02 UTC
26 Jul 2010 18:06:23 UTC

Probably every 4 in 5 attempts results in a
1/08/2010 4:33:32 SETI@home Scheduler request failed: Couldn't connect to server
message.
Eventually when it does make contact i get the Reached limit on tasks message.

I suspect it's something server side as it's only occured since coming back up after the last outage (and the system took a long time for things to settle down & start splitting new work).

---

Grant
Darwin NT

not sure if this is related, but it looks like they've started to bring Beta back up, but I'm getting an error from there saying the feeder is down.
31/07/2010 21:27:56 | SETI@home Beta Test | Sending scheduler request: Requested by user.
31/07/2010 21:27:56 | SETI@home Beta Test | Reporting 194 completed tasks, not requesting new tasks
31/07/2010 21:28:19 | SETI@home Beta Test | Scheduler request completed
31/07/2010 21:28:19 | SETI@home Beta Test | Message from project server: Server error: feeder not running
31/07/2010 21:28:19 | | [work_fetch] Request work fetch: RPC complete

Beta's feeder is hosted on Anakin, which deals with a lot of the reporting daemons for here as well (schedulars, feeders, transitioners etc)
Wonder if in the process of bringing Beta up, something here started to play up?

---

Anyone know if this limit is still in effect?
The project is on line with the following limits:

40/CPU
320/GPU

If it is then Grant, you wont get anymore tasks since you have 85 WUs in progress and those 21 ghosts you have from awhile back may be effecting your count too.

---

PROUD MEMBER OF Team Starfire World BOINC

Probably every 4 in 5 attempts results in a
1/08/2010 4:33:32 SETI@home Scheduler request failed: Couldn't connect to server
message.
Eventually when it does make contact i get the Reached limit on tasks message.

I suspect it's something server side as it's only occured since coming back up after the last outage (and the system took a long time for things to settle down & start splitting new work).

All of my pc's have trouble reaching the server, but the main issue in this thread is that a number of pc's have not been able to report at all since Monday and the few times these pc's reach the scheduler it ends with an "HTTP internal server error" message.

Anyone know if this limit is still in effect?
The project is on line with the following limits:

40/CPU
320/GPU

If it is then Grant, you wont get anymore tasks since you have 85 WUs in progress and those 21 ghosts you have from awhile back may be effecting your count too.

Yep, the limits are there as i get the Computer has reach a limit on tasks in progress message when it does get through. The problem is it takes about 5 atttempts before it does get through.

---

Grant
Darwin NT

Sure not a smooth recovery...Hope they don't wait till Monday to raise limits.

---

Official Abuser of Boinc Buttons...
And no good credit hound!