This has happened before -- got some misspelled files - like-
<url>http://uploader1.atm.ox.ac.uk/cpdn_cgi/file_upload_hnddler</url>

that fail upload with an error like "Project file upload handler is missing"

I'm doing (from memory (mine))
Stop BOINC - backup - edit client_state.xml to fix the misspppelled word 'handler' - restart BOINC

---

OK - the old fix worked and files are up0loading normally.

Question is - how many of these malformed wu's are out there?

Other question is - how many crunchers will notice?
And how many will be able or willing to apply the fix?

I know this problem happened a while ago - do any of the moderators have a good short instruction on the problem and the fix to post here?

And I also remember that a few crunchers got over-enthusiastic on editing the client_state.xml -- which is - in general - not something good to do. (experts on the various versions of BOINC and also CPDN excepted - but even those rare birds will be careful - and do backups before and after every step)

---

... Question is - how many of these malformed wu's are out there? ...

As I recall, it was established at the project end that the files leave them uncorrupted and are changed on/after download on Linux machines. I've always assumed it's a problem in the BOINC client somewhere, but no-one has ever found out where.

... Question is - how many of these malformed wu's are out there? ...

As I recall, it was established at the project end that the files leave them uncorrupted and are changed on/after download on Linux machines. I've always assumed it's a problem in the BOINC client somewhere, but no-one has ever found out where.

Yup - your recall matches my recall - one of those inexplicable data corruptions in the BOINC part -- NOT the cpdn data part. I think I tried a few things back then but got no handle (pun - pun -hnddle !) on what was happening.

I'll be watching my uploads on my 6 linux hosts more closely the next few weeks.

Thanks --

---

Have we ever had cases of the misspellings that weren't on Linux?

---

Cpdn news

There was a Windows user a couple of years back who said so, but I think that turned out to be not the case in the end.

It may be a variable in Linux that's an 'integer', and the value being sent is a 'double', or 'long', causing truncation/compression. Or a word that's storing values 'high byte/low byte', and it's being sent as 'low byte/high byte'.

And I don't think that it affects all varieties of Linux, just the most popular.

---

Backups: Here