There is no work from project AGAIN??

What CC version are you running? Apparently the project will only give work to those running 4.09 now.

> What CC version are you running? Apparently the project will only give work to
> those running 4.09 now.
>


We'll I've been on v4.09 for a week or so now and I cannot get any SETI WU's - been like that for a day or so - so my PC's are running CPDN and LHC almost exclusively, since there's no SETI work available.

Timbo

Are you running the setiathome_4.05 worker?

If you are still on the 4.03 there may be no work left for this client.

Dunc

> Are you running the setiathome_4.05 worker?
>
> If you are still on the 4.03 there may be no work left for this client.
>
> Dunc


Dunc,

I'm on SETI v4.05 (automatically downloaded a couple of days ago) and BOINC v4.09.

rgds,

Timbo

>
> Dunc,
>
> I'm on SETI v4.05 (automatically downloaded a couple of days ago) and BOINC
> v4.09.
>
> rgds,
>
> Timbo


FU:

I currently show:
SETI@home - 2004-10-02 15:29:14 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-02 15:29:14 - No schedulers responded


BUT the message shown at:

http://setiweb.ssl.berkeley.edu/sah_status.html

says:

data-driven web pages klaatu Running
scheduler kryten Running
feeder kryten Running
file_deleter koloth Running
transitioner1 klaatu Running
transitioner2 klaatu Running
transitioner3 kryten Running
transitioner4 kryten Running
sah_validate klaatu Running
sah_assimilator galileo Running

sah_splitter galileo Not running
sah_splitter2 milkyway Not running
sah_splitter3 philmor Not running


So, why aren't any SETI WU's coming my way?

(I shouldn't worry - it's just that more time-slicing goes to LHC and CPDN..!!)

Timbo

Strange, I have had no problems contacting here?

SETI@home - 2004-10-02 15:00:42 - Resuming computation for result 26ap04ab.3369.13248.22154.80_1 using setiathome version 4.03
SETI@home - 2004-10-02 15:00:43 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-02 15:00:49 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-02 15:00:49 - Project prefs: using your defaults
SETI@home - 2004-10-02 15:39:16 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-02 15:39:20 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

and

SETI@home - 2004-10-02 04:07:54 - Starting result 06my04ab.10554.1072.203404.244_3 using setiathome version 4.05
SETI@home - 2004-10-02 04:07:54 - Started upload of 06my04ab.10554.1072.203404.247_3_0
SETI@home - 2004-10-02 04:08:02 - Finished upload of 06my04ab.10554.1072.203404.247_3_0
SETI@home - 2004-10-02 04:08:02 - Throughput 6992 bytes/sec
SETI@home - 2004-10-02 04:08:02 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-02 04:08:07 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-02 15:41:02 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-02 15:41:07 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

Dunc

I got a WU about an hour ago.

Just try to update again.

win98SE
Boinc 4.09
Seti 4.05

> Strange, I have had no problems contacting here?

> Dunc
>
>


Dunc,

I just tried again and got:

SETI@home - 2004-10-02 15:48:30 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded


BUT still no more WU's downloaded - am 76% through the last one and no more in the cache.

Maybe it's my SETI prefs, although, these are really wide open to allow SETI to use up plenty of HDD space and no restrictions on time, etc.

I'm flummoxed...!

Timbo

Just to check, under general prefs, how many days do you have under 'Connect to network about every'?

Dunc

> Just to check, under general prefs, how many days do you have under 'Connect
> to network about every'?
>
> Dunc


Hi Dunc,

I'm set at every "1" days (and am on cable connection 24/7) and have a 3Ghz P4 crunching 24/7. So, in theory, as each WU is crunched in less than 4 hours. So, ideally I guess my cache should always be around 6 or 7 WU's (ie a days worth).


Timbo

> I got a WU about an hour ago.
>
> Just try to update again.
>
> win98SE
> Boinc 4.09
> Seti 4.05
>


Hi Seti-seeker,

Thanks for the post - I'm running exactly the same spec, so cannot understand the WU's aren't flowing in...!

Timbo

Hi Timbo,

It may be worth increasing it to 2 for example and seeing what it does. You can always put it back afterwards.

I personally run mine at 11 days! In the past it has served me well during outages.

Dunc

> Hi Timbo,
>
> It may be worth increasing it to 2 for example and seeing what it does. You
> can always put it back afterwards.
>
> I personally run mine at 11 days! In the past it has served me well during
> outages.
>
> Dunc


Dunc,

I just changed it to 5 and left it for a while (before I answered your last post).

Now when I do a manual update I get:

SETI@home - 2004-10-02 16:27:29 - Message from server: Not sending work - last RPC too recent: 546 sec


What's an RPC? And how can it dictate that "it" doesn't want to send me work?

I thought that the BOINC client allowed for greater "user preferences" compared to SETI Classic !!
(BTW: I used SETI Classic and SETI Driver, so when things got "tight" on the SETI server, I increased my cache and it worked flawlesly. BOINC now seems to take more control *away* from the user.

Timbo

This may work if the server is down between the 11 days connection, but if the server is down on the 11 day you could still not get any work.
Watch the deadline. If you have 11 days set you should get 22 days of work.
The deadline is 14 days. So 7 days should give you 14 days of work.
At this time mine is set for one day. I'm connected to 4 projects and at time have wu that don't beat the deadline. If you don't return result before the deadline you won't get credit for that wu. The dev are working on the deadline problem with multi projects.

Fred BOINC Alpha & BOINC Beta Tester

>
> SETI@home - 2004-10-02 16:27:29 - Message from server: Not sending work - last
> RPC too recent: 546 sec
>
>
> What's an RPC? And how can it dictate that "it" doesn't want to send me work?
>

RPC stands for Remote Procedure Call. Which is when your client (the remote part) calls a procedure on the server. It's controlled on the server I believe, so there's nothing you can really do about it. It's most likely a control that prevents users from flooding BOINC by requesting WUs over and over and over and over and over and over and over and over and over again but mashing on the Update feature in the client.




------------------------------------


The game High/Low is played by tossing two nuclear warheads into the air. The one whose bomb explodes higher wins. This game is usually played by people of low intelligence, hence the name High/Low.

Hi Timbo,

I would let the time out expire, and if it doesn't automatically update, manually update it.

I run the boinc_gui with the following switch (-return_results_immediately). This maintains a full cache at the desired setting. In theory it downloads a wu for everyone you send back. In practice it sets a low and high water mark with your desired cache as the median value, ie low=10days desired=11days and high=12days. When your cache reaches the low mark it usually tries to fill to the high mark.

In theory ;-)

Dunc

> Hi Timbo,
>
> I would let the time out expire, and if it doesn't automatically update,
> manually update it.
>
> I run the boinc_gui with the following switch (-return_results_immediately).
> This maintains a full cache at the desired setting. In theory it downloads a
> wu for everyone you send back. In practice it sets a low and high water mark
> with your desired cache as the median value, ie low=10days desired=11days and
> high=12days. When your cache reaches the low mark it usually tries to fill to
> the high mark.
>
> In theory ;-)
>
> Dunc


To all who've responded.

Thanks for your messages and help.

Seems that I'm not destined (currently) to be able to re-fill my cache to the level I think I need, in order to prevent a lack of WU's from affecting my ability to crunch.

(I've tried to prevent that anyways, by joining a few projects, but given I've been crunching for SETI since August 1999, SETI@home has always been my "preferred" choice for using spare CPU cycles).

So, I'm going to try and ride this one out - and hopefully I'll get enough WU's to keep my credits rolling (as you can see from my signatures, I've been quite succcessful on SETI/BOINC up to now - only had "trouble" in the last few days) and I cannot explain why I'm not getting WU's in any significant quantity.

C'est la vie !

Timbo

PS Just did a manual update and SETI says:

SETI@home 2004-10-02 18:53:14 Message from server: No work available

You just can't win !!

> > Hi Timbo,
> >
> > I would let the time out expire, and if it doesn't automatically update,
> > manually update it.
> >
> > I run the boinc_gui with the following switch
> (-return_results_immediately).
> > This maintains a full cache at the desired setting. In theory it
> downloads a
> > wu for everyone you send back. In practice it sets a low and high water
> mark
> > with your desired cache as the median value, ie low=10days desired=11days
> and
> > high=12days. When your cache reaches the low mark it usually tries to
> fill to
> > the high mark.
> >
> > In theory ;-)
> >
> > Dunc
>
>
> To all who've responded.
>
> Thanks for your messages and help.
>
> Seems that I'm not destined (currently) to be able to re-fill my cache to the
> level I think I need, in order to prevent a lack of WU's from affecting my
> ability to crunch.
>
> (I've tried to prevent that anyways, by joining a few projects, but given I've
> been crunching for SETI since August 1999, SETI@home has always been my
> "preferred" choice for using spare CPU cycles).
>
> So, I'm going to try and ride this one out - and hopefully I'll get enough
> WU's to keep my credits rolling (as you can see from my signatures, I've been
> quite succcessful on SETI/BOINC up to now - only had "trouble" in the last few
> days) and I cannot explain why I'm not getting WU's in any significant
> quantity.
>
> C'est la vie !
>
> Timbo
> src="http://boinc.mundayweb.com/cpdn/stats.php?userID=377">
>


The more projects you attach to, the fewer WUWUs you get for each project, think about it!!!!


My name is Pascal and this message has no meaning, but still has my approval...

It is 10 oclock, do you know what your WUWUs are doing tonight...

>
> The more projects you attach to, the fewer WUWUs you get for each project,
> think about it!!!!
>
>
> My name is Pascal and this message has no meaning, but still has my
> approval...
>


Pascal,

You are of course correct that if you crunch WU's on one project for 100% of the time, of course you'll get more WU's than if you only crunch say 50/50 on two projects.

But I'm getting say 1 SETI WU a day (and no cached WU's), my prefs are set to crunch 40% for SETI and I'm running a P4 PC at 3GHz, which should return maybe 7 a day at 100% (or just under 3 a day at 40%). So, why can't *I* ensure that my cache has enough WU in order that the PC is kept working if I have no other WU to crunch and if SETI goes offline???

Timbo