Oh well, its getting rather warm in the room where the two PCs are (the PC at the warm end is only running one WU at a time, whilst the PC at the cool end is running normally!), so, as I've kept them at 1 days cache, a little break might not be a bad thing. I'll have to get my 'nearest and dearest' to rig-up an extraction system, like you get with some tumble driers......

---

Don't take life too seriously, as you'll never come out of it alive!

Oh well, its getting rather warm in the room where the two PCs are (the PC at the warm end is only running one WU at a time, whilst the PC at the cool end is running normally!), so, as I've kept them at 1 days cache, a little break might not be a bad thing. I'll have to get my 'nearest and dearest' to rig-up an extraction system, like you get with some tumble driers......

Yeah It's warm alright, But I have 3 PCs, Actually I have 5, But one is old and the other I don't feel like bringing online yet, As 86-88F is warm enough for Me. Thankfully I have about a 4.5 day cache and fortunately 2 PCs are doing Astropulse(2 on 1 and 1 on the other). Uploads are working, But the scheduler appears to be AWOL so far, Maybe It needs one of those (Marvin)Martians to get It started again. ;)

Oh and back to the Olympics, GO USA!! Beat those Croats in Water Polo!

CRO 5
USA 7

This score is in the 4th quarter.

USA wins!! Score same as before 7-5.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I have placed a phone call to Eric and he is indisposed, but Angela will let him know as soon as he is free.

5:30pm EST update-I just uploaded and reported 3 results

---

I have placed a phone call to Eric and he is indisposed, but Angela will let him know as soon as he is free.

Ok, Although It's looking a bit better:), I hope, Marvin must have got B Bunny with His Disintegrating gun. ;)

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

If everyone would REDUCE their cache size to only TWO days, or even only ONE day, there would be adequate disk space for the system to operate efficiently.

Also, please be sure to upload and report finished workunits promptly to get them off the system.

It is the hoarding of workunits that is causing most of the problems right now.

Sure, there are occasional breakdowns, but they are usually recovered within 24 hours or less, so a TWO day cache is more than enough for most circumstances.

Well Said, Whit. I couldn't agree more!

Possible problem?
Network traffic is pretty much normal, but the Ready to Send buffer is dropping & the splitters haven't picked up the pace to fill it up again.

---

Grant
Darwin NT

Well somebody is having trouble or did.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.PC1>tracert setiathome.berkeley.edu

Tracing route to setiathome.SSL.berkeley.edu [128.32.18.150]
over a maximum of 30 hops:

1 25 ms 25 ms 25 ms L100.DSL-35.LSANCA.verizon-gni.net [71.105.32.1]
2 28 ms 29 ms 29 ms G9-0-2935.LCR-09.LSANCA.verizon-gni.net [130.81.136.14]
3 29 ms 28 ms 29 ms 130.81.28.72
4 30 ms 114 ms 30 ms 0.so-7-2-0.XT2.LAX7.ALTER.NET [152.63.10.153]
5 30 ms 30 ms 30 ms 0.so-7-0-0.XT1.LAX7.ALTER.NET [152.63.116.249]
6 30 ms 29 ms 29 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41]
7 30 ms 30 ms 30 ms 204.255.169.194
8 30 ms 29 ms 29 ms los-core-01.inet.qwest.net [205.171.32.9]
9 30 ms 30 ms 30 ms los-edge-01.inet.qwest.net [205.171.32.34]
10 68 ms 39 ms 31 ms 63.147.28.182
11 87 ms 111 ms 41 ms dc-oak-isp--lax-isp-t2.cenic.net [137.164.40.230]
12 43 ms 43 ms 43 ms inet-ucb--oak-isp.cenic.net [137.164.24.142]
13 973 ms * * g4-1.inr-202-reccev.Berkeley.EDU [128.32.0.50]
14 * 971 ms * g6-2.inr-230-spr.Berkeley.EDU [128.32.255.114]
15 * * * Request timed out.
16 * * 956 ms thinman.ssl.berkeley.edu [128.32.18.150]

Trace complete.

C:\Documents and Settings\Administrator.PC1>ping setiathome.berkeley.edu

Pinging setiathome.SSL.berkeley.edu [128.32.18.150] with 32 bytes of data:

Request timed out.
Reply from 128.32.18.150: bytes=32 time=951ms TTL=51
Request timed out.
Reply from 128.32.18.150: bytes=32 time=970ms TTL=51

Ping statistics for 128.32.18.150:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 951ms, Maximum = 970ms, Average = 960ms

C:\Documents and Settings\Administrator.PC1>

Is It this SLOOOOOOWWW for anybody else?

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Well somebody is having trouble or did.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.PC1>tracert setiathome.berkeley.edu

Tracing route to setiathome.SSL.berkeley.edu [128.32.18.150]
over a maximum of 30 hops:

1 25 ms 25 ms 25 ms L100.DSL-35.LSANCA.verizon-gni.net [71.105.32.1]
2 28 ms 29 ms 29 ms G9-0-2935.LCR-09.LSANCA.verizon-gni.net [130.81.136.14]
3 29 ms 28 ms 29 ms 130.81.28.72
4 30 ms 114 ms 30 ms 0.so-7-2-0.XT2.LAX7.ALTER.NET [152.63.10.153]
5 30 ms 30 ms 30 ms 0.so-7-0-0.XT1.LAX7.ALTER.NET [152.63.116.249]
6 30 ms 29 ms 29 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41]
7 30 ms 30 ms 30 ms 204.255.169.194
8 30 ms 29 ms 29 ms los-core-01.inet.qwest.net [205.171.32.9]
9 30 ms 30 ms 30 ms los-edge-01.inet.qwest.net [205.171.32.34]
10 68 ms 39 ms 31 ms 63.147.28.182
11 87 ms 111 ms 41 ms dc-oak-isp--lax-isp-t2.cenic.net [137.164.40.230]
12 43 ms 43 ms 43 ms inet-ucb--oak-isp.cenic.net [137.164.24.142]
13 973 ms * * g4-1.inr-202-reccev.Berkeley.EDU [128.32.0.50]
14 * 971 ms * g6-2.inr-230-spr.Berkeley.EDU [128.32.255.114]
15 * * * Request timed out.
16 * * 956 ms thinman.ssl.berkeley.edu [128.32.18.150]

Trace complete.

C:\Documents and Settings\Administrator.PC1>ping setiathome.berkeley.edu

Pinging setiathome.SSL.berkeley.edu [128.32.18.150] with 32 bytes of data:

Request timed out.
Reply from 128.32.18.150: bytes=32 time=951ms TTL=51
Request timed out.
Reply from 128.32.18.150: bytes=32 time=970ms TTL=51

Ping statistics for 128.32.18.150:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 951ms, Maximum = 970ms, Average = 960ms

C:\Documents and Settings\Administrator.PC1>

Is It this SLOOOOOOWWW for anybody else?

Haciendo ping a 128.32.18.150 con 32 bytes de datos: Respuesta desde 128.32.18.150: bytes=32 tiempo=205ms TTL=44
Respuesta desde 128.32.18.150: bytes=32 tiempo=214ms TTL=44
Respuesta desde 128.32.18.150: bytes=32 tiempo=213ms TTL=44
Respuesta desde 128.32.18.150: bytes=32 tiempo=202ms TTL=44 Estadísticas de ping para 128.32.18.150:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0%perdidos)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 202ms, Máximo = 214ms, Media = 208ms

Here now. But a few minutes ago all was very slow...


Best regards.

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Well somebody is having trouble or did.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.PC1>tracert setiathome.berkeley.edu

Tracing route to setiathome.SSL.berkeley.edu [128.32.18.150]
over a maximum of 30 hops:

1 25 ms 25 ms 25 ms L100.DSL-35.LSANCA.verizon-gni.net [71.105.32.1]
2 28 ms 29 ms 29 ms G9-0-2935.LCR-09.LSANCA.verizon-gni.net [130.81.136.14]
3 29 ms 28 ms 29 ms 130.81.28.72
4 30 ms 114 ms 30 ms 0.so-7-2-0.XT2.LAX7.ALTER.NET [152.63.10.153]
5 30 ms 30 ms 30 ms 0.so-7-0-0.XT1.LAX7.ALTER.NET [152.63.116.249]
6 30 ms 29 ms 29 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41]
7 30 ms 30 ms 30 ms 204.255.169.194
8 30 ms 29 ms 29 ms los-core-01.inet.qwest.net [205.171.32.9]
9 30 ms 30 ms 30 ms los-edge-01.inet.qwest.net [205.171.32.34]
10 68 ms 39 ms 31 ms 63.147.28.182
11 87 ms 111 ms 41 ms dc-oak-isp--lax-isp-t2.cenic.net [137.164.40.230]
12 43 ms 43 ms 43 ms inet-ucb--oak-isp.cenic.net [137.164.24.142]
13 973 ms * * g4-1.inr-202-reccev.Berkeley.EDU [128.32.0.50]
14 * 971 ms * g6-2.inr-230-spr.Berkeley.EDU [128.32.255.114]
15 * * * Request timed out.
16 * * 956 ms thinman.ssl.berkeley.edu [128.32.18.150]

Trace complete.

C:\Documents and Settings\Administrator.PC1>ping setiathome.berkeley.edu

Pinging setiathome.SSL.berkeley.edu [128.32.18.150] with 32 bytes of data:

Request timed out.
Reply from 128.32.18.150: bytes=32 time=951ms TTL=51
Request timed out.
Reply from 128.32.18.150: bytes=32 time=970ms TTL=51

Ping statistics for 128.32.18.150:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 951ms, Maximum = 970ms, Average = 960ms

C:\Documents and Settings\Administrator.PC1>

Is It this SLOOOOOOWWW for anybody else?

Haciendo ping a 128.32.18.150 con 32 bytes de datos: Respuesta desde 128.32.18.150: bytes=32 tiempo=205ms TTL=44
Respuesta desde 128.32.18.150: bytes=32 tiempo=214ms TTL=44
Respuesta desde 128.32.18.150: bytes=32 tiempo=213ms TTL=44
Respuesta desde 128.32.18.150: bytes=32 tiempo=202ms TTL=44 Estadísticas de ping para 128.32.18.150:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0%perdidos)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 202ms, Máximo = 214ms, Media = 208ms

Here now. But a few minutes ago all was very slow...


Best regards.

Yeah, I think the proverbial snail or maybe molasses was quicker for a little bit, I'm glad It cleared Itself up or that somebody somewhere cleared whatever was slowing access around here.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

What gives?
Huge amount of network traffic, yet the Ready to Send buffer is stable and the splitters are barely turning over to maintain it.

Anyone got any ideas?

---

Grant
Darwin NT

Crunchers might be refilling their caches. I had to, since I was on my last WUs.

---

Pluto will always be a planet to me.

Seti Ambassador
Not to late to order an Anni Shirt

Crunchers might be refilling their caches. I had to, since I was on my last WUs.

If that were the case, then the Ready to Send buffer would be shrinking, or the splitters would be in high gear to maintain the buffer.
I thought of existing Work Units being re-issued, but i wouldn't expect such a sustained level of traffic as we're getting at the moment.

---

Grant
Darwin NT

What gives?
Huge amount of network traffic, yet the Ready to Send buffer is stable and the splitters are barely turning over to maintain it.

Anyone got any ideas?

Erics post may give a hint. Perhaps they decided not to wait until Monday and everyone is downloading the new science app directly from here instead of another site.

---

Boinc....Boinc....Boinc....Boinc....

Erics post may give a hint. Perhaps they decided not to wait until Monday and everyone is downloading the new science app directly from here instead of another site.

Certainly seems feasible.

---

Grant
Darwin NT

Another glitch?
Heaps of network traffic, Ready to Send buffer dropping steadily, but the splitters are still just ilding along.

---

Grant
Darwin NT

Ready to Send buffer contiues to shrink. Should be out of work (other than what the splitters can provide) any minute now.

---

Grant
Darwin NT

Ready to Send buffer contiues to shrink. Should be out of work (other than what the splitters can provide) any minute now.

Can you be anymore pessimistic? The servers are working...

Results ready to send 20,123 9m
Current result creation rate 22.35/sec 0m

Ready to Send buffer contiues to shrink. Should be out of work (other than what the splitters can provide) any minute now.

Can you be anymore pessimistic? The servers are working...

Results ready to send 20,123 9m
Current result creation rate 22.35/sec 0m

Since there was almost a day between the time i made my posts, and when you made yours, it's not surprising that things had chaged somewhat.

---

Grant
Darwin NT

Since there was almost a day between the time i made my posts, and when you made yours, it's not surprising that things had chaged somewhat.

Well, no offense sir. I'm glad the scheduled downtime on Tuesday got all the processes caught up. It's hard to catch up once the system gets behind.

Seems to be a problem

29/08/2008 22:34:38|SETI@home|Finished upload of 31mr08aa.5514.7025.9.8.175_2_0
29/08/2008 22:41:26|SETI@home|Sending scheduler request: To fetch work. Requesting 2821 seconds of work, reporting 2 completed tasks
29/08/2008 22:41:31|SETI@home|Scheduler request succeeded: got 0 new tasks

See Cricket

---