Eric's biannual post #6: You can tuna fish, but you can't tune a TCP

Hi Eric, Thanks for the information. I just want to confirm something. . .

. . . Only penguin is on download duty, but that may change if downloads start becoming a problem. . .
. . . Eric

Please note unusual verbage (Message from Server: Incomplete request received.) in the following exchange. This seems to be common to many per the message threads.

Please note unusual verbage (Message from Server: Incomplete request received.) in the following exchange. This seems to be common to many per the message threads.

As you say, many people have reported this - yet others say things are working normally.

I have two older hosts/older clients (v5.3.12.tx36) which have been trying to report at intervals all day. Sometimes they failed to contact the scheduler at all, sometimes they got the 'Incomplete request received' response. Since Eric mentioned that the scheduler has been moved, I thought I'd give them a prod.

Just did an 'Exit BOINC - start BOINC' sequence, and both have now reported. Coincidence or.....?

Only penguin is on download duty, but that may change if downloads start becoming a problem.

Only penguin is on download duty, but that may change if downloads start becoming a problem.

That would be now. Nothing is downloading, even though the account information on the server says that it has.

Do you mean you have tasks shown on the 'Transfers' tab in BOINC Manager, trying but failing to download? If so, then we need an additional download server.

Or do you mean you see tasks in the 'Results for computer' on this web site, but nothing in BOINC Manager? We call those "Ghost WUs" - different problem, different solution.

Just one more wierd happening to report and I'll be quiet. One of my hosts reported to request work and report 36 results. It got the dreaded:

5/17/2007 6:07:11 PM Scheduler request failed: HTTP internal server error

When I checked that host under My Computers on the web site, I see that all 36 were indeed reported at that time even though they still show up in BOINC as "Ready to Report". The system also claims to have sent two ghost work units at the same time which never arrived.

Anyway, things are still very broken. Just my 2c.

Eric, it looks like you hit the jackpot. Slowly but surely my upload queue is shrinking and WUs are trickling down too. Thanks for making it happen!

I got manu WU's, too. Unfortunately they were all ghosts. They upload queue is gone, though.

It's still pretty hit and miss (as you can see). Hopefully it's getting toward more hit than miss at this point.

Ptolemy lost connectivity to the upload directories on bruno for a while. Just fixed that, so our upload rate should double.

This Graph is still your best bet of checking your chances of getting through. The higher the graph is, the better. But we should be hovering around 22 Mbps rather than 15.

We're still operating on a single scheduler due to compile problems. G'nite. I'll catch up on where we are in the morning.

Eric


____________

@ Eric,

A lot of people are reporting incomplete scheduler requests (with various error messages) and the creation of a lot of 'ghost' results - potentially storing up another batch of problems in the future when the 'ghost' deadlines expire.

At least some of this seems to relate to the anonymous platform mechanism. The following recipe has worked for me on three machines, and independently verified by another user:

Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying
Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)

I don't know why this works - one user has speculated about app_info processing overhead, I'm wondering about the BOINC v5.10 <platform> tag - but it seems consistent and reproducible, so it may help to narrow down the debug search.

Eric, just to add to what others have said, none of my ten workstations are able to upload/download, and are returning the same messages, "Schedular Request Failed: Server returned nothing (No headers, no data)" and then they return the " Message from Server: Incomplete request recieved" message.

Eric, just to add to what others have said, none of my ten workstations are able to upload/download, and are returning the same messages, "Schedular Request Failed: Server returned nothing (No headers, no data)" and then they return the " Message from Server: Incomplete request recieved" message.

Could you give me an IP address for this machine? I'd like to scan the logs to see what's going on on this side.

Eric

@ Eric,

A lot of people are reporting incomplete scheduler requests (with various error messages) and the creation of a lot of 'ghost' results - potentially storing up another batch of problems in the future when the 'ghost' deadlines expire.

At least some of this seems to relate to the anonymous platform mechanism. The following recipe has worked for me on three machines, and independently verified by another user:

Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying
Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)

I don't know why this works - one user has speculated about app_info processing overhead, I'm wondering about the BOINC v5.10 <platform> tag - but it seems consistent and reproducible, so it may help to narrow down the debug search.



That solution seems to work for me as well as i use the anonymous plattforn mechanism in conjunction with boinc 5.8.16 and had servere difficulties do download any new wu's since the 16th. around 16:00utc
Now new wu's pooring in.
The above mentioned workaround works.

ty Richard


____________