Now the AP DB is back up but splitters are down.
Getting very low on work.


Michael Miles

UL starts to give a lot of retry´s it´s only me?

---

UL starts to give a lot of retry´s it´s only me?

No same here, but nothing apparently wrong on server status page.

---

Yes, things are not looking happy on the server front this morning.

Cheers.

From this station:

24/02/2014 19:29:21 | SETI@home | Temporarily failed upload of 25no13aa.26022.184052.438086664197.12.61_0_0: connect() failed
24/02/2014 19:29:21 | SETI@home | Backing off 00:02:55 on upload of 25no13aa.26022.184052.438086664197.12.61_0_0
24/02/2014 19:29:21 | SETI@home | Started upload of 25no13aa.26022.184052.438086664197.12.58_1_0
24/02/2014 19:29:22 | | Internet access OK - project servers may be temporarily down.
24/02/2014 19:29:43 | | Project communication failed: attempting access to reference site

Yes we have a problem, hope not for a long time.

---

UL starts to give a lot of retry´s it´s only me?

It's been horribly erratic all evening - for the last three hours at least - with machines needing a periodic tickle (or kick, if you're inclined to that sort of thing).

But most uploads have got there eventually - I'm nowhere near as stuffed as I would have been if it was a total blackout.

It does seem to be only the upload server - scheduler and downloads have been fine.

UL starts to give a lot of retry´s it´s only me?

Over 30 stuck here when I looked.

20 won't move even after a little "help"

Brings back memories of BC


(Before Co-Lo) :-)

---

UL starts to give a lot of retry´s it´s only me?

It's been horribly erratic all evening - for the last three hours at least - with machines needing a periodic tickle (or kick, if you're inclined to that sort of thing).

But most uploads have got there eventually - I'm nowhere near as stuffed as I would have been if it was a total blackout.

It does seem to be only the upload server - scheduler and downloads have been fine.

Looking at the graph it looks like downloads are starting to taper off from the stuck uploads.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

They are going again...

Dont forget you can use SIVx64 to auto retry the upload queue...

Windows .... Boinc Status.... Auto Retry

---

Dont forget you can use SIVx64 to auto retry the upload queue...

Windows .... Boinc Status.... Auto Retry

Thanks for reminding me, and others.

Claggy

Dont forget you can use SIVx64 to auto retry the upload queue...

Windows .... Boinc Status.... Auto Retry

Thanks for reminding me, and others.

Claggy

Don't retry too often. Remember that modern BOINC clients don't request new work while uploads are 'active' (i.e. after retry, and before failure).

Autoretry is not working fine too. The UL allways end on error.

That must be point a network problem, trace the route to Berkeley shows that: (is in portugues sorry).

Rastreando a rota para setiathome.berkeley.edu [169.229.217.150]
com no m ximo 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 7 ms 10.29.128.1
3 10 ms 7 ms 8 ms c9118001.virtua.com.br [201.17.128.1]
4 13 ms 11 ms 15 ms embratel-T0-2-0-0-tacc01.bhe.embratel.net.br [200.167.53.17]
5 129 ms 131 ms 131 ms ebt-T0-5-3-0-tcore01.bhe.embratel.net.br [200.244.140.202]
6 132 ms 132 ms 137 ms ebt-P0-3-2-0-intl01.nyk.embratel.net.br [200.230.220.94]
7 128 ms 130 ms 129 ms ae59.edge2.NewYork1.Level3.net [4.71.230.241]
8 201 ms 197 ms 200 ms vlan60.csw1.NewYork1.Level3.net [4.69.155.62]
9 199 ms 203 ms 197 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
10 199 ms 196 ms 197 ms ae-2-2.ebr1.SanJose1.Level3.net [4.69.135.185]
11 197 ms 200 ms 199 ms ae-61-61.csw1.SanJose1.Level3.net [4.69.153.2]
12 199 ms 197 ms 198 ms ae-1-60.edge1.SanJose1.Level3.net [4.69.152.14]
13 203 ms 199 ms 199 ms CENIC.edge1.SanJose1.Level3.net [4.53.16.186]
14 205 ms 200 ms 203 ms dc-svl-core1--svl-isp1-10ge.cenic.net [137.164.47.133]
15 198 ms 199 ms 202 ms sfo-agg1--svl-agg2-10g.cenic.net [137.164.22.26]
16 204 ms 206 ms 201 ms dc-ucb--sfo-agg1-10ge.cenic.net [137.164.50.17]
17 200 ms 199 ms 199 ms t1-3.inr-201-sut.Berkeley.EDU [128.32.0.65]
18 207 ms 203 ms 203 ms t5-4.inr-211-srb.Berkeley.EDU [128.32.255.41]
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido

Yes, Huston we have a problem... again...

---

According to the server stats page, the server named bruno is responsible for running all of the SETI@home validators and the upload server process. Since there are 683 work units waiting for validation as of this writing, could bruno's CPUs be too maxed out to handle uploads adequately?

I have managed to upload most of my 200+ queue now and it's stopping and starting in spurts.
Downloads are booming in.

Dear fellows, there is absolutely no sense in forcing the upload by permanently retrying. This only worsen the problem on the server side. Simply let BOINC do it's Job. It is the same with people always reklicking on links, that obviously don't work, because the server is already overloaded.

---

Aloha, Uli

As allways, anyone has realy an ideia what is happening?

---

Don't retry too often. Remember that modern BOINC clients don't request new work while uploads are 'active' (i.e. after retry, and before failure).



It would be very nice just to get some AP work
All weekend no AP downloads

Michael

I'm back on my 2 backup projects once again, Primegrid on the 760 and Collatz on the 670.

---

Not being able to upload has at least allowed the ready-to-send buffer to refill. At least until we can upload again & then get more work...

---

Grant
Darwin NT