Glad to hear you've gotten work.

In two weeks when those ghost WUs aren't returned, they'll be marked as errors and you may notice a reduction in your quota. Nothing to be done about this but to continue to return good WUS. For each good WU returned your quota will double, so it it's down to 1/cpu/day, return one and it's 2, then 4, then 8 and you'll quickly be back up to 100.

tony

Thanks Tony,

I will watch out for the slow-down; I'll know what's happening so it shouldn't be a problem.

Regards,
Bill_Mole

---

I have BOINC Manager 5.2.8
Most recently I was running SETI 4.18
I have 6 beta units, enough for about 5 days, running on 5.12

I assume 4.18 will update automatically when it's ready.

At about the time noted I tried resetting and then detaching/reattaching SETI (manually) to try and "shake some Work Units loose", which explains the messages above.

I also tried some manual updates - with similar lack of success. Then I saw this thread and decided to join in.

Regards,
Bill_Mole

Hi Michael & Mmciastro,

I applied patience and waited - and lo and behold 20 work units turned up in the last 15 minutes or so. It must have been Ghosts in the system as you suggested - panic over.

Many thanks for your support and kind words of advice.

Regards,
Bill_Mole

I'm glad it worked out...it's all about crunching :)

---

I have BOINC Manager 5.2.8
Most recently I was running SETI 4.18
I have 6 beta units, enough for about 5 days, running on 5.12

I assume 4.18 will update automatically when it's ready.

At about the time noted I tried resetting and then detaching/reattaching SETI (manually) to try and "shake some Work Units loose", which explains the messages above.

I also tried some manual updates - with similar lack of success. Then I saw this thread and decided to join in.

Regards,
Bill_Mole

Hi Michael & Mmciastro,

I applied patience and waited - and lo and behold 20 work units turned up in the last 15 minutes or so. It must have been Ghosts in the system as you suggested - panic over.

Many thanks for your support and kind words of advice.

Regards,
Bill_Mole

---

I see this:

03/05/2006 10:11:34|SETI@home|Resetting project
03/05/2006 10:11:34||request_reschedule_cpus: exit_tasks
03/05/2006 10:11:34||request_reschedule_cpus: project op
03/05/2006 10:12:30|SETI@home|Resetting project
03/05/2006 10:12:30||request_reschedule_cpus: exit_tasks
03/05/2006 10:12:30|SETI@home|Detaching from project

followed by more resets and detachments. Are you doing this or it boinc doing this??? Which core client are you using??? 5.2.13, etc, do you currently have beta work to crunch?

I have BOINC Manager 5.2.8
Most recently I was running SETI 4.18
I have 6 beta units, enough for about 5 days, running on 5.12

I assume 4.18 will update automatically when it's ready.

At about the time noted I tried resetting and then detaching/reattaching SETI (manually) to try and "shake some Work Units loose", which explains the messages above.

I also tried some manual updates - with similar lack of success. Then I saw this thread and decided to join in.

Regards,
Bill_Mole

---

Thanks and Regards,
Bill

You're seeing Ghosts. This happens once in a great while and noone I know of has tracked down exactly why it's happening. The servers assigned them and shipped them to you, but you didn't get them. Now that Seti thinks you've gotten your limit, it won't let you get anymore until tomorrow (or whenever their clock is set for). Hmmmm,

thinking

Thanks for this - it had me worried for a while - now I'll sit back and see if I get some more units tomorrow. Meanwhile I will let Beta have my spare cycles, as I seem to be getting units from there OK.

Many thanks for the advice.

Regards,
Bill

---

Thanks and Regards,
Bill

You're seeing Ghosts. This happens once in a great while and noone I know of has tracked down exactly why it's happening. The servers assigned them and shipped them to you, but you didn't get them. Now that Seti thinks you've gotten your limit, it won't let you get anymore until tomorrow (or whenever their clock is set for). Hmmmm,

thinking

If he was returning errors, wouldn't his quota be lower? It might be a connection issue where he got "ghosts" that are counting agains his total. Bill, do you have 100 uncrunched results on your work tab that were downloaded today(last 24 hours)?

Hi Mmciastro,

I can see I apparently have about 80 or so units on the BOINC Server, but none at this end.

I have a firewall which is set to allow SETI and BOINC to communicate unhindered; and messages and completed units have been flowing fine.

That takes me past the limits of my small expertise . . .

Thanks and Regards,
Bill

---

If he was returning errors, wouldn't his quota be lower? It might be a connection issue where he got "ghosts" that are counting agains his total. Bill, do you have 100 uncrunched results on your work tab that were downloaded today(last 24 hours)?

Your right.

Hmm....I still want to look at his machines though...I think it would be helpful.

---

the big stopper I see is this:

03/05/2006 11:51:27|SETI@home|Message from server: (reached daily quota of 100 results)

You've reached your daily quota of 100 results/cpu/day.

Yeah that's why i wanted to look at his boxes...see if he is returning errors.

---

bill mole: COuld you unhide your computers please so I can take a look at them?

Hi Michael,

I think that should do it - sorry!

Regards,
Bill

Give it time....they aren't unhidden ..yet.

---

bill mole: COuld you unhide your computers please so I can take a look at them?

Hi Michael,

I think that should do it - sorry!

Regards,
Bill

---

bill mole: COuld you unhide your computers please so I can take a look at them?

---

Hi Folks,

I have also apparently been cut-off from SETI, having not received any new work for about 5 days now. When the last WU in my system drained away without replacement (about 09:40 BST - UTC+1)I tried resetting, and even detaching and re-attaching, with no success. All I have are the following messages:

03/05/2006 09:40:44|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 09:40:44|SETI@home|Reason: Requested by user
03/05/2006 09:40:44|SETI@home|Reporting 1 results
03/05/2006 09:40:49|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 10:08:55||Suspending computation and network activity - running CPU benchmarks
03/05/2006 10:08:55|SETI@home Beta Test|Pausing result 01jn01aa.18567.12098.286082.3.22_1 (left in memory)
03/05/2006 10:08:58||Running CPU benchmarks
03/05/2006 10:09:57||Benchmark results:
03/05/2006 10:09:57|| Number of CPUs: 1
03/05/2006 10:09:57|| 2698 double precision MIPS (Whetstone) per CPU
03/05/2006 10:09:57|| 7665 integer MIPS (Dhrystone) per CPU
03/05/2006 10:09:57||Finished CPU benchmarks
03/05/2006 10:09:58||Resuming computation and network activity
03/05/2006 10:09:58||request_reschedule_cpus: Resuming activities
03/05/2006 10:09:58|SETI@home Beta Test|Resuming result 01jn01aa.18567.12098.286082.3.22_1 using setiathome_enhanced version 512
03/05/2006 10:09:58|SETI@home Beta Test|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi
03/05/2006 10:09:58|SETI@home Beta Test|Reason: To fetch work
03/05/2006 10:09:58|SETI@home Beta Test|Requesting 1079 seconds of new work
03/05/2006 10:10:03|SETI@home Beta Test|Scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi succeeded
03/05/2006 10:10:05|SETI@home Beta Test|Started download of 03ap01aa.22043.114.792340.3.222
03/05/2006 10:10:58|SETI@home Beta Test|Finished download of 03ap01aa.22043.114.792340.3.222
03/05/2006 10:10:58|SETI@home Beta Test|Throughput 6804 bytes/sec
03/05/2006 10:10:59||request_reschedule_cpus: files downloaded
03/05/2006 10:11:34|SETI@home|Resetting project
03/05/2006 10:11:34||request_reschedule_cpus: exit_tasks
03/05/2006 10:11:34||request_reschedule_cpus: project op
03/05/2006 10:12:30|SETI@home|Resetting project
03/05/2006 10:12:30||request_reschedule_cpus: exit_tasks
03/05/2006 10:12:30|SETI@home|Detaching from project
03/05/2006 10:12:30||request_reschedule_cpus: project op
03/05/2006 10:12:57||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php
03/05/2006 10:13:28|http://setiathome.berkeley.edu/|Master file download succeeded
03/05/2006 10:13:28|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 10:13:28|http://setiathome.berkeley.edu/|Reason: Requested by user
03/05/2006 10:13:28|http://setiathome.berkeley.edu/|Requesting 432000 seconds of new work
03/05/2006 10:15:36|http://setiathome.berkeley.edu/|Resetting project
03/05/2006 10:15:36||request_reschedule_cpus: exit_tasks
03/05/2006 10:15:36|http://setiathome.berkeley.edu/|Detaching from project
03/05/2006 10:15:36||request_reschedule_cpus: project op
03/05/2006 10:18:32||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php
03/05/2006 10:18:53|http://setiathome.berkeley.edu/|Master file download succeeded
03/05/2006 10:18:53|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 10:18:53|http://setiathome.berkeley.edu/|Reason: Requested by user
03/05/2006 10:18:53|http://setiathome.berkeley.edu/|Requesting 432000 seconds of new work
03/05/2006 10:18:55|http://setiathome.berkeley.edu/|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 10:18:55|SETI@home|Message from server: Not sending work - last request too recent: 326 sec
03/05/2006 10:18:55|SETI@home|New host venue: home
03/05/2006 10:18:55|SETI@home|Successfully attached to SETI@home
03/05/2006 10:29:01|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 10:29:01|SETI@home|Reason: To fetch work
03/05/2006 10:29:01|SETI@home|Requesting 432000 seconds of new work
03/05/2006 10:34:12||Attempting to communicate with [setiboinc.ssl.berkeley.edu] timed out
03/05/2006 10:34:16|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -182
03/05/2006 10:34:16|SETI@home|No schedulers responded
03/05/2006 10:35:17|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 10:35:17|SETI@home|Reason: To fetch work
03/05/2006 10:35:17|SETI@home|Requesting 432000 seconds of new work
03/05/2006 10:35:22|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 10:35:22|SETI@home|Message from server: Not sending work - last request too recent: 375 sec
03/05/2006 10:35:22|SETI@home|No work from project
03/05/2006 10:45:32|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 10:45:32|SETI@home|Reason: To fetch work
03/05/2006 10:45:32|SETI@home|Requesting 432000 seconds of new work
03/05/2006 10:50:41||Attempting to communicate with [setiboinc.ssl.berkeley.edu] timed out
03/05/2006 10:50:42|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -182
03/05/2006 10:50:42|SETI@home|No schedulers responded
03/05/2006 10:51:42|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 10:51:42|SETI@home|Reason: To fetch work
03/05/2006 10:51:42|SETI@home|Requesting 432000 seconds of new work
03/05/2006 10:51:47|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 10:51:47|SETI@home|Message from server: Not sending work - last request too recent: 370 sec
03/05/2006 10:51:47|SETI@home|No work from project
03/05/2006 11:01:58|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 11:01:58|SETI@home|Reason: To fetch work
03/05/2006 11:01:58|SETI@home|Requesting 432000 seconds of new work
03/05/2006 11:07:07||Attempting to communicate with [setiboinc.ssl.berkeley.edu] timed out
03/05/2006 11:07:08|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -182
03/05/2006 11:07:08|SETI@home|No schedulers responded
03/05/2006 11:08:19|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 11:08:19|SETI@home|Reason: To fetch work
03/05/2006 11:08:19|SETI@home|Requesting 432000 seconds of new work
03/05/2006 11:08:24|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 11:08:24|SETI@home|Message from server: Not sending work - last request too recent: 380 sec
03/05/2006 11:08:24|SETI@home|No work from project
03/05/2006 11:18:35|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 11:18:35|SETI@home|Reason: To fetch work
03/05/2006 11:18:35|SETI@home|Requesting 432000 seconds of new work
03/05/2006 11:23:46||Attempting to communicate with [setiboinc.ssl.berkeley.edu] timed out
03/05/2006 11:23:50|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -182
03/05/2006 11:23:50|SETI@home|No schedulers responded
03/05/2006 11:38:07|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 11:38:07|SETI@home|Reason: To fetch work
03/05/2006 11:38:07|SETI@home|Requesting 432000 seconds of new work
03/05/2006 11:38:12|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 11:38:12|SETI@home|Message from server: No work sent
03/05/2006 11:38:12|SETI@home|Message from server: (reached daily quota of 100 results)
03/05/2006 11:38:12|SETI@home|No work from project
03/05/2006 11:41:05||request_reschedule_cpus: project op
03/05/2006 11:41:07|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 11:41:07|SETI@home|Reason: Requested by user
03/05/2006 11:41:07|SETI@home|Requesting 432000 seconds of new work
03/05/2006 11:41:13|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 11:41:13|SETI@home|General preferences have been updated
03/05/2006 11:41:13|SETI@home|Message from server: Not sending work - last request too recent: 180 sec
03/05/2006 11:41:13||General prefs: from SETI@home (last modified 2006-05-03 11:40:46)
03/05/2006 11:41:13||General prefs: no separate prefs for home; using your defaults
03/05/2006 11:51:22|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/05/2006 11:51:22|SETI@home|Reason: To fetch work
03/05/2006 11:51:22|SETI@home|Requesting 432000 seconds of new work
03/05/2006 11:51:27|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
03/05/2006 11:51:27|SETI@home|General preferences have been updated
03/05/2006 11:51:27|SETI@home|Message from server: No work sent
03/05/2006 11:51:27|SETI@home|Message from server: (reached daily quota of 100 results)
03/05/2006 11:51:27||General prefs: from SETI@home (last modified 2006-05-03 11:42:40)
03/05/2006 11:51:27||General prefs: no separate prefs for home; using your defaults
03/05/2006 11:51:27|SETI@home|No work from project

Apologies for the length of this post - I would appreciate any help to get me up and going again.

Meanwhile I still have some WU for Beta to crunch . . .

Thanks in advance,
Bill_Mole

---

I'm not from the UK, but I'll assume "sorted" means it's OK now. If not, we'll be here

tony

yup, all working now. many thanks. have found the culprit - the 'git' that did it!

Did you bang his head on the wall?

---