what is the problem here? Why can't I report this project and get a new one?

4/4/2005 7:23:38 AM||Insufficient work; requesting more
4/4/2005 7:23:38 AM|SETI@home|Requesting 8640.00 seconds of work
4/4/2005 7:23:38 AM|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
4/4/2005 7:23:39 AM|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
4/4/2005 7:23:39 AM|SETI@home|No schedulers responded
4/4/2005 7:23:39 AM|SETI@home|Deferring communication with project for 2 minutes and 41 seconds

---

> what is the problem here? Why can't I report this project and get a new one?
>
> 4/4/2005 7:23:38 AM||Insufficient work; requesting more
> 4/4/2005 7:23:38 AM|SETI@home|Requesting 8640.00 seconds of work
> 4/4/2005 7:23:38 AM|SETI@home|Sending request to scheduler:
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> 4/4/2005 7:23:39 AM|SETI@home|Scheduler RPC to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
> 4/4/2005 7:23:39 AM|SETI@home|No schedulers responded
> 4/4/2005 7:23:39 AM|SETI@home|Deferring communication with project for 2
> minutes and 41 seconds
>
>
You must be new here. There are brief outages ALL the time, and as you see the last thing your client does is back off for 2 minutes. Just let it sit and you hould be fine.

---

This message was on main screen. You will have to wait till 4.10 is up and running again, then you can update.

April 2, 2005
We have temporarily taken down 4.10 until we can understand why some people are reporting problems with the graphics even though graphics was working for them with 4.09. 4.10 should have only increased the number of people who were able to see the S@H graphics, not decrease.

---

KeeleySam described it as brief OUTAGES but in reality it is most likely that their connections were full the second you tried to connect and it gave you that message. Boinc Incrementally increases the reconnect time with each failed effort. this is done to try to decrease the number of retries and thusly get things flowing again.

This is normal

If however it continues for a hour then they may have taken down the server. You can go to the main page and select "server status" to check on it. This works as long as the server that hosts the "status Page" is not down itself.

hope this helps

tony

---

Leave it alone. The BOINC app is designed to sort it all out for you.

---

I will just leve it be then.


thanks for the info.....

---

No problem. 99/100 the servers are down or congested.

---

Boincstats shows seti@home is Offline although status page shows all running.

---

> Boincstats shows seti@home is Offline although status page shows all running.
>

I think perhaps the servers are just congested right now. I've been able to upload results but have not been able to download anything since early this morning. I'm sure it will work itself out. :)

Dig

---

> > Boincstats shows seti@home is Offline although status page shows all
> running.
> >
>
> I think perhaps the servers are just congested right now. I've been able to
> upload results but have not been able to download anything since early this
> morning. I'm sure it will work itself out. :)
>

It's congestion. I believe they are reloading 4.09 to all the people that received 4.10. At least they did with me. We'll probably get slow again when 4.10 gets re-released and the switch back occurs.

If Boincstats or other programs that monitor server status can't reach the server, the program can't determine if it is just congestion or the servers actually being down.

---

To truly explore, one must keep an open mind...

Hi,
Having same problems.
But unfortunately, for me and 15 buddies of mine, we all have a 4 work unit per day limit. I don't know why, but it only lets me have cached up 4 work units. I am running bionc 4.25, with exactly the same settings as I had in boinc 4.19, and I was able to cache up to 15 work units at a time.
I run a pentium 4 3.4G HT, and get done with 2 every 4-5 hours.
So 4 work units means I have to connect MANY times during the day to keep things crunching.
I am not the only one. 15 others are in same boat.
Now now WU, and no way to get anymore.
Just letting you know the status of several boinxsters that are now down due to connection issue at BOINC, and a crazy new limit of 4 w/u.
Believe it or not, but BOINC responded back to us with saying there was a 4 w/u per day limit now.

John

---

Thanks, and Keep on crunchin'
John Henry KI4JPL
Sevierville TN

I started with nothing,
and I still have some of it left.
<img src="http://www.boincstats.com/stats/banner.php?cpid=989478996ebd8eadba8f0809051cdde2">

FYI, completely uninstalled and reinstalled boinc 4.25, and seti still unable to download any new work units. Same result on MANY computers now.
I am now getting my cph work unit just fine, but not seti.

John

---

Thanks, and Keep on crunchin'
John Henry KI4JPL
Sevierville TN

I started with nothing,
and I still have some of it left.
<img src="http://www.boincstats.com/stats/banner.php?cpid=989478996ebd8eadba8f0809051cdde2">

It's not and outage!

For me it's a wu crunched with the 4.10 application that's stuck with a HTTP/1.0 500 Internal Server Error.

The version 4.10 was taken back and 4.09 was set as actual for the BOINC server. Now the clients, that got the 4.10 application to crunch are trying to report their already uploaded results and the server has absolute no idea, there already was a 4.10 application and gets confused.

Simply revoking the 4.10 application isn't enough. The server must know, there are 4.10 results coming.

just my 0.02 €

---

Aloha, Uli

> Hi,
> Having same problems.
> But unfortunately, for me and 15 buddies of mine, we all have a 4 work unit
> per day limit. I don't know why, but it only lets me have cached up 4 work
> units. I am running bionc 4.25, with exactly the same settings as I had in
> boinc 4.19, and I was able to cache up to 15 work units at a time.
> I run a pentium 4 3.4G HT, and get done with 2 every 4-5 hours.
> So 4 work units means I have to connect MANY times during the day to keep
> things crunching.
> I am not the only one. 15 others are in same boat.
> Now now WU, and no way to get anymore.
> Just letting you know the status of several boinxsters that are now down due
> to connection issue at BOINC, and a crazy new limit of 4 w/u.
> Believe it or not, but BOINC responded back to us with saying there was a 4
> w/u per day limit now.
>
> John
>
Don't hold me to it but I believe 4.2x has changed the way it calculates the number or WU to request. It now calls for 1/2 what it used to. I suggest you try increasing your "connect every x.x day" in the preference.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

> It's not and outage!
>
> For me it's a wu crunched with the 4.10 application that's stuck with a
> HTTP/1.0 500 Internal Server Error.
>
> The version 4.10 was taken back and 4.09 was set as actual for the BOINC
> server. Now the clients, that got the 4.10 application to crunch are trying to
> report their already uploaded results and the server has absolute no
> idea, there already was a 4.10 application and gets confused.
>
> Simply revoking the 4.10 application isn't enough. The server must know, there
> are 4.10 results coming.
>
> just my 0.02 €
>
>
sorry to disrupt the theory, but the PC i am on right now did not upgrade (off over the weekend) and is unable to report a 4.09 unit (uploaded friday afternoon). due to its only being on 8hrs per day, i keep only 1 unit at a time on it. it has been over 3hrs without a successful scheduler reply.

mind, i am not complaining, just putting out information.

Micah

---

S@h Berkeley's Staff Friends Club

I just got through to the scheduler...
And this is the result I got (after I got a downgrade to 4.09)


SETI@home - 2005-04-04 17:03:58 - Temporarily failed download of 28au03aa.6008.2657.978394.129
SETI@home - 2005-04-04 17:03:58 - Giving up on download of 28au03aa.6008.2657.978394.129: file was not found on server
SETI@home - 2005-04-04 17:03:58 - Temporarily failed download of 28au03aa.4213.11488.372156.174
SETI@home - 2005-04-04 17:03:58 - Giving up on download of 28au03aa.4213.11488.372156.174: file was not found on server
SETI@home - 2005-04-04 17:03:58 - MD5 computation error for 28au03aa.6008.2657.978394.129: -108
SETI@home - 2005-04-04 17:03:58 - Checksum or signature error for 28au03aa.6008.2657.978394.129
SETI@home - 2005-04-04 17:03:58 - MD5 computation error for 28au03aa.4213.11488.372156.174: -108
SETI@home - 2005-04-04 17:03:58 - Checksum or signature error for 28au03aa.4213.11488.372156.174
SETI@home - 2005-04-04 17:03:58 - Unrecoverable error for result 28au03aa.6008.2657.978394.129_6 (WU download error: couldn't get input files:
28au03aa.6008.2657.978394.129: MD5 computation error
)
SETI@home - 2005-04-04 17:03:58 - Unrecoverable error for result 28au03aa.4213.11488.372156.174_5 (WU download error: couldn't get input files:
28au03aa.4213.11488.372156.174: MD5 computation error
)

Seems like these are old wu's?

fic.

My connect is set up for the max, every 10 days.
Still only lets me download 4 work units.
Something amiss here.
4.19 was fine. Would even let me bank up to 30 wu at a time.
4.25 has some issues. It won't allow me and 35 others now more than 4 per day. And we are all set to 10 days between connect time.
Seen this exact same issue on 35 computers now.
Thanks,
John

---

Thanks, and Keep on crunchin'
John Henry KI4JPL
Sevierville TN

I started with nothing,
and I still have some of it left.
<img src="http://www.boincstats.com/stats/banner.php?cpid=989478996ebd8eadba8f0809051cdde2">

>
> I just got through to the scheduler...
> And this is the result I got (after I got a downgrade to 4.09)
>
>
> SETI@home - 2005-04-04 17:03:58 - Temporarily failed download of
> 28au03aa.6008.2657.978394.129
> SETI@home - 2005-04-04 17:03:58 - Giving up on download of
> 28au03aa.6008.2657.978394.129: file was not found on server
> SETI@home - 2005-04-04 17:03:58 - Temporarily failed download of
> 28au03aa.4213.11488.372156.174
> SETI@home - 2005-04-04 17:03:58 - Giving up on download of
> 28au03aa.4213.11488.372156.174: file was not found on server
> SETI@home - 2005-04-04 17:03:58 - MD5 computation error for
> 28au03aa.6008.2657.978394.129: -108
> SETI@home - 2005-04-04 17:03:58 - Checksum or signature error for
> 28au03aa.6008.2657.978394.129
> SETI@home - 2005-04-04 17:03:58 - MD5 computation error for
> 28au03aa.4213.11488.372156.174: -108
> SETI@home - 2005-04-04 17:03:58 - Checksum or signature error for
> 28au03aa.4213.11488.372156.174
> SETI@home - 2005-04-04 17:03:58 - Unrecoverable error for result
> 28au03aa.6008.2657.978394.129_6 (WU download error: couldn't get input files:
> 28au03aa.6008.2657.978394.129: MD5 computation error
> )
> SETI@home - 2005-04-04 17:03:58 - Unrecoverable error for result
> 28au03aa.4213.11488.372156.174_5 (WU download error: couldn't get input
> files:
> 28au03aa.4213.11488.372156.174: MD5 computation error
> )
>
> Seems like these are old wu's?
>
> fic.
>
>
I just got the same thing. Tried to download two workunits originally sent out in Jul 04 but had same download errors as you. Looks like they are trying to get those old workunits out of the system. Of course they doing it when the system is having problems.

> ...
> Of course they doing it when the system is having problems.
>
LOL, thanks for mentioning it...
If i would have said that, i would be disrupted, as usual ;)

---

Aloha, Uli

I've been able to upload WU's all morning:

4/4/2005 10:00:16 AM|SETI@home|Started upload of 20ja05aa.9268.2082.767320.169_1_0
4/4/2005 10:00:21 AM|SETI@home|Finished upload of 20ja05aa.9268.2082.767320.169_1_0
4/4/2005 10:00:21 AM|SETI@home|Throughput 49129 bytes/sec

I just haven't been able to download any new ones:

4/4/2005 10:07:08 AM|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
4/4/2005 10:07:08 AM|SETI@home|No schedulers responded
4/4/2005 10:07:08 AM|SETI@home|Deferring communication with project for 15 minutes and 48 seconds


At least in my case, i feel this is probably just server congestion. :)

Dig

---