small problem
20 Feb 2005 23:44:08 UTC
Topic 187785
(moderation:
Hi...can anybody explain me what does this mean and how to prevent it?
21.2.2005 0:49:17|Einstein@Home|Got ack for result H1_0507.9__0508.0_0.1_T05_Test02, can't find
I´ve just finished WU, contacted server,pending credit appeared but the WU is still in my work queue and after project update there is this announcement...what the hell?
Using 4.22 boinc client
small problem
)
Isn't 4.22 a non stable release?
I'm using 4.22. It's a
)
I'm using 4.22. It's a developmental (I.E. Alpha)release. People like me run it so that we can help get that line of program debugged. 4.19 is the current Boinc Core client that has been released for general use. All programs have bugs, and can be improved in some way. I.E Microsoft XP "SERVICE Pack II". You can run 4.22 if you choose to, as long as you accept the risks associated. I.E having to reload your operating system and all software, replacement of burned out components. That kind of thing.
I've run most the developmental, some have worse bugs than others.
does this help?
Also, the Error message you're getting seems to be quite common as you will find many other recent threads with the same problem.
This looks like the result of
)
This looks like the result of a client-server communication problem that Bruce fixed on the scheduler side some hours ago. Shouldn't happen again. Show up if it does!
BM
BM
> This looks like the result
)
> This looks like the result of a client-server communication problem that Bruce
> fixed on the scheduler side some hours ago. Shouldn't happen again. Show up if
> it does!
Bernd is probably right. The scheduler was sending some replies to clients that had more than 256 bytes on a line. *Supposedly* the 4.19 client and your 4.22 client can handle this. But it was apparently causing trouble. I think it's very possible that some of these problems that you have seen are also due to such issues. Hopefully the problems will now fade away.
Note that for users operating behind proxy servers, ALL the current clients (4.19, current experimental/development, etc) suffer from some bugs which might also cause the behavior you are seeing. Updated/fixed BOINC clients should be ready soon.
Cheers,
Bruce
Director, Einstein@Home