// DBOINCP-300: added node comment count condition in order to get Preview working ?>
Anonymous
20 Feb 2005 23:44:08 UTC
Topic 12616
(moderation:
)
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!
> 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.
small problem
)
> 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