| Author |
Message |
|---|
|
|
|
I keep getting this for the last hour or so... is SETI running out of work? |
|
|
|
|
|
> I keep getting this for the last hour or so... is SETI running out of work?
>
The servers were down, apparently to activate the point validator, but everything should be back up now. Next time it connects it should get work.
|
|
|
|
|
|
When it comes back up, if you keep seeing the message that it's backing off for 10 minutes, 0 seconds, you're in a backoff loop.
Close BOINC for 15-20 minutes, and restart the client. |
|
|
|
|
|
> > I keep getting this for the last hour or so... is SETI running out of
> work?
> >
> The servers were down, apparently to activate the point validator, but
> everything should be back up now. Next time it connects it should get work.
>
>
> <a> href="http://www.boinc.dk/index.php?page=user_statistics&userid=24497">
Yes, it is working again now. |
|
|
|
|
|
I'm still getting the "no work available" - on two different machines, two different platforms, I've shutdown the client on both machines and waited for a period of time on each machine, and neither of them get work. |
|
|
|
|
|
> When it comes back up, if you keep seeing the message that it's backing off
> for 10 minutes, 0 seconds, you're in a backoff loop.
>
> Close BOINC for 15-20 minutes, and restart the client.
done that and still get "no work available"...
|
|
|
|
|
|
> > When it comes back up, if you keep seeing the message that it's backing
> off
> > for 10 minutes, 0 seconds, you're in a backoff loop.
> >
> > Close BOINC for 15-20 minutes, and restart the client.
>
> done that and still get "no work available"...
Then it sounds like a lot of people are pounding the servers for work. |
|
|
|
|
|
> I keep getting this for the last hour or so... is SETI running out of work?
>
My first system is also not receiving units, with back off periods of 5, 10 and 40 minutes. I have shut it off and restarted. Apparently, with no other error meesages included, there is no work avialable?
Any other possiblities?
|
|
|
|
|
|
> > I keep getting this for the last hour or so... is SETI running out of
> work?
> My first system is also not receiving units, with back off periods of 5, 10
> and 40 minutes. I have shut it off and restarted. Apparently, with no other
> error meesages included, there is no work avialable?
>
> Any other possiblities?
If you stop the software and restart it immediately several times the server will not talk to you to prevent DoS type problems with broken client machines. Let it time out on its own if you haven't?
|
|
|
|
|
|
> I keep getting this for the last hour or so... is SETI running out of work?
>
Same here - it seems very strange that there is no work!
|
|
|
|
|
|
> My first system is also not receiving units, with back off periods of 5, 10
> and 40 minutes. I have shut it off and restarted. Apparently, with no other
> error meesages included, there is no work avialable?
Keep in mind that once a backoff time has been issued, there is no way around actually waiting that time. Stopping it and restarting it will allow you to reconnect as long as you have NOT been given a backoff time. If your last backoff was 40 minutes - nothing will reconnect you before that time has passed (even stopping and restarting the program doesn't override a backoff time).
Simply let it go until that time has lapsed and it will try again.
|
|
|
|
|
|
Its not working for me, either. All I get is no work available.
|
|
|
|
|
|
I received 4 WU's 3 hours ago, bringing my total in cache to 9....
|
|
|
|
|
|
2 pc's on for more then 2 hours, still no work available,
queued to more then 1 hour :-(
any idea guys ?
Greetz Master D
Homepage www.setiatbelgie.be |
|
|
|
|
|
> Keep in mind that once a backoff time has been issued, there is no way around
> actually waiting that time. Stopping it and restarting it will allow you to
> reconnect as long as you have NOT been given a backoff time. If your last
> backoff was 40 minutes - nothing will reconnect you before that time has
> passed (even stopping and restarting the program doesn't override a backoff
> time).
Incorrect. Updating (retry now) the project will force it to try and connect, regardless of backoff time. Also, turning off the client and giving it 15-20 minutes will cause the backoff to expire. If it's not doing this, give it more time "off".
As for those not getting work, if there is a huge number of people also trying to get work, it might take a bit. It is functioning, because I just downloaded work. |
|
|
|
|
|
All seems fine and dandy now.
|
|
|
|
|
|
> Incorrect. Updating (retry now) the project will force it to try and connect,
> regardless of backoff time.
My apologies for the incorrect info.
There is no such option for the linux client (I learned this the hard way in beta), and since I have no windows systems my old feable mind often forgets exactly what some of the differences I've read about are.
|
|
|
|
|
|
ok thx, retrying now....for the 40th time lol
I'll give it another go tomorrow :-(
Anyone knows how to delete the log ? seems pretty much in such a short time.
Regards Master D |
|
|
|
|
|
SETI@home - 2004-06-24 17:05:01 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-24 17:05:01 - General preferences have been updated
SETI@home - 2004-06-24 17:05:01 - Message from server: No work available
--- - 2004-06-24 17:05:01 - General prefs: from SETI@home (last modified 2004-06-24 17:02:56)
--- - 2004-06-24 17:05:01 - General prefs: no separate prefs for work; using your defaults
SETI@home - 2004-06-24 17:05:01 - Project prefs: no separate prefs for work; using your defaults
SETI@home - 2004-06-24 17:05:01 - No work from project
SETI@home - 2004-06-24 17:05:01 - Deferring communication with project for 1 minutes and 0 seconds
--- - 2004-06-24 17:06:04 - Fewer active results than CPUs; requesting more work
SETI@home - 2004-06-24 17:06:04 - Requesting 430998 seconds of work
SETI@home - 2004-06-24 17:06:04 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-24 17:06:07 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-24 17:06:07 - Message from server: Not sending work - last RPC too recent: 65 sec
SETI@home - 2004-06-24 17:06:07 - No work from project
SETI@home - 2004-06-24 17:06:07 - Deferring communication with project for 10 minutes and 0 seconds
OK - I have setup several machines today but all the machines I have don in the last 5 hours are getting this message and have NOT downloaded and data sets. I have tried turning them off for 2-4 hours but they still cannot connect.
I am guessing either the download server is overloaded (and someone should be able to confirm this) or we have something else going on here...
|
|
|
|
|
|
@Darren.
No problem. I often forget that there are other users with different OSs, and given Windows advice to Linux users. :)
@MasterDave.
To clear the log. Close and restart the GUI. This will start the message log fresh.
@Ace
Yes, I believe it's just overloaded servers. Also remember, a planed server outage is to take place at 1700 UTC. |
|
|
