Posts by AMDave
|
1)
(Message 182)
Posted 3 Sep 2012 by AMDave Post: down to 6 now. fetching more popcorn :) |
|
2)
(Message 178)
Posted 2 Sep 2012 by AMDave Post: Finished mine but it looks like it just went right on out again http://asteroidsathome.net/boinc/workunit.php?wuid=8172 multiple error and inconclusive results. If there are a few WUs like this, it would explain why they are taking so long to finish. |
|
3)
(Message 176)
Posted 2 Sep 2012 by AMDave Post: at 2 and 15 I still have 1 in progress. |
|
4)
(Message 174)
Posted 2 Sep 2012 by AMDave Post: That stat on the server page is informative. I have 1 re-send which is at 55% at 16 hrs, but no other tasks from this project. So that means I must be the 1 user in the last 24 hours. But I account for only 1 of the 17 tasks in progress. So who has the other 16? Perhaps they may have detached the project and that's why their client has not contacted the server in the last 24hrs? (or maybe a laptop that is turned off?) |
|
5)
(Message 173)
Posted 2 Sep 2012 by AMDave Post: Now down to 1 and 17. There's nowhere to hide. :P I hope they are crunching them. |
|
6)
(Message 172)
Posted 1 Sep 2012 by AMDave Post: Now down to 2 and 19. |
|
7)
(Message 171)
Posted 1 Sep 2012 by AMDave Post: Down to 3 users and 19 tasks. We can wait or you can kill the tasks, shorten the deadline and re-issue them for us to complete pronto. |
|
8)
(Message 170)
Posted 1 Sep 2012 by AMDave Post: Add WU 4735 to the list |
|
9)
(Message 106)
Posted 17 Jul 2012 by AMDave Post: I do not have any BOINC signal 11's because I follow this advice on my 64-bit systems that are running 32-bit clients (or 64-bit clients that still have 32-bit libs hooked to them) on my 64-bit systems: http://boincfaq.mundayweb.com/index.php?view=459&language=1 If you install Ia32 libs on your 64 bit system, most often this problem goes away. If it does not, then you need to take the initial advice on the contents and start swap-out testing your RAM, un-O/C-ing your rig, etc. to locate the source of the issue. But most often it is from running 32-bit apps on a 64-bit system without providing the 32-bit libs that the 32-bit client was compiled under. YAY! for the maintainers of the Ia32 libs! Good job lads. PS - another thanks to Jorden (wherever he is now) who tested and posted that back in 2008. It is intriguing that the problem continues to the present day. I think someone really should put a catch() in front of that throw() and tell the developer / user that this is what the problem is instead of expecting folks to interpret the error ID. But that's just me. HTH AMDave |
|
10)
(Message 77)
Posted 2 Jul 2012 by AMDave Post: Good reporting & deduction guys. I was still trying to figure out what was going on. Good change, Kyong. I have re-enabled my clients. |
|
11)
(Message 59)
Posted 25 Jun 2012 by AMDave Post: Validator appears to be working better than before: http://asteroidsathome.net/boinc/results.php?hostid=124&offset=0&show_names=0&state=3&appid= Queue shows 5,965 ready to send on the server status page: http://asteroidsathome.net/boinc/server_status.php The newest set of WUs are much longer than the previous set, so the rate of return has reduced. This in turn has affected the rate of uptake of WUs from the queue. So supply appears greater than demand at this moment. No reason to expect your wing-man WU will not get re-sent. It may take some time to go out, but may be done on a faster CPU (based on probability) so you should not have to wait uncomfortably long. If you run close to completion limit, just abort and the server will re-issue the WU to someone else. If you over-run the limit it will re-issue the WU to someone else anyway. HTH |