2893 in play.
2162 pending.
59 dunnos....inconclusive.
1756 valid.

But I now show 39 errors.
Which are listed as 'abandoned'...
And not just on one rig, but across several.
WTF, Chuck?

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

You have some marked 'Abandoned' I see.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I just noted that.............
And the problem is that it is not just one rig gone down........

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Comms glitch - snow on the line?

We (Jason, William, and I) did get a scheduler change committed to reduce the chances of that - we can ask Eric/David on Monday whether the new scheduler was built from that updated code, or from a local copy.

You have some marked 'Abandoned' I see.

Same thing here across several machines at the same time.

---

Comms glitch - snow on the line?

We (Jason, William, and I) did get a scheduler change committed to reduce the chances of that - we can ask Eric/David on Monday whether the new scheduler was built from that updated code, or from a local copy.

Do that.......
The kitties are not in the Seti business to abandon or error tasks.
Need an answer for these.
The only time in the past that I have had 'abandoned' tasks is a rig gone down with an OS crash, and that is certainly not the case at this time.

Meow?????????

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

"Abandoned tasks" are not an installer issue. Perhaps we could ask a friendly mod to fork this thread?

"Abandoned tasks" are not an installer issue. Perhaps we could ask a friendly mod to fork this thread?

Then tell me how they occured.........across several different hosts.
How?

Before you put a fork in it.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Please read 4222d744e88163a4b02d269349c51cd22d6826ca and Suddenly BOINC Decides to Abandon 71 APs...WTH? to get an idea what we're wrestling with.

It IS an installer issue if somehow the apps distributed thereby have caused the problem.
Do not whitewash this.
I run 9 very dedicated hosts on this project.
39 errors IS an issue.

I am asking for analysis of it.
Not washing your hands of it.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Please read 4222d744e88163a4b02d269349c51cd22d6826ca and Suddenly BOINC Decides to Abandon 71 APs...WTH? to get an idea what we're wrestling with.

The first link has to do with linux, no bearing.

The second seems to blame server comms issues? That I can believe.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

The first link has to do with linux, no bearing.

Yes, that's David's style - mix up two separate subjects in one commit. Many of the other developers have complained about that.

But read the second paragraph too:

- Scheduler: in no-host-ID case, don't mark results as "detached"
if request contains any in-progress results

That was William's work - though you need to know how to switch between BOINC and GitHub repositories to follow the trail of breadcrunbs.

OK...calming down now.
The errored tasks are tagged as being reported on December 26th???
On several different rigs?

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

OK...calming down now.
The errored tasks are tagged as being reported on December 26th???

Um, yes, that might be a clue ;)

On all machines? You can see a combined list, I have to step through them host by host. The ones I'm seeing were setiathome_v7, too.

OK...calming down now.
The errored tasks are tagged as being reported on December 26th???

Um, yes, that might be a clue ;)

On all machines? You can see a combined list, I have to step through them host by host. The ones I'm seeing were setiathome_v7, too.

Of course....I only installed v8 when it came out, had not messed with any pre release things before that.

'Tis a puzzlement that they seem to have showed up just now.

NOT a v8 issue, and I am sorry for injecting it into the v8 realm.

My bad....my v8 task list still shows no warrants, no wants....LOL.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

To be fair, problems between the Installer and previous Beta applications - such as reported by Ageless yesterday - can result in tasks showing as abandoned. But that would happen at the moment of installation, not days or weeks later - or earlier ;)

To be fair, problems between the Installer and previous Beta applications - such as reported by Ageless yesterday - can result in tasks showing as abandoned. But that would happen at the moment of installation, not days or weeks later - or earlier ;)

The installer is perfecto.
Nothing to see here now...please move along...LOL.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Mine don't show as abandoned, not yet. BOINC just discarded them, they'll stay in my task list until they time out.

Funny side thing is that the tasks are actually also still in the ..\projects\setiathome.berkeley.edu\ folder. Had I time to manually edit the client_state.xml file, I could probably add them back in. But not really interested in doing so.

---

You could try the "report the same task twice" trick, when requesting new work - that triggers a one-time 'resend lost tasks', even though it's switched off by the project.

That should rebuild client_state.xml, 20 tasks at a time, if you request enough.

You could try the "report the same task twice" trick, when requesting new work - that triggers a one-time 'resend lost tasks', even though it's switched off by the project.

That should rebuild client_state.xml, 20 tasks at a time, if you request enough.

I did that several days ago to recover four v7 tasks that had been inadvertently dumped when I added v8 to the app_info on my old ThinkPad at the beginning of the month (due to my botching of a simple cut and paste operation). It actually took a couple attempts, as the first one only returned one of the lost tasks, since that was all that was needed to fill the queue. A few days later, before the second attempt, I first bumped up the size of the work buffer and then successfully got the remaining three v7 tasks back. Pretty neat trick when "resend lost tasks" is turned off!

---