Talking about weird hosts, how can a status get to look like this ?
State: All (9551) · In progress (9259) · Validation pending (0) · Validation inconclusive (0) · Valid (0) · Invalid (0) · Error (292)
Application: All (9578) · AstroPulse v7 (27) · SETI@home v8 (9551)

Usually by using an over zealous antivirus in most cases.

Cheers.

Usually by using an over zealous antivirus in most cases.
Cheers.

With not much work returned, how has he gathered well over 9000 in progress on one PC ?

---

Humans may rule the world...but bacteria run it...

Usually by using an over zealous antivirus in most cases.
Cheers.

With not much work returned, how has he gathered well over 9000 in progress on one PC ?

If you can please post the HostID so we could follow.

---

Usually by using an over zealous antivirus in most cases.
Cheers.

With not much work returned, how has he gathered well over 9000 in progress on one PC ?

Unfortunately, the auto-throttling mechanism of the schedulers doesn't work well or consistently.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Usually by using an over zealous antivirus in most cases.
Cheers.

With not much work returned, how has he gathered well over 9000 in progress on one PC ?

If you can please post the HostID so we could follow.

https://setiathome.berkeley.edu/show_host_detail.php?hostid=8158553

---

Humans may rule the world...but bacteria run it...

290 errors - all timed out. Expect the rest to time out :-(

290 errors - all timed out. Expect the rest to time out :-(

. . But the host is still contacting the servers, is it getting more work when it does ????

Stephen

??

It appears that way. Last time I checked he had 27 AP's, now got 29 :-(

It appears that way. Last time I checked he had 27 AP's, now got 29 :-(

. . That needs to be fixed ... :(

. . But how?

Stephen

??

It can't evidently. When MilkyWay tried, it messed up perfectly good hosts when they tried to get rid of the bad with the BOINC mechanism.

The BOINC code would have to be rewritten. And we know they don't have the guts to try to do so . . . . or the actual resources to do anyway.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

It can't evidently. When MilkyWay tried, it messed up perfectly good hosts when they tried to get rid of the bad with the BOINC mechanism.

The BOINC code would have to be rewritten. And we know they don't have the guts to try to do so . . . . or the actual resources to do anyway.

. . Resources would be the big issue I guess ...

Stephen

?

290 errors - all timed out. Expect the rest to time out :-(

. . But the host is still contacting the servers, is it getting more work when it does ????

It's a ghost machine- it makes ghosts.

---

Grant
Darwin NT

While an automated system may not work, this computer would be a prime target for a manual intervention - I'm pretty certain Eric has done a "forced stop" on errant computers in the past. And one with >9000 tasks in progress and not returning any results must be a prime candidate.

I'm with Glenn on this, I'd guess that the computer doesn't actually have >9000 tasks lying around, but has had >9000 lost in transit to become ghosts.

---

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

It can't evidently. When MilkyWay tried, it messed up perfectly good hosts when they tried to get rid of the bad with the BOINC mechanism.

The BOINC code would have to be rewritten. And we know they don't have the guts to try to do so . . . . or the actual resources to do anyway.

. . Resources would be the big issue I guess ...

Stephen

?

Actually Richard Haselgrove, who has regular contact with Eric as part of the PMC has stated numerous times that Eric is loathe to touch any part of the scheduler. And also he has said that the one person who might actually understand at least some of the code, (never named but I assume was referring to D.A.) really doesn't at all since the code is so ancient and the original programmers long gone.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Actually Richard Haselgrove, who has regular contact with Eric as part of the PMC has stated numerous times that Eric is loathe to touch any part of the scheduler. And also he has said that the one person who might actually understand at least some of the code, (never named but I assume was referring to D.A.) really doesn't at all since the code is so ancient and the original programmers long gone.

So it'd pretty much have to be re-written, almost from scratch.

---

Grant
Darwin NT

290 errors - all timed out. Expect the rest to time out :-(

. . But the host is still contacting the servers, is it getting more work when it does ????

It's a ghost machine- it makes ghosts.

That is what I suspected too.
Still, he gets chunks of work every day. So, when the host contacts the servers, they see the machine as being empty,
even when the host page reports over 9000 tasks in progress ?
There should be a way to report such hosts, and to fix the problem...even if it has to be done manually.

---

Humans may rule the world...but bacteria run it...

Actually Richard Haselgrove, who has regular contact with Eric as part of the PMC has stated numerous times that Eric is loathe to touch any part of the scheduler. And also he has said that the one person who might actually understand at least some of the code, (never named but I assume was referring to D.A.) really doesn't at all since the code is so ancient and the original programmers long gone.

So it'd pretty much have to be re-written, almost from scratch.

That's the gist I get out of it. Which leads back to Stephen's comment that the lack of resources is the biggest obstacle. We need a full-time system administrator ( the person tasked with contacting the bad seeds and if no reply, deleting the bad host) for keeping the servers running; a full-time developer who would rewrite the entire code base from scratch; and finally a full-time fundraiser to coordinate paying for these personnel and the operating costs.

Then the project scientists could get on with real science (like Nebula) and not have to deal with the day-to day tasks of just keeping this shoe-string budget project running.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

There should be a way to report such hosts, and to fix the problem...even if it has to be done manually.

There is already in the defacto "Invalid Host messaging" thread. But that would entail actually having staff read the thread about bad hosts and then doing something about it.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Maybe running back into our old problem of host has reached the limit of tasks in progress.

Keith-Windows7

39 SETI@home 4/16/2018 13:27:20 Sending scheduler request: To fetch work.
40 SETI@home 4/16/2018 13:27:20 Reporting 4 completed tasks
41 SETI@home 4/16/2018 13:27:20 Requesting new tasks for CPU
42 SETI@home 4/16/2018 13:27:20 [sched_op] CPU work request: 221374.89 seconds; 0.00 devices
43 SETI@home 4/16/2018 13:27:20 [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
44 SETI@home 4/16/2018 13:27:23 Scheduler request completed: got 1 new tasks
45 SETI@home 4/16/2018 13:27:23 [sched_op] Server version 709
46 SETI@home 4/16/2018 13:27:23 Project requested delay of 303 seconds
47 SETI@home 4/16/2018 13:27:23 [sched_op] estimated total CPU task duration: 5063 seconds
48 SETI@home 4/16/2018 13:27:23 [sched_op] estimated total NVIDIA GPU task duration: 0 seconds
49 SETI@home 4/16/2018 13:27:23 [sched_op] handle_scheduler_reply(): got ack for task 01ja17aa.17267.16435.14.41.253.vlar_1
50 SETI@home 4/16/2018 13:27:23 [sched_op] handle_scheduler_reply(): got ack for task 01ja17aa.16724.18889.13.40.22.vlar_1
51 SETI@home 4/16/2018 13:27:23 [sched_op] handle_scheduler_reply(): got ack for task 07ja17aa.2453.407059.9.36.7_1
52 SETI@home 4/16/2018 13:27:23 [sched_op] handle_scheduler_reply(): got ack for task blc14_2bit_guppi_58137_27894_HIP45839_0015.9893.818.22.45.20.vlar_2
53 SETI@home 4/16/2018 13:27:23 [sched_op] Deferring communication for 00:05:03
54 SETI@home 4/16/2018 13:27:23 [sched_op] Reason: requested by project
55 SETI@home 4/16/2018 13:27:25 Started download of 09ja17aa.20243.2938.9.36.95
56 SETI@home 4/16/2018 13:27:28 Finished download of 09ja17aa.20243.2938.9.36.95
57 SETI@home 4/16/2018 13:32:29 [sched_op] Starting scheduler request
58 SETI@home 4/16/2018 13:32:29 Sending scheduler request: To fetch work.
59 SETI@home 4/16/2018 13:32:29 Requesting new tasks for CPU
60 SETI@home 4/16/2018 13:32:29 [sched_op] CPU work request: 217778.85 seconds; 0.00 devices
61 SETI@home 4/16/2018 13:32:29 [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
62 SETI@home 4/16/2018 13:32:32 Scheduler request completed: got 0 new tasks
63 SETI@home 4/16/2018 13:32:32 [sched_op] Server version 709
64 SETI@home 4/16/2018 13:32:32 No tasks sent
65 SETI@home 4/16/2018 13:32:32 This computer has reached a limit on tasks in progress

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Maybe running back into our old problem of host has reached the limit of tasks in progress.

Apparently not. Just a sort hiccup it appears. Anybody want to guess the length of the outage tomorrow? Short or normal?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)