#691 closed Defect (fixed)
Message from server: Incomplete request received
Reported by: | Ageless | Owned by: | davea |
---|---|---|---|
Priority: | Blocker | Milestone: | 6.2 |
Component: | Client - Daemon | Version: | 6.2.11 |
Keywords: | scheduler message server | Cc: | Ageless |
Description
This bug has been around since about 2005, people come on forums and report that their client, which was working perfectly for months, all of a sudden only returns this error. They can't upload, download or report work anymore.
Most of the times we try to help in forums, but since none of us knows what is causing it, eventually the person is left behind without help. As far as I know, the only real fix is to reformat, reinstall the OS and reinstall BOINC clean. Which isn't good enough, imho.
So I am inputting it into Trac, as a blocker.
Old threads it happened in:
http://setiathome.berkeley.edu/forum_thread.php?id=45585#718991
http://setiathome.berkeley.edu/forum_thread.php?id=46842#747721
http://www.primegrid.com/orig/forum_thread.php?id=304
http://einstein.phys.uwm.edu/forum_thread.php?id=5830
http://www.bjoernhenke.de/forum/viewtopic.php?t=433
http://boinc.gorlaeus.net/forum_thread.php?id=109
http://boinc.bakerlab.org/rosetta/forum_thread.php?id=4039&nowrap=true#52221
http://boinc.berkeley.edu/dev/forum_thread.php?id=2584#16465
The latest thread (and person I am trying to help):
http://einstein.phys.uwm.edu/forum_thread.php?id=6729
It would be nice to have a final answer to this problem.
Attachments (1)
Change History (5)
comment:1 Changed 17 years ago by
Owner: | changed from davea romw to davea |
---|
Changed 17 years ago by
Attachment: | 080628 TPQ BOINC Message Dump.doc added |
---|
comment:2 Changed 17 years ago by
The best way to figure out what's going on is capturing the network traffic (eg. with Wireshark), to see exactly what data the client is receiving. And/or running boinc under a debugger on a machine that gets such errors.
comment:3 Changed 17 years ago by
At this moment Tom is checking the maximum packet size he can send on the network (MTU). Perhaps that he's stuck behind a black hole router, or his ISP changed the maximum size of packets to be sent (without warning its clients).
comment:4 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed. With thanks to David.
See Message from server: Incomplete request received for cause and solution.
Log file with <http_debug> and <http_xfer_debug> flags on