Have changed BOINC installation to not run as service. The outage is coming soon and this systeem needs a lot of jobs ;-)

You could try moving work over from the GPU to the CPU.
Start with a small number, this should get you GPU work as well.

Thats exactly what I am doing, but still not getting (requesting) any work :-(

---

Have changed BOINC installation to not run as service. The outage is coming soon and this systeem needs a lot of jobs ;-)

You could try moving work over from the GPU to the CPU.
Start with a small number, this should get you GPU work as well.

Thats exactly what I am doing, but still not getting (requesting) any work :-(

I just trashed by work when the Client shut down and restarted itself automatically. But I now got 550+ already, more than enough.
Not requesting work is mostly another problem. There is plenty of work and the limits are gone.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

Have changed BOINC installation to not run as service. The outage is coming soon and this systeem needs a lot of jobs ;-)

You could try moving work over from the GPU to the CPU.
Start with a small number, this should get you GPU work as well.

Thats exactly what I am doing, but still not getting (requesting) any work :-(

Probably now new work because of the number of errors you are getting.
http://setiathome.berkeley.edu/results.php?hostid=4414471&offset=0&show_names=0&state=5
Shows a lot of -226 errors on both CPU and GPU (CUDA).

ERR_TOO_MANY_EXITS -226

An application has exited prematurely (unexpectedly) more than 99 times without generating a checkpoint, so giving up on that task.

I see you are using 6.10.58 - have you recently upgraded to this version and now get these problems and from which version? Try downgrading?

---

GPU Users Group

After a few hours (?) just started getting new work !!! :-)

---

V 1.1

Warning: Make sure the BOINC Manager is shut down before rescheduling. It restarts the BOINC client on some computers.

Changed: A slightly different way to start the BOINC client.
Fixed: When the CPU or GPU was out of work, it sometimes refused to reschedule.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

I got those errors after rescheduling as i mentioned a few posts earlier.
All my CPU jobs errored out.

Running 6.10.58 on some systems now without any problem. Seems to be a good stable version.

Have changed BOINC installation to not run as service. The outage is coming soon and this systeem needs a lot of jobs ;-)

You could try moving work over from the GPU to the CPU.
Start with a small number, this should get you GPU work as well.

Thats exactly what I am doing, but still not getting (requesting) any work :-(

Probably now new work because of the number of errors you are getting.
http://setiathome.berkeley.edu/results.php?hostid=4414471&offset=0&show_names=0&state=5
Shows a lot of -226 errors on both CPU and GPU (CUDA).

ERR_TOO_MANY_EXITS -226

An application has exited prematurely (unexpectedly) more than 99 times without generating a checkpoint, so giving up on that task.

I see you are using 6.10.58 - have you recently upgraded to this version and now get these problems and from which version? Try downgrading?

---

Will try this version after the current outage. (and reporting)

---

Will try this version after the current outage. (and reporting)

Hey HansR!
Always nice to see another Dutch Power Cow on the forum :P

---

Rig name: "x6Crunchy"
OS: Win 7 x64
MB: Asus M4N98TD EVO
CPU: AMD X6 1055T 2.8(1,2v)
GPU: 2x Asus GTX560ti
Member of: Dutch Power Cows

V 1.2

Add: A block on the BOINC client, to run while rescheduling. The BOINC Manager sometimes restarts the client.
Add: A warning in the log, when the BOINC Manager is running.
Add: Rescheduling now uses the CPU and GPU ratio. The ratio is used by SETI to correct runtime estimates.
Changed: Rescheduling on the regular SETI installation is now permitted. (With two different plan classes running).
Fixed: Several small bugs

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

V 1.2

Add: A block on the BOINC client, to run while rescheduling. The BOINC Manager sometimes restarts the client.
Add: A warning in the log, when the BOINC Manager is running.
Add: Rescheduling now uses the CPU and GPU ratio. The ratio is used by SETI to correct runtime estimates.
Changed: Rescheduling on the regular SETI installation is now permitted. (With two different plan classes running).
Fixed: Several small bugs

What happens now that VLAR's don't go to GPU's?

---

- Jarryd

Version 1.2 crushes something: after rescheduling BOINC manager sees no projects at all, no clients running.

Repair BOINC installation fixes the problem: everything is back: projects, clients running.

Running the rescheduler V 1.2 again: same problem.

Repair fixes this again.

Switched back to V 0.9: no problem.

---

Repair BOINC installation fixes the problem: everything is back: projects, clients running.

Perhaps an "Advanced/Select Computer..." would have done it too?

Or a "File/Exit" and restart of the manager?

Gruß,
Gundolf

V 1.3

Fixed: Program crashes when SETI beta is present and regular SETI is out of work, after pressing Run, even when no rescheduling is required.
Fixed: Sometimes the BOINC client was blocked from running.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

Version 1.2 crushes something: after rescheduling BOINC manager sees no projects at all, no clients running.

Repair BOINC installation fixes the problem: everything is back: projects, clients running.

Running the rescheduler V 1.2 again: same problem.

Repair fixes this again.

Switched back to V 0.9: no problem.

Too much protection didn't allow the boinc client to run.
1.3 fixed that, but closing the rescheduler unlocks everything as well.
A repair shouldn't be necessary. as there is nothing wrong with the state file.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

Neither the "select computer" nor the restart did fix it.
Closing the scheduler might have solved it.

I can't try V 1.3 till monday, because my remote login get stuck if I try to download the rescheduler.

---

V 1.4

Add: Other tab, for rescheduling other tasks like Astropulse -> ATI GPU.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

Hi Fred
A couple of suggestions.
1) An option NOT to restart BOINC after a reschedule. Sometimes for maintenance purposes I use your app while the client is not running and do not want it to restart afterwards.

2) An easier way to move all the units to the CPU (similar in operation to Marius's slider bar ). Once again this is for maintenance purposes.

There are times, e.g. When changing the CUDA app version or video card that you need to be able to do things this way to avoid trashing units.

You may have already added these, I'm still using V0.6. It's been hard to keep up with as things have been changing so rapidly. :-)

Thanks for your efforts on this.

T.A.

What happens if these two options are conflicting?:

"If GPU tasks are less than" 40 "fill up to" 60 "Tasks": Moves tasks to the GPU when the current total is less than 40. Move enough tasks to end up with 60 tasks.
"If CPU tasks are less than" 20 "fill up to" 30 "Tasks": Moves tasks to the CPU when the current total is less than 20. Move enough tasks to end up with 30 tasks.

Will it loop e.g. if you have total of 62 tasks
GPU: 20 - CPU: 42 -> GPU fill to 60 =
GPU: 60 - CPU: 2 -> CPU fill to 30 =
GPU: 32 - CPU: 30 -> GPU fill to 60 =
GPU: 60 - CPU: 2 -> CPU fill to 30 =
..........

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

What happens if these two options are conflicting?:

"If GPU tasks are less than" 40 "fill up to" 60 "Tasks": Moves tasks to the GPU when the current total is less than 40. Move enough tasks to end up with 60 tasks.
"If CPU tasks are less than" 20 "fill up to" 30 "Tasks": Moves tasks to the CPU when the current total is less than 20. Move enough tasks to end up with 30 tasks.

Will it loop e.g. if you have total of 62 tasks
GPU: 20 - CPU: 42 -> GPU fill to 60 =
GPU: 60 - CPU: 2 -> CPU fill to 30 =
GPU: 32 - CPU: 30 -> GPU fill to 60 =
GPU: 60 - CPU: 2 -> CPU fill to 30 =
..........

The GPU will take first pick. What's left is for the CPU.
It takes account for the minimum on both GPU and CPU.
You can simply try by pressing test.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

Hi Fred
A couple of suggestions.
1) An option NOT to restart BOINC after a reschedule. Sometimes for maintenance purposes I use your app while the client is not running and do not want it to restart afterwards.

2) An easier way to move all the units to the CPU (similar in operation to Marius's slider bar ). Once again this is for maintenance purposes.

There are times, e.g. When changing the CUDA app version or video card that you need to be able to do things this way to avoid trashing units.

You may have already added these, I'm still using V0.6. It's been hard to keep up with as things have been changing so rapidly. :-)

Thanks for your efforts on this.

T.A.

1) I can do, will add a START and STOP button and a check not to start the client. You could also use the simulation mode and move over the new client state when needed.
2) There is a reason. The Server keeps tab on the CPU and GPU work, with a slider you keep moving work from one to another too easily.
The approach I took tries to schedule as little as possible. It's less confusing for the Server and doesn't mess the correction ratio's, that will be switched on anytime.

A reason to update, there are some bug fixes in later version.......

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.