Is there a way to abort pending tasks when I no longer have the hardware (and client) for those tasks?

The BOINC server will eventually abort them when they time out, but I want to be considerate of my wingman. Someone out there is waiting for their tasks to validate, and I've got about 40 tasks hanging in the queue waiting to time out.

---

Go to BOINC manager and go to the "View" tab, and punch up "advanced" Go to the tasks tab, click on it an all your tasks will show. Use the "show all tasks tab". Put your cursor on the task tp abort and highlight it. Then go to the left side "commands" bar and click "abort".

Do it for all tasks you wish to abort, then run an update.

Perhaps setting NNT (No New Tasks) before doing such a thing as well and next enable it once again before pressing update for any new tasks could perhaps also help.

Really not sure here, but perhaps may not be a bad thing.

Fidel,

Unless the hard drive in question is toast (in which case you'd be right), you can move hardware around to accomplish this.

Folks cook GPUs and motherboards all the time. The gentlemen didn't specify what hardware was the problem.

With 10+ systems crunching at any one time, I swap components all the time.

Enjoy your cigar.

The first line of the OP's post quite clearly states he no longer has the hardware, so it is impossible for him to set No New Tasks, or anything else that is reliant on accessing the HDD.
Unfortunately if you no longer have that drive, or it is failed, there is nothing you can do apart from letting the tasks time out.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I normally run machines dry of tasks or abort them manually. But this was an unexpected loss that left a bunch of tasks hanging.

---

Exactly. If I had merely fried a motherboard or GPU, I'd just be swearing for a few hours fixing it. In this case I no longer have any of the hardware, to include the hard drive. To be more precise, I no longer have access to it.

However, all I am worried about is leaving other crunchers hanging until those tasks time out.

---

Exactly. If I had merely fried a motherboard or GPU, I'd just be swearing for a few hours fixing it. In this case I no longer have any of the hardware, to include the hard drive. To be more precise, I no longer have access to it.

However, all I am worried about is leaving other crunchers hanging until those tasks time out.

Unfortunately the BOINC designed method is to let the tasks timeout.

Supposedly it is possible to modify a client_state.xml in order to get the server to abandon the tasks for a host, but I've never gotten it it actually work.

I decided it was easier to backup my BOINC data folder when the host had 0 tasks on hand. That way if I ever lost the drive or system I could load the data folder on another system to clear out the tasks & continue where the previous had left off.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

After some thought, there is a way, but you would have to have a new set of hardware and name it the exactly same as the defunct system . Log on to seti under the same user account/password and add the system. After the handshake and file download, the old files would show as abandoned. If the hardware is dissimilar, seti might show it as a second computer and you might have to do the merge.

It worked just last week when I had to replace a hard drive and OS for BOINC2 in my stable. The one "pending" task went to "abandoned" in the error file and went back in the queue.

I think it's a problem where the the solution is more trouble than it's worth.

The system is designed to cope with individual machines dropping dead, being sold on short notice, catching fire etc . That mechanism is that they time out, and get sent to someone else. The original Wingman doesn't lose out, just some credits get left in "pending" for a month or 2. Most of us have a few of those, and they come through in due course.

Of course setting no new tasks, or running a small cache in a machine you expect to "go away" is sensible, just so you don't clutter up the system with hundreds of tasks that are going to time out. But even if your whole week cache gets lost, the real world effect is basically, nothing.

So if someone is stressing over having to wait 7 weeks to get some SETI credits... They should probably seek professional help for their OCD...

4 months is generally the longest I have to wait, and it's usually only 1 or 2 WUs that take that long.

---

Grant
Darwin NT