--- - 2004-10-14 14:18:54 - Insufficient work; requesting more
SETI@home - 2004-10-14 14:18:54 - Requesting 690509 seconds of work
SETI@home - 2004-10-14 14:18:54 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-14 14:19:01 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-14 14:19:01 - Message from server: Not sending work - last RPC too recent: 89 sec
SETI@home - 2004-10-14 14:19:01 - No work from project
SETI@home - 2004-10-14 14:19:01 - Deferring communication with project for 10 minutes and 0 seconds


My question is, how do i download the work needed? My computer is idle at the mo and would like it to do some work over lunch.

I have reset the project x2 today and lost the work, but howd i get more?


=========

---

The error message that you show in your post means that it is two short a time since the last contact with the scheduler (last RPC too recent: 89), is there any errors before this one.

---

Hello NovaPaul

I get this everytime I set-up a new box, it's just a matter of waiting, normally not more that 10-20 mins :)

---

<a href='http://www.theclangers.net'> <img border='0' src='http://www.acolburn.co.uk/clangers.gif' height='132'></a></p>

> The error message that you show in your post means that it is two short a time
> since the last contact with the scheduler (last RPC too recent: 89), is there
> any errors before this one.
>

Hi Andrew. Theres no other messages. its just repeated over and over. Been doing it since i reset project @ 11:52am... bout 2 hours ago.

---

> > The error message that you show in your post means that it is two short a
> time
> > since the last contact with the scheduler (last RPC too recent: 89), is
> there
> > any errors before this one.
> >
>
> Hi Andrew. Theres no other messages. its just repeated over and over. Been
> doing it since i reset project @ 11:52am... bout 2 hours ago.
>
When I reset mine it took a while to send me more wu's.I just left it and it sorted itself out after a while.

---

......In Space No One Can Hear You Scream......

> --- - 2004-10-14 14:18:54 - Insufficient work; requesting more
> SETI@home - 2004-10-14 14:18:54 - Requesting 690509 seconds of work
> SETI@home - 2004-10-14 14:18:54 - Sending request to scheduler:
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> SETI@home - 2004-10-14 14:19:01 - Scheduler RPC to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
> SETI@home - 2004-10-14 14:19:01 - Message from server: Not sending work - last
> RPC too recent: 89 sec
> SETI@home - 2004-10-14 14:19:01 - No work from project
> SETI@home - 2004-10-14 14:19:01 - Deferring communication with project for 10
> minutes and 0 seconds
>
>
> My question is, how do i download the work needed? My computer is idle at the
> mo and would like it to do some work over lunch.
>
> I have reset the project x2 today and lost the work, but howd i get more?


As has already been stated the connecting to the server has been too close together. Don't manually try updating and wait for Boinc to do it.

Also a possibility you said you reset twice and lost work. It looks like you're trying to download 8 days work which would mean you lost about 16 days already. If Seti has set a daily limit like LHC you may have exceeded it.

Try waiting and see what the message is when Boinc connects to Seti again.

>
> SETI@home - 2004-10-14 14:19:01 - Message from server: Not sending work - last
> RPC too recent: 89 sec
> SETI@home - 2004-10-14 14:19:01 - No work from project
> SETI@home - 2004-10-14 14:19:01 - Deferring communication with project for 10
> minutes and 0 seconds
>

This normally sorts itself out when next it makes contact with the project server.

>
> My question is, how do i download the work needed? My computer is idle at the
> mo and would like it to do some work over lunch.
>
> I have reset the project x2 today and lost the work, but howd i get more?
>

There are d/l limits for each project, SETI's is probably 50 WU's per day. One of the reasons for the limit is to prevent people from d/l large quantities of WU's, then resetting or detaching the project and losing those WU's. These lost WU's won't be re-sent to a new user until the deadline date for for the WU has past.

Personally, if I were the server, I wouldn't send you any more WU's, either. When you do a reset, you tend to annoy (also know as "piss off") a great number of people because you make the WUs you lose into "orphans," and people, who have been waiting for _your_ results so they can get credit for the work _THEY_ have done, have to wait even longer. They now have to wait until the WU is resent, processed, and the results returned by yet another person. This is not how to win friends and influence people on the BOINC-based DC projects. Then, when they don't get credit, they start whinning about it, I have to read through all of that "stuff."

As to the "Connect every" parameter, it has been suggested (by people more knowledgable than I) that you set "Connect every" to no more than 5 days, based on a 14-day deadline. This will give you somewhere between 5 and 10 days of work. This will be sufficient to cover most server outages. Depending on your computer(s) you might want to start with a setting of 2 or 3 days, then adjust accordingly.

Cheers,

Stephen

---

<P>"I want to go dancing on the moon, I want to frolic in zero gravity!....", and now, I might be able to go someday! Thanks, SpaceShipOne and crew!<BR><a><img src="http://69.93.59.107/stats/banner.php?cpid=26cbd89db7fb85cbfe580729d76705c1"></a>

Hi guys,

I restarted my machine coz it was on a go-slo. i checked boinc messages and it said:

--- - 2004-10-13 14:00:50 - Starting BOINC client version 4.12 for windows_intelx86
SETI@home - 2004-10-13 14:00:50 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-10-13 14:00:50 - Host ID is 226106
--- - 2004-10-13 14:00:51 - General prefs: from SETI@home (last modified 2004-10-13 12:16:03)
--- - 2004-10-13 14:00:51 - General prefs: no separate prefs for home; using your defaults
SETI@home - 2004-10-13 14:00:53 - Deferring communication with project for 1 days, 0 hours, 28 minutes, and 8 seconds


:'( i dont wanna be waiting this long, but if i have to... :'(

im not gonna wine.... :P



============

---

> >
> > SETI@home - 2004-10-14 14:19:01 - Message from server: Not sending work -
> last
> > RPC too recent: 89 sec
> > SETI@home - 2004-10-14 14:19:01 - No work from project
> > SETI@home - 2004-10-14 14:19:01 - Deferring communication with project
> for 10
> > minutes and 0 seconds
> >
>
> This normally sorts itself out when next it makes contact with the project
> server.
>
> >
> > My question is, how do i download the work needed? My computer is idle at
> the
> > mo and would like it to do some work over lunch.
> >
> > I have reset the project x2 today and lost the work, but howd i get
> more?
> >
>
> There are d/l limits for each project, SETI's is probably 50 WU's per day. One
> of the reasons for the limit is to prevent people from d/l large quantities of
> WU's, then resetting or detaching the project and losing those WU's. These
> lost WU's won't be re-sent to a new user until the deadline date for for the
> WU has past.
>
> Personally, if I were the server, I wouldn't send you any more WU's, either.
> When you do a reset, you tend to annoy (also know as "piss off") a great
> number of people because you make the WUs you lose into "orphans," and people,
> who have been waiting for _your_ results so they can get credit for the work
> _THEY_ have done, have to wait even longer. They now have to wait until the WU
> is resent, processed, and the results returned by yet another person. This is
> not how to win friends and influence people on the BOINC-based DC projects.
> Then, when they don't get credit, they start whinning about it, I have to read
> through all of that "stuff."
>
> Cheers,
>
> Stephen
>

I had to reset mine as every single wu was erroring out and being deleted anyway.I did not have many wu's left though.About 6 i think.

---

......In Space No One Can Hear You Scream......

The most likely problem is that you went over the 50 WU a day limit of the SETI@Home project. Usually though you will get a message for that.

The RPC message is telling me and you that you are trying to "force" the connection and the Schedular is saying to us, "hold your horses!" ...

Again, this is why it is important to try to be involved with more than one project. Lucky devil that I am I managed to squeeze into all 5 projects so that, right now with 3 of them up, I don't run out of work to do ...

Joining cp.net, even with a lower share allows you to have work to do at all times ...

---

Rachel,

There can be valid reasons to reset a project, but in my opinion (and it is just my opinion, but based on my current list of "pending" WU's, and other users recent messages) too many people use reset as a "cure all." It isn't.

> > >
> > > SETI@home - 2004-10-14 14:19:01 - Message from server: Not sending
> work -
> > last
> > > RPC too recent: 89 sec
> > > SETI@home - 2004-10-14 14:19:01 - No work from project
> > > SETI@home - 2004-10-14 14:19:01 - Deferring communication with
> project
> > for 10
> > > minutes and 0 seconds
> > >
> >
> > This normally sorts itself out when next it makes contact with the
> project
> > server.
> >
> > >
> > > My question is, how do i download the work needed? My computer is
> idle at
> > the
> > > mo and would like it to do some work over lunch.
> > >
> > > I have reset the project x2 today and lost the work, but howd i get
> > more?
> > >
> >
> > There are d/l limits for each project, SETI's is probably 50 WU's per
> day. One
> > of the reasons for the limit is to prevent people from d/l large
> quantities of
> > WU's, then resetting or detaching the project and losing those WU's.
> These
> > lost WU's won't be re-sent to a new user until the deadline date for for
> the
> > WU has past.
> >
> > Personally, if I were the server, I wouldn't send you any more WU's,
> either.
> > When you do a reset, you tend to annoy (also know as "piss off") a great
> > number of people because you make the WUs you lose into "orphans," and
> people,
> > who have been waiting for _your_ results so they can get credit for the
> work
> > _THEY_ have done, have to wait even longer. They now have to wait until
> the WU
> > is resent, processed, and the results returned by yet another person.
> This is
> > not how to win friends and influence people on the BOINC-based DC
> projects.
> > Then, when they don't get credit, they start whinning about it, I have to
> read
> > through all of that "stuff."
> >
> > As to the "Connect every" parameter, it has been suggested (by people more
> > knowledgable than I) that you set "Connect every" to no more than 5 days,
> > based on a 14-day deadline. This will give you somewhere between 5 and 10
> > days of work. This will be sufficient to cover most server outages.
> > Depending on your computer(s) you might want to start with a setting of 2 or
> > 3 days, then adjust accordingly.
> >
> > Cheers,
> >
> > Stephen
> >
>
> I had to reset mine as every single wu was erroring out and being deleted
> anyway.I did not have many wu's left though.About 6 i think.
>

---

<P>"I want to go dancing on the moon, I want to frolic in zero gravity!....", and now, I might be able to go someday! Thanks, SpaceShipOne and crew!<BR><a><img src="http://69.93.59.107/stats/banner.php?cpid=26cbd89db7fb85cbfe580729d76705c1"></a>

Yeh, i reset the project twice beacuse the client was advising me to...in the message it said the file had return a value of zero but it was not finish, if this continues, reset the project.... so i did.

Now its stuffed.


btw, if i have delayed anyones credit by resetting my project then i am very, very sorry. I have over 100 Wu's pending, from over 3 weeks ago... so i guess were all in the same boat... again... very sorry.


Thank you guys for your help



=========

---

>
> Thank you guys for your help
>

Why not do as Paul suggested and join CPDN. It only takes a couple of minutes to register and download a wu which will keep your machine busy for many weeks to come. Setting your resource share lower for CPDN will give Seti priority when work is available.

So your Seti credit stats might suffer but you still get trickle credit which goes towards your Boinc total credit.

> Why not do as Paul suggested and join CPDN. It only takes a couple of minutes
> to register and download a wu which will keep your machine busy for many weeks
> to come. Setting your resource share lower for CPDN will give Seti priority
> when work is available.
>
> So your Seti credit stats might suffer but you still get trickle credit which
> goes towards your Boinc total credit.
>

i did join Climate Predictor but it slowed my machine down too much. This computer belongs to work and i do some heavy database and webdesigning... i need all the power i can get... wen im running seti/boinc i can hardly tell its there... theres no performance change but wen i use CP its a whole new kettle of fish...

i might give it another go...

---

The thing is my results were not getting sent back anyway so resetting made no diff I think to people losing credit or waiting for credit..I just wanted my pc to stop crunching wu's that were just being deleted straight after and get crunching again on wu's that would get sent back ok and get people credit.

---

......In Space No One Can Hear You Scream......

NovaPaul,

First, I'm not attacking you, or blaming you for anything. I was pointing out the results of using reset as a "cure all" approach to "fixing" problems with SETI (and other projects.)

> Yeh, i reset the project twice beacuse the client was advising me to...in the
> message it said the file had return a value of zero but it was not finish, if
> this continues, reset the project.... so i did.
>
> Now its stuffed.
>
> btw, if i have delayed anyones credit by resetting my project then i am very,
> very sorry. I have over 100 Wu's pending, from over 3 weeks ago... so i guess
> were all in the same boat... again... very sorry.
>

We all have this problem. I suspect we have all lost WU's due to a reset. I admit it. I have, too.

The problem doesn't sound very significant when you consider only a couple of people with 10 to 20 WU's each, but when hundreds or thousands of people reset the project, and they each have 10 to 20 WU's on their machines which are then lost to the reset, it suddenly becomes a significant problem, and not just because of the delayed user credits, either. (People pay more attention when their credits, and how resets affect them, are mentioned.) The important point is that it delays the science, and the results returned to the project.

>
> Thank you guys for your help
>

You're welcome. Most people here will try to help others, if they can.

Cheers,

Stephen

> NovaPaul,
>
> First, I'm not attacking you, or blaming you for anything. I was pointing out
> the results of using reset as a "cure all" approach to "fixing" problems with
> SETI (and other projects.)
>
> > Yeh, i reset the project twice beacuse the client was advising me to...in
> the
> > message it said the file had return a value of zero but it was not
> finish, if
> > this continues, reset the project.... so i did.
> >
> > Now its stuffed.
> >
> > btw, if i have delayed anyones credit by resetting my project then i am
> very,
> > very sorry. I have over 100 Wu's pending, from over 3 weeks ago... so i
> guess
> > were all in the same boat... again... very sorry.
> >
>
> We all have this problem. I suspect we have all lost WU's due to a reset. I
> admit it. I have, too.
>
> The problem doesn't sound very significant when you consider only a couple of
> people with 10 to 20 WU's each, but when hundreds or thousands of people reset
> the project, and they each have 10 to 20 WU's on their machines which are then
> lost to the reset, it suddenly becomes a significant problem, and not just
> because of the delayed user credits, either. (People pay more attention when
> their credits, and how resets affect them, are mentioned.) The important point
> is that it delays the science, and the results returned to the project.
>
> >
> > Thank you guys for your help
> >
>
> You're welcome. Most people here will try to help others, if they can.
>
> Cheers,
>
> Stephen
>


No appology necessary Stephen, i took no offence. Im a laid back kinda guy... i dont do stress... ;)

I just got al little impatient at wanting work units. I have not reset the project before today, but when boinc advises me to, so it might fix a prob, i will reset the project losing the hours i have put into it already.

I appreciate it causes more probs but there will always be probs running software globally.

No offence/malice intended,

Paul

=========

---

> As to the "Connect every" parameter, it has been suggested (by people more
> knowledgable than I) that you set "Connect every" to no more than 5 days,
> based on a 14-day deadline. This will give you somewhere between 5 and 10 days
> of work. This will be sufficient to cover most server outages. Depending on
> your computer(s) you might want to start with a setting of 2 or 3 days, then
> adjust accordingly.

Work units are uploaded as they are finished, but they don't go to the validator until your BOINC client reports them to the scheduler.

If you have "connect every 5 days" then those work units sit on the servers until those five days pass and BOINC connects.

While this is good from a server loading standpoint (fewer scheduler calls) and it's good from a "keep busy" standpoint, it won't be so great if you are expecting quick credits.

In fact, it may take ten days (two five-day cycles) before credits show in the BOINC client.

I've seen lots of panicky messages about credit not being granted, and I'm willing to bet those people have this number set too high. 3 or 4 is probably as high as you want to go.

---

> btw, if i have delayed anyones credit by resetting my project then i am very,
> very sorry. I have over 100 Wu's pending, from over 3 weeks ago... so i guess
> were all in the same boat... again... very sorry.

Note: "...100 Wu's pending, from over 3 weeks ago.."

The expiration date on WUs is 2 weeks (for seti) so if any results really were 3 weeks ago, then they were over deadline.

---

> i did join Climate Predictor but it slowed my machine down too much. This
> computer belongs to work and i do some heavy database and webdesigning... i
> need all the power i can get... wen im running seti/boinc i can hardly tell
> its there... theres no performance change but wen i use CP its a whole new
> kettle of fish...
>
> i might give it another go...
>

If you try again to use Climate on your machine at work there are a couple of general preference settings that might help.

Do work while computer is in use? No

Leave applications in memory while preempted?
(suspended applications will consume swap space if 'yes') No

and maybe also

Do work only between the hours of xx:xx and xx:xx

---