I've (this morning) changed some server settings which should help to get rid of orphans and phantom results.

Please let me know if you are still seeing these.

Eric

---

@SETIEric@qoto.org (Mastodon)

Result 219876056 from Feb 2006, has no WU 52570717.

Does this count?

---

My movie https://vimeo.com/manage/videos/502242

Some users appear to heve felt it in their nether regions. I havem't felt the pain yet.

Long as I can see the Light......

Oops. thats from another post in the Cafe.

---

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

This one is just hanging out there since 6 Jun 2006? Too many errors.80831620

---

SETI Classic Stats:
Workunits processed 28,419
Total CPU time 216,314 hours

I'm down to three. All are results with no associated WU.
221555221
221368611
221368609

08/06/2007 23:29:00|SETI@home|Scheduler RPC succeeded [server version 509]
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 14fe05aa.4646.17872.22154.3.254_1
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 15mr05aa.23822.7570.292318.3.156_1
08/06/2007 23:29:00|SETI@home|Message from server: Didn't resend lost result 15mr05aa.24057.14082.86072.3.135_0 (expired)
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 15mr05aa.24057.14129.804838.3.236_1
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 15mr05aa.24057.14386.67340.3.142_1
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 05mr05aa.16336.22449.679838.3.214_2
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 15mr05aa.10014.14433.786080.3.13_0
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 14fe05aa.2059.22050.311076.3.137_1
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 05mr05aa.2917.22834.98570.3.241_2
08/06/2007 23:29:00|SETI@home|Message from server: Didn't resend lost result 05mr05aa.5065.22929.486066.3.144_1 (expired)
08/06/2007 23:29:00|SETI@home|Message from server: Didn't resend lost result 14fe05aa.15458.22816.222162.3.59_2 (expired)
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 05mr05aa.14525.23266.242328.3.218_2
08/06/2007 23:29:00|SETI@home|Message from server: Resent lost result 05mr05aa.28809.24002.373564.3.175_0
08/06/2007 23:29:00|SETI@home|Deferring communication for 11 sec

Looks good to me. Can you tell how many additional WU's this freed up?

---

Wow - who you gonna call?

Ghostbusters.

2 of my hosts had ghosts, and they all appear to be
either gone, or not ghosts anymore, but they took
2 different paths to that end.

One seems to have had all the ghosts have their
deadline set to "right now" (all at the same time
in the UTC PM of 6/8),so they all expired. Done!
No other action relative to those units, near as I
can tell.

The other host got the same thing, each ghost getting
expired at a single time (whenever the Ghostbuster hit
that host, couple of hours away from when the other host
got cleaned up) But a bunch of them got resent to that
host, apparently because that host picked that same
time to request 66 seconds of work. There were messages
like the previous post (about either resending or not
resending lost results) in response to my host request
for 66 seconds of work. But, the ones that did get
resent totalled something like 200-300 hours!!
i.e., sent a lot more than what's needed for 66 secs.

Looks like it'll be able to crunch them all, and in this
case too much work is, at least, a good problem to
have. So, we'll be crunching on over here!

Dave

(edit)
Digging back thru messages, I now see that my first
host did actually have the same response, I just didn't
notice it. It is a lot faster host, so the handful of
units that did get resent did not represent a large
(relatively) bulge in work on hand, and that excess has
already burned off. So the timing thing of the work
request was not a coincidence - apparently the Ghostbuster
process waits until you request, and then springs into action.

I had three of them, they all vanished today and all is clean now. Many thanks Eric.

---

I had three of them, they all vanished today and all is clean now. Many thanks Eric.

In fact, they does not vanished, they was resent to me and are ready to crunch now. Good job !

---

The two Ghosts that I had, (which I originally reported in my "Ghosts, Ghosts, and more Ghosts" Thread), have been killed off of my "Results" Page. As of today, they have been marked as "No Reply".


WU: 16fe05ab.10775.10880.397176.3.166

Excalibur, Computer 2244330: 1St "No Reply".


WU: 04mr05ab.8726.13154.304840.3.23

Excalibur, Computer 2244330: 2Nd "No Reply".


So, no more Ghosts in my Results Page. Hopefully no new Ghosts will follow. 8-D

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I still have old ghosts:
http://setiathome.berkeley.edu/results.php?userid=8295849&offset=220
And the next few pages

previous page has compute errors stemming from switching versions of the optimized client mid-WU (even though I had suspended processing), but I'm willing to live with those;).

I have 265 "results" right now, which seems rather high as compared to my old throughput at least. It seems a lot of WUs only have me (or 2) users that are complete with processing, which seems unusual.

Additionally, my client was chugging along fine for a week or two with downloading new workunits, but now has suddenly failed to fill up its queue.

Here are present messages:
6/12/2007 7:38:16 AM|SETI@home|Requesting 345600 seconds of new work, and reporting 35 completed tasks
6/12/2007 7:38:46 AM|SETI@home|Scheduler RPC succeeded [server version 509]
6/12/2007 7:38:46 AM|SETI@home|Deferring communication for 11 sec
6/12/2007 7:38:46 AM|SETI@home|Reason: requested by project
6/12/2007 7:38:46 AM|SETI@home|Deferring communication for 59 min 19 sec
6/12/2007 7:38:46 AM|SETI@home|Reason: no work from project
6/12/2007 7:48:51 AM|SETI@home|Sending scheduler request: Requested by user
6/12/2007 7:48:51 AM|SETI@home|Requesting 345600 seconds of new work
6/12/2007 7:50:01 AM|SETI@home|Scheduler request failed: HTTP service unavailable
6/12/2007 7:50:01 AM|SETI@home|Deferring communication for 2 hr 9 min 5 sec
6/12/2007 7:50:01 AM|SETI@home|Reason: scheduler request failed

Also, last night it decided on its own to re-run the benchmarks (when it had no work to process):
6/11/2007 8:50:50 PM|SETI@home|Requesting 345600 seconds of new work, and reporting 35 completed tasks
6/11/2007 8:50:55 PM|SETI@home|Scheduler request failed: couldn't resolve host name
6/11/2007 8:50:55 PM|SETI@home|Deferring communication for 44 min 42 sec
6/11/2007 8:50:55 PM|SETI@home|Reason: scheduler request failed
6/11/2007 9:10:36 PM||Running CPU benchmarks
6/11/2007 9:10:36 PM||Suspending computation - running CPU benchmarks
6/11/2007 9:11:37 PM||Benchmark results:
6/11/2007 9:11:37 PM|| Number of CPUs: 2
6/11/2007 9:11:37 PM|| 2228 floating point MIPS (Whetstone) per CPU
6/11/2007 9:11:37 PM|| 4655 integer MIPS (Dhrystone) per CPU
6/11/2007 9:11:38 PM||Resuming computation


Previously these were the stats
6/6/2007 9:10:35 PM|| 2239 floating point MIPS (Whetstone) per CPU
6/6/2007 9:10:35 PM|| 4619 integer MIPS (Dhrystone) per CPU

Does it re-run every 5 days at the same time?

Yes, the benchmarks run every five days at roughly the same time as long as the host is up at that time. If it is off and the benchmark time has passed, they will run as soon as it's turned on again.

I looked at your current host summary, and it seems like there were two ghost resends at the very end which have completed. If you had more they must have been purged already, most likely because they weren't needed to complete the WU.

HTH,

Alinator

I looked at your current host summary, and it seems like there were two ghost resends at the very end which have completed. If you had more they must have been purged already, most likely because they weren't needed to complete the WU.

HTH,

Alinator

Ahh...it must have had something to do with an orphaned host from when I updated BOINC and S@H. It thought my computer was new. The 35 or so ghosts were from my old host number. So...now that I have merged, those old ghosts should be able to either purge or be resent to me:) I'll check on it tonight when I dial that computer in again. Still no new workunits issued to me today though:(

Hello!

result list seems to be clean, but funny WUs on the end of the list.

6 WUs, all from February 2nd, 2006. I can see results (so it is still
filling up some disks and tables) but WU is no more available.

Maybe an quick clean-up to unload dB even more?

73

Iztok



220209372 52622047 2 Feb 2006 12:33:19 UTC 11 Feb 2006 6:22:53 UTC Over Success Done 11,115.81 16.40 21.42
220201162 52650133 2 Feb 2006 12:23:06 UTC 11 Feb 2006 6:22:53 UTC Over Success Done 11,023.60 16.26 33.08
219848210 52563967 2 Feb 2006 5:01:34 UTC 11 Feb 2006 6:22:53 UTC Over Success Done 10,742.95 15.85 19.72
219848202 52563961 2 Feb 2006 5:01:34 UTC 11 Feb 2006 6:22:53 UTC Over Success Done 9,832.13 14.51 21.15
219848198 52563958 2 Feb 2006 5:01:34 UTC 11 Feb 2006 6:22:53 UTC Over Success Done 10,726.71 15.83 20.60
219837818 52561434 2 Feb 2006 4:51:19 UTC 11 Feb 2006 6:22:53 UTC Over Success Done 10,557.96 15.58 32.26

I have a workunit that was crunched back in January, and it shows that four of us completed it that month. It's keeping me from deleting an old host. ID# 109013436

---

I have a workunit that was crunched back in January, and it shows that four of us completed it that month. It's keeping me from deleting an old host. ID# 109013436

It will eventually go away on its own. Give it another few months. It isn't hurting anything, nor does it affect your scores.

---