I have not seen a work unit in about 2 months. It is getting frustrating. I am about to give up and remove seti from my pc and not look back. What can I do to actually recieve a work unit these days.

---

Hi Ski,

It is obvious that there is something amiss here.

1. are you attaching to the correct url?.
2. are your firewall settings allowing Bonic to connect?.
3. what does your messages say?.
4. what version of Bonic do you have?.
5. are you on a dial up?

Please give us more info O.K.

---

> I have not seen a work unit in about 2 months. It is getting frustrating. I am
> about to give up and remove seti from my pc and not look back. What can I do
> to actually recieve a work unit these days.
>
>
Hi

As far as I know (and according to the server status page) there are no problems with a shortage of WU's.
Is is safe to assume that you are referring to hostid 52863 which hasn't sent in a result since august 29th? If so, then all those client errors are suspicious because (correct me if I'm wrong folks!) I don't think there were any major problems with the project back then.
Your other computer hostid 175233, seems to have fared a lot better, but last returned a result on october 1st, prior to then, it looks like it was ticking over nicely.
Both computers are well within recommended specs and seem to have had enough resources at the time, all I can think of is that you have some strange configuration problem at your end. What did you do on the above dates (both of them!)?
Post back with as much info as you can, then perhaps we can help more.

[edit} @Timmy, apologies for the duplication, you beat me to the enter key by 4 minutes, while I was still faffing about with links :) [/edit]

TTFN,

---

Ken Phillips

BOINC question? Look here



"The beginning is the most important part of the work." - Plato

SKI,
Are you downloading one work unit for two puters that might cause
client errors.

I betcha your preferences are also screwwy...

Timmy

---

I am on cable modem and only one of my pc's has been running boinc because I wanted to see it work properly before I tied my other machine up. Believe it or not, I did not change any settings on the pc at all, it went from having the outages to not getting any wu at all. with a constant telling of no wu available. However, I have still gotten a few credits since then, but no wu's.

Here is what BOINC has been saying.

--- - 2004-10-26 01:40:11 - Insufficient work; requesting more
SETI@home - 2004-10-26 01:40:11 - Requesting 29822 seconds of work
SETI@home - 2004-10-26 01:40:12 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-26 01:40:15 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-26 01:40:15 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-10-26 01:40:15 - No work from project
SETI@home - 2004-10-26 01:40:15 - Deferring communication with project for 1 days, 0 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 02:40:15 - Deferring communication with project for 23 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 03:40:15 - Deferring communication with project for 22 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 04:40:15 - Deferring communication with project for 21 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 05:40:15 - Deferring communication with project for 20 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 06:40:15 - Deferring communication with project for 19 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 07:40:15 - Deferring communication with project for 18 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 08:40:15 - Deferring communication with project for 17 hours, 0 minutes, and 0 seconds
--- - 2004-10-26 09:23:14 - Insufficient work; requesting more
SETI@home - 2004-10-26 09:23:14 - Requesting 29872 seconds of work
SETI@home - 2004-10-26 09:23:14 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-26 09:23:17 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-26 09:23:17 - General preferences have been updated
SETI@home - 2004-10-26 09:23:17 - Message from server: No work available (your core client is out of date - please upgrade)
--- - 2004-10-26 09:23:17 - General prefs: from SETI@home (last modified 2004-10-26 09:22:59)
--- - 2004-10-26 09:23:17 - General prefs: using your defaults
SETI@home - 2004-10-26 09:23:17 - No work from project
SETI@home - 2004-10-26 09:23:17 - Deferring communication with project for 1 days, 0 hours, 0 minutes, and 0 seconds
--- - 2004-10-26 09:23:29 - Insufficient work; requesting more
SETI@home - 2004-10-26 09:23:29 - Requesting 2987205 seconds of work
SETI@home - 2004-10-26 09:23:29 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-26 09:23:32 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-26 09:23:32 - No schedulers responded
SETI@home - 2004-10-26 09:23:32 - Deferring communication with project for 2 minutes and 26 seconds
SETI@home - 2004-10-26 09:25:58 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-26 09:26:02 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-26 09:26:02 - Message from server: A new version (4.13) of the BOINC core client is available from this project's web site.
--- - 2004-10-26 09:26:02 - Insufficient work; requesting more
SETI@home - 2004-10-26 09:26:02 - Requesting 2987233 seconds of work
SETI@home - 2004-10-26 09:26:02 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-26 09:26:05 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-26 09:26:05 - Message from server: Not sending work - last RPC too recent: 4 sec
SETI@home - 2004-10-26 09:26:05 - No work from project
SETI@home - 2004-10-26 09:26:05 - Deferring communication with project for 10 minutes and 0 seconds
--- - 2004-10-26 09:36:06 - Insufficient work; requesting more
SETI@home - 2004-10-26 09:36:06 - Requesting 2987342 seconds of work
SETI@home - 2004-10-26 09:36:06 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-26 09:36:09 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-26 09:36:09 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-10-26 09:36:09 - No work from project
SETI@home - 2004-10-26 09:36:09 - Deferring communication with project for 1 days, 0 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 10:36:09 - Deferring communication with project for 23 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 11:36:09 - Deferring communication with project for 22 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 12:36:09 - Deferring communication with project for 21 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 13:36:09 - Deferring communication with project for 20 hours, 0 minutes, and 0 seconds
SETI@home - 2004-10-26 14:36:09 - Deferring communication with project for 19 hours, 0 minutes, and 0 seconds


any more suggestions?

---

I think I just found the problem... Version 4.05 I believe it was. I just updated to 4.13, I will see if that solves the problem.

---

that solved the problem. I now have wu's. Thanks for the help to all of you guys.

---

> SETI@home - 2004-10-26 01:40:15 - Message from server: No work available (your
> core client is out of date - please upgrade)
> SETI@home - 2004-10-26 01:40:15 - No work from project

It says it all right there ^^^^^ "No work available"
You need to download a new core "BOINC" client, the current version is 4.13


Look here:
http://setiweb.ssl.berkeley.edu/download.php

Mike

---

Seti Classic: 204,777 WU /113.636 Yrs

LOL :D

That's the best NON-Seti@Home bug, i have ever seen or heard of. By the way versions changes very often, so watch out maybe there'll be a new version tommorow. Who knows :)
I'm not trying to make a big deal out of it, but must say 2 month no work, because of you know etc. I just can't help it :)

Nice tread by the way ;)

---

Regards