Only Errors !!! |
| log in |
Message boards : Number crunching : Only Errors !!!
| Author | Message |
|---|---|
|
Hello | |
| ID: 1324 · Rating: 0 · rate:
| |
|
Within the last couple weeks our servers weren't delivering our apps properly, including our lisp app (Steel Bank Common Lisp -SBCL). The errors you are getting are with running our lisp application, so try detaching and reattaching the project to see if you can download the lisp app correctly. Then let me know if you still get these errors. | |
| ID: 1326 · Rating: 0 · rate:
| |
|
Hello | |
| ID: 1338 · Rating: 0 · rate:
| |
|
I too am getting error messages. I looked back and have been getting this error since January 19th when I started again but was fine for the most part before December 11th. Anything with the client 6.4.5 and later has just errored out. | |
| ID: 1346 · Rating: 0 · rate:
| |
|
I have this exact same problem. Every single WU fails. I'm running Vista x64 SP1, BOINC 6.6.20. I've tried resetting the project, but it didn't help. | |
| ID: 1370 · Rating: 0 · rate:
| |
|
Try setting your configuration so that only one or two workunits are running in parallel. There may be a problem with running multiple iterations of the SBCL progam concurrently in Vista. | |
| ID: 1382 · Rating: 0 · rate:
| |
Try setting your configuration so that only one or two workunits are running in parallel. There may be a problem with running multiple iterations of the SBCL progam concurrently in Vista. And how do you propose to do this? I have asked the BOINC developers to allow this option for several years, and it seems they are clueless on how to achieve this. I really should not be hard to do. Once work is cached, BOINC will decide when to run the work, and how many concurrent WU's of a particular project to run at a time based on number of cores, debt, and priority. But no way to tell BOINC to run project x on core 0, project y on core 1, project z on core 2, etc... The only way to limit it currently is to set your BOINC to run on a single core, leaving the others non productive. | |
| ID: 1384 · Rating: 0 · rate:
| |
|
Try reducing how much memory your BOINC client uses when running a job. It that works, we'll at least know it's a problem with running multiple iterations of lisp on some Vista clients. | |
| ID: 1388 · Rating: 0 · rate:
| |
|
Crashing every WU on every machine. | |
| ID: 1396 · Rating: 0 · rate:
| |
|
The new DSST_6-3 work units seem to get stuck after about 21 minutes (on my 1.86Ghz E4300) and then the CPU utilization goes to zero. This is on 32-bit Unbuntu Linux. System Monitor shows the process is sleeping on futex_wait. I'm having to abort them when they stop running. Not sure if all of them are going to do this. The To Completion time keeps increasing, but the CPU time stops increasing. Looks like some kind of deadlock. | |
| ID: 1419 · Rating: 0 · rate:
| |
|
Same here using sidux 64-bit and boincmanager 6.4.5. | |
| ID: 1427 · Rating: 0 · rate:
| |
|
Sorry for the errors. We've had to delete that model from our jobs queue, because it is proving difficult to run on our volunteers. If you're computer has currently downloaded workunits with the "DSST_6" prefix, abort them immediately. | |
| ID: 1428 · Rating: 0 · rate:
| |
|
And it's not just the Linux/unix WUs. All Windows WUs are going to completion with error. I've set the project to no new tasks until someone can confirm the problems have been fixed. | |
| ID: 1429 · Rating: 0 · rate:
| |
|
Must have been typing when you were! The server status shows 24k results ready to send. Are all of those going to be aborted? Just wondering when I can let in new WUs. | |
| ID: 1430 · Rating: 0 · rate:
| |
|
Wooah! Thanks for bringing the "24k workunits" to my attention. The DSST_6 model was aborted last Friday but it appears that the workunits were not destroyed along with it. | |
| ID: 1432 · Rating: 0 · rate:
| |
|
Noticed a lot of new work. However, on 32-bit Ubuntu, it only gets to 38.999% and then CPU time stops incrementing. I'm having to abort these as I have no idea when they would even decide to give up. They ran a few minutes only (to 38.999%), and then showed the to completion as 7+ hours and growing. | |
| ID: 1448 · Rating: 0 · rate:
| |
|
Hi Gary, | |
| ID: 1449 · Rating: 0 · rate:
| |
|
So Tom, | |
| ID: 1450 · Rating: 0 · rate:
| |
Message boards :
Number crunching :
Only Errors !!!