I upgraded my BOINC client to 6.13.12, so I could get ATI tasks to work over on another project. Anyway, now I am trying to get work for this project again, and am running into error messages, and I can't get work. Can something be done to make Moo! compatible with the new version of BOINC client?

11/18/2011 7:04:06 AM | Moo! Wrapper | update requested by user
11/18/2011 7:04:09 AM | Moo! Wrapper | [sched_op] Starting scheduler request
11/18/2011 7:04:09 AM | Moo! Wrapper | Sending scheduler request: Requested by user.
11/18/2011 7:04:09 AM | Moo! Wrapper | Requesting new tasks for ATI
11/18/2011 7:04:09 AM | Moo! Wrapper | [sched_op] CPU work request: 0.00 seconds; 0.00 CPUs
11/18/2011 7:04:09 AM | Moo! Wrapper | [sched_op] ATI work request: 172801.73 seconds; 0.33 CPUs
11/18/2011 7:04:11 AM | Moo! Wrapper | [error] Can't parse application version in scheduler reply: unexpected XML tag or syntax
11/18/2011 7:04:11 AM | Moo! Wrapper | [error] No close tag in scheduler reply
11/18/2011 7:04:11 AM | Moo! Wrapper | [sched_op] Deferring communication for 37 min 12 sec
11/18/2011 7:04:11 AM | Moo! Wrapper | [sched_op] Reason: can't parse scheduler reply

---

Reno, NV
Team SETI.USA

Anything above the recommended version of BOINC is development only, and problems may occur.

However that is especially true of odd number iterations, which by convention really are "off the wall" testing out future concepts, and are highly likely to be unstable, more so than other Alpha development releases, and even more not meant for general use than "normal" Alpha non recommended releases.

Stay with even numbered releases - ie 6.12.XX, 6.14.xx, 6.16.xx etc. I am curently running 6.12.43 wihich is the latest BOINC Alpha for the 6.12.xx series, running fine for me.

Regards
Zy

Yes, I know I am using experimental versions, and all the issues that can go with it. I am using 6.13.xx intentionally, to do testing.

It turns out that DA has already asked the projects to modify their settings, and this project just needs to implement.

http://boinc.berkeley.edu/dev/forum_thread.php?id=7054

---

Reno, NV
Team SETI.USA

11/18/2011 7:04:11 AM | Moo! Wrapper | [error] Can't parse application version in scheduler reply: unexpected XML tag or syntax
11/18/2011 7:04:11 AM | Moo! Wrapper | [error] No close tag in scheduler reply
11/18/2011 7:04:11 AM | Moo! Wrapper | [sched_op] Deferring communication for 37 min 12 sec
11/18/2011 7:04:11 AM | Moo! Wrapper | [sched_op] Reason: can't parse scheduler reply

Interesting error that might be related to switching to the new XML parser that's happening at the moment. I'll see if there's something fixed in a later server revision and update server side (which I need to do anyway).

Meanwhile, you could check the sched_reply_moowrap.net.xml file in your BOINC data folder to see if you can spot any obvious validation problems in it. Especially related to an app_version tag that's is supposedly malformed according to that error. Note that only the last reply is stored there so the error must have just happened to catch the erroneous scheduler reply.

If you want, you can also post contents of the (or maybe even the whole file) to me in a PM or some other way and I can take a look.

-w

I had moved my machines back to 6.12.34 so I could get some work. I will move one back to 6.13.12 later tonight, and get you the info.

---

Reno, NV
Team SETI.USA

Boinc 6.13.12

11/23/2011 1:16:55 PM | Moo! Wrapper | Master file download succeeded
11/23/2011 1:17:00 PM | Moo! Wrapper | Sending scheduler request: Project initialization.
11/23/2011 1:17:00 PM | Moo! Wrapper | Requesting new tasks for CPU and NVIDIA
11/23/2011 1:17:03 PM | Moo! Wrapper | [error] Can't parse application version in scheduler reply: unexpected XML tag or syntax
11/23/2011 1:17:03 PM | Moo! Wrapper | [error] No close tag in scheduler reply

---

Proud Member of Team [H]ard|OCP and the [H]ard DC Commandos

Boinc 6.13.12

Cool. Another with the same problem. Can you please forward the files he requested? That would same me the hassle of converting back to 6.13 (until this gets resolved).

---

Reno, NV
Team SETI.USA

Reported the same issue four days ago in the Macintosh forum:

http://moowrap.net/forum_thread.php?id=152

OS X 10.7.2/2011 iMac 27" i5/core client 6.13.12
Received the following error(s) in response to a request for work:

Mon Nov 21 20:33:27 2011 | Moo! Wrapper | Sending scheduler request: To fetch work.
Mon Nov 21 20:33:27 2011 | Moo! Wrapper | Requesting new tasks for CPU

Mon Nov 21 20:33:31 2011 | Moo! Wrapper | [error] Can't parse application version in scheduler reply: unexpected XML tag or syntax
Mon Nov 21 20:33:31 2011 | Moo! Wrapper | [error] No close tag in scheduler reply


--
Jon

Will also post to the BOINC Alpha email thread as a heads-up.

--
Jon

PM sent

---

Proud Member of Team [H]ard|OCP and the [H]ard DC Commandos

Hi,

I have updated to the latest server code so if this is still happening, I'm suspecting it's a alpha client bug. At least the problem is consistent since there are more than one people that are affected. :)

-w

Thanks! I'll give it a shot later tonight, and let you know.

---

Reno, NV
Team SETI.USA

FYI, the problem is still there. Or maybe it is back again. Same messages. Can't get work.

---

Reno, NV
Team SETI.USA

Latest from thread 152: (http://moowrap.net/forum_thread.php?id=152)

Received this response from David Anderson at BOINC:

Jon:
Please forward this.
Actually the bug was in update_versions.
It created bad XML in the app_version table, such as:
<version_num>102</version_name>
So you need to fix this either by
- create new app_versions (e.g. version 1.03), or
- manually editing the XML field using mysql
I recommend the first option, less error-prone.
-- David

Hope this helps.

--
Jon

--
Jon

Has this been fixed now?

---

Reno, NV
Team SETI.USA

No, I had to revert to 6.12.34 on several Box to get the Moo Wu's to run, lost work in process from other projects on the roll-back ...

---

Both my Windows and OS X hosts are now receiving, processing, and successfully returning results. Here's the thread that tracked the issue on the OS X host:

http://moowrap.net/forum_thread.php?id=152

--
Jon

I think the key could be whether your running Win 7 or not, my Win 7 Laptop & Client v7.0.2 will run the MOO CUDA Wu's but none of my Win XP Box's will run the Wu's with anything over Client v6.12.34 ...

---

No, I had to revert to 6.12.34 on several Box to get the Moo Wu's to run, lost work in process from other projects on the roll-back ...

Ouch.. :(

Odd, this specific problem should now have been fixed. At least for new/resent work since clients cache the bad app_version metadata in their client_state.xml (that metadata is fixed only after app is sent). Hmm, are you perhaps using app_info.xml that has the problem in it?

I'll still take a look in the DB if there's still bad XML around. In the meantime, if anybody is suffering this problem (or can reproduce without too much problems) I would like to see your sched_reply_moowrap.net.xml file just after a failed fetch attempt via PM. Thanks, in any case. :)

-w

Hmm, are you perhaps using app_info.xml that has the problem in it?

No, I'm not using any app_info.xml file to run the Wu's ... I get CUDA Wu's from MOO using 7.0.2 & 7.0.3 but they just don't run until I go back to 6.12.34 which then they get wiped out & new Wu's sent ...

---

I think the key could be whether your running Win 7 or not, my Win 7 Laptop & Client v7.0.2 will run the MOO CUDA Wu's but none of my Win XP Box's will run the Wu's with anything over Client v6.12.34 ...

Yeah. XP64 + 7.0.3 gets and runs MOO just fine. win7 64 + 7.0.3 will not run MOO. The task just sits there waiting.

---

Reno, NV
Team SETI.USA