ALERT : Scheduler incompatible to CC4.19
22 Feb 2007 16:29:15 UTC
Topic 192471
(moderation:
Without the need to do it, Berkeley has decided to kick 4.19 out of the game :
CC4.19 doesn't like stuff that preceeds
The effect is known here in the project (or was it Pirates?) from the mime type string that had been on top of the scheduler reply (resulting in "SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain.")
4.19 hosts will get lots of WUs assigned but they will not recognize this assignment - resulting in thousands of ghost WUs.
Other 4.19 hosts will create a new host entry on each reply.
That was a really stupid modification!
ALERT : Scheduler incompatible to CC4.19
)
The bug reported above is especially very nice as "Merge hosts" seems to be broken too.
Sorry, I don't get the nuance
)
Sorry, I don't get the nuance of your post. This is a bug and we think BOINC will fix or it's fallout from a new feature and we are S O L?
I am certain I am running an old version of BOINC and because my employer wont allow me to upgrade, are my pending results "trash"? Seti@home is not reporting the same issue, btw.
Thanks.
SETI Beta with scheduler 509
)
SETI Beta with scheduler 509 has that problem too, whereas the SETI main project uses the older scheduler version 507, which did not have the character encoding string in the reply yet.
The BOINC devs added it as a new feature without thinking much about the consequences.
Depending on the number of 4.19 (and earlier) hosts that are still present, it can cause quite some trouble for the project itself, not just for the crunchers.
I wonder how you could report results with 4.19 yesterday, I have the problem on all 3 4.19 hosts, neither report nor fetch new work does any good. Maybe you have a proxy that filters this script stuff. It will not do damage to results that have already been reported btw..
The reason why I still use 4.19 on 3 boxes is : The cURL version of BOINC won't let me pass the firewall.
Thanks, Ananas. I don't
)
Thanks, Ananas.
I don't often spend much time on these 'boards, so should I also post this as "a bug imho" somewhere else?
Or, iyo, is it time to abandon BOINC on my non-upgradable box?
Well, I hope that the
)
Well, I hope that the Einstein project guys can make the BOINC developers take back this modification.
The problem seems not to affect your computers, maybe your company firewall filters script code ( ) so you sure can continue with 4.19
p.s.: the thing that bugs me most is that the code to skip unknown trash in the scheduler reply has been submitted by myself - and now I cannot even profit from that code snippet :´(
No, company took away Admin
)
No, company took away Admin rights. This means I can not install anything new. They were cowardly enough not to remove "unauthorized" software. ;-)
LOL ... I have to fight for
)
LOL ... I have to fight for admin rights on my own box@work too - but imho. a platform developer without admin right is not fully functional :-/
PC is bridge to my *real*
)
PC is bridge to my *real* development platform and is otherwise for email, IM and word processing. Because the company is not in the software business their knees knock together at the thought of all this "new-fangled technology". I am awaiting the day I will get an email banning memory sticks.
pssst ... they did that here,
)
pssst ... they did that here, limit USB usage to certain device types - but either the installer crashed on my box or they simply forgot me, but of course I will not complain ;-)
Currently developement isn't my primary job but we have a bad shortage in experienced C/C++ people so I often have to help out on AIX, Linux and Windows. We have Z/OS and BS2000 too but that's voodoo stuff and I won't touch it.
David A has checked in a fix
)
David A has checked in a fix for this...
Kathryn :o)
Einstein@Home Moderator