Each of my eligible computers is listed as have several hundred WUs issued/assigned but none of the listed WUs actually exist on the target computers. I've RESET and DETACHED/ATACHED each device with no change in the WUs listed at the MOO Wapper site.

An example of this scenario is: (http://moowrap.net/results.php?hostid=6210). None of the listed WUs exist on the specified host. This issue exists across all eligible hosts (Windows and OS X).

Thanks in advance for any assistance with this issue.

--
Jon

Each of my eligible computers is listed as have several hundred WUs issued/assigned but none of the listed WUs actually exist on the target computers. I've RESET and DETACHED/ATACHED each device with no change in the WUs listed at the MOO Wapper site.

An example of this scenario is: (http://moowrap.net/results.php?hostid=6210). None of the listed WUs exist on the specified host. This issue exists across all eligible hosts (Windows and OS X).

Thanks in advance for any assistance with this issue.

--
Jon

I had similar concerns.switched back to 6.12.34,now getting work.

---

"I always win law permanently"

Thanks for the feedback and confirmation of a possible general work distribution issue. I'm committed to providing test beds for alpha and development level BOINC core client releases so I'll stick it out and look to bridge the testing feedback loop between the BOINC developers and projects like Moo! Wrapper.


--
Jon

An example of this scenario is: (http://moowrap.net/results.php?hostid=6210). None of the listed WUs exist on the specified host. This issue exists across all eligible hosts (Windows and OS X).

Looking at that particular host, it seems to have lost it's previous tasks (probably via a reset) and scheduler has been sending (and expiring some non-suitable ones) it these work when it has been contacting us to get more work around 18-20 Dec.

A reset wouldn't "solve" this as that just makes your client forget the work it has and our scheduler, that has a long memory, would just resent them next time you it asks.

Do you see anything bad happening due to these ghost tasks or was that just an observation and/or concern that there's something wrong? Ghost work should eventually get resent to your host or expired (which hopefully doesn't count as an error and decrease your quota) and sent to somebody else (or even you).

-w

With the change to correct the "unexpected XML tag or syntax" issue, I received new WUs for my OS X host. I'll continue to monitor the Windows hosts but expect that they will also start receiving new WUs in due course.

Thanks.

--
Jon