Ah, thanks, we will see if that works out alone. ;)

Just wondered about this behaviour, I always thought the WU cache would be independent from other projects.

> I have yet to recieve any WUs from Seti servers since I signed up with BOINC a
> few days ago. Anyone know of special commands or procedures that could be
> used to get some WUs?
>
>

My response to this problem is I am going back to the old system that works and when they finally fix the problems with this boinc, I will happly come back here, But I am finding it very annoying to work in this environment, had on 1 wu in 24 hours then the computer spend 17 hours trying to get the second.

Getting fed-up of boincing my head against the wall?

see you's all soon and maybe they will give out some real instructions on how to use their systems insead of us lot trying to figure it out for them.

may sound a bit hacked off, but I work for a company that does this to it employees, so cannot and will not put up with it in my fun time.

thank you all have fun wishing you all the wu's you can't handle so they never run out.

Bye bye.

> > I have yet to recieve any WUs from Seti servers since I signed up with
> BOINC a
> > few days ago. Anyone know of special commands or procedures that could
> be
> > used to get some WUs?
> >
> >
>
>

Same ehere. Original SETI@Home started giving errors last night and then I saw that BOINC (BOINK?) was the "new" and wonderful thing to have. Installed at home and at work but both can't seem to get any workunits.

Hey, The hint from Kabuki works!
Just reattached and kicked that http:// from the URL and here we go!

thx man!

If everyone quit and when back to clasic the dev team would not know of any bandwidth problems.
So clasic end and everyone sign back to boinc and guess what BANDWIDTH PROBLEMS.
So hang in there the sooner they know of problems the sooner they can fix them.

Fred BOINC Alpha & BOINC Beta Tester

> Ok...now that I figured the URL problem....just type in the SETIATHOME....
> forget the http:...and the WU's will flow. See ya l8r!
>
Just detached and reattached using the url w/o the http OR any trailing slash
as in setiathome.berkeley.edu and am getting slightly different msgs (still no work, so we will see....)

I just don't understand why the old one had problems, so I went to the new. One computer has no problems getting WU's and the other one hasn't gotten one for two days? Maybe I should just use it for something else, looks like they went too soon to the new one.

WUWU
Owner's manual

Website Owner's Manual

Bah!!! I am in it for the money

> > Ok...now that I figured the URL problem....just type in the
> SETIATHOME....
> > forget the http:...and the WU's will flow. See ya l8r!
> >
> Just detached and reattached using the url w/o the http OR any trailing slash
> as in setiathome.berkeley.edu and am getting slightly different msgs (still no
> work, so we will see....)
>
>

i signed in about an hour ago .... since then i could not get any work.

http://setiathome.berkeley.edu/ - 2005-03-04 19:23:51 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
http://setiathome.berkeley.edu/ - 2005-03-04 19:24:13 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
http://setiathome.berkeley.edu/ - 2005-03-04 19:24:13 - No schedulers responded
http://setiathome.berkeley.edu/ - 2005-03-04 19:24:13 - Deferring communication with project for 1 minutes and 46 seconds

---

> i signed in about an hour ago .... since then i could not get any work.
>
> http://setiathome.berkeley.edu/ - 2005-03-04 19:23:51 - Sending request to
> scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> http://setiathome.berkeley.edu/ - 2005-03-04 19:24:13 - Scheduler RPC to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
> http://setiathome.berkeley.edu/ - 2005-03-04 19:24:13 - No schedulers
> responded
> http://setiathome.berkeley.edu/ - 2005-03-04 19:24:13 - Deferring
> communication with project for 1 minutes and 46 seconds

Please have a look at the Technical News.

S@H/Boinc had severe problems the last days.

As for now, the servers will be overload with requests of thousand PC's. This is very probably the reason why you can't have contact with the scheduler.

Greetings from Belgium.
Thierry

I have same kind of problem. I'm getting the following message:

--- - 2005-04-20 18:17:21 - Insufficient work; requesting more
SETI@home - 2005-04-20 18:17:21 - Requesting 783043 seconds of work
SETI@home - 2005-04-20 18:17:21 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-04-20 18:17:25 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2005-04-20 18:17:25 - Message from server: No work sent (daily quota of 20 WU reached)
SETI@home - 2005-04-20 18:17:25 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2005-04-20 18:17:25 - No work from project
SETI@home - 2005-04-20 18:17:25 - Deferring communication with project for 1 hours, 0 minutes, and 0 seconds

When has there become somekind of quota on daily WUs? I'm running still BOINC 4.19 on this computer (others have 4.25 at least) and I was just palnning to upgrade.

---

Hey, The hint from Kabuki works!
Just reattached and kicked that http:// from the URL and here we go!

thx man!

thats right...
the units are comming.....
;-)

greets
christian

---

15/05/2006 11:24:47|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15/05/2006 11:24:47|SETI@home|Reason: To fetch work
15/05/2006 11:24:47|SETI@home|Requesting 2 seconds of new work
15/05/2006 11:24:52|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
15/05/2006 11:24:52|SETI@home|Message from server: No work sent
15/05/2006 11:24:52|SETI@home|No work from project

There is a problem with BOINC servers? Overload maybe? I have many problems getting WU's to process!!!

15/05/2006 11:24:47|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15/05/2006 11:24:47|SETI@home|Reason: To fetch work
15/05/2006 11:24:47|SETI@home|Requesting 2 seconds of new work
15/05/2006 11:24:52|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
15/05/2006 11:24:52|SETI@home|Message from server: No work sent
15/05/2006 11:24:52|SETI@home|No work from project

There is a problem with BOINC servers? Overload maybe? I have many problems getting WU's to process!!!

Your computers are hidden, so I can’t see what you’re running, but if you’re using an optimized v4.x app that’s ‘protected’ by an app_info.xml file, this is probably an attempt to send you an Enhanced WU for which you don’t have the new app. I’ve seen these messages on my Macs, alternating randomly with successful downloads of v4.18 work, since the public release of v5.12 last week.

---