The more things change, the more they stay the same. |
![]() |
| log in |
Message boards : Technical News : The more things change, the more they stay the same.
Previous · 1 . . . 4 · 5 · 6 · 7 · 8 · 9 · 10 · Next
| Author | Message |
|---|---|
|
MEEP MEEEP | |
| ID: 977694 · | |
MEEP MEEEP It's not that the splitters have failed, it's that there's nothing for them to work on - and I'm wondering about that... have we used up all of SETI's "banked" data? Is Aracibo shut down again? Did someone forget to "hang a tape/some tapes"? :-) Try looking here before posting! ____________ . | |
| ID: 977736 · | |
Try looking here before posting! and if you would have looked 2.5 hours sooner, you would have seen the same thing as me, lots of RED. you might choose to look at it as they are out of work to split, me FAILED. ____________ | |
| ID: 977924 · | |
|
and now.... | |
| ID: 978177 · | |
|
So what happened to the posts from Matt or Eric? Did the guys quit on us? Its been almost a month since Matt's last post. | |
| ID: 978186 · | |
So what happened to the posts from Matt or Eric? Did the guys quit on us? Its been almost a month since Matt's last post. How about you having a look in the SETI@home Staff Blog? Claggy | |
| ID: 978191 · | |
|
See Where's Matt? in the SETI@home Staff Blog. | |
| ID: 978193 · | |
|
Bad luck? Or no luck at all? It appears there are back-to-back problems with SETI lately. | |
| ID: 978198 · | |
Try looking here before posting! There was still a lot of red (in the splitters area...) when I looked... but red for a splitter means that that splitter ran out of work, or has otherwise failed: to see which, see the right-hand column, labeled "Splitter Status" - if there's only one "tape" shown there, (as was the case when I looked Friday morning) then work has run out! BTW, the red "Not running" means (according to the definition below the "server Status" column) "Program failed or ran out of work" - with splitters, the second condition is most commonly the case... Dittoing the others that are having problems uploading, reporting, and getting new work... ____________ . | |
| ID: 978222 · | |
|
Results ready to send 54,476 (much more than last days) | |
| ID: 978231 · | |
|
Hi! c:\Download>pathping -n 128.32.18.150 -w 100000
Śledzenie trasy do 128.32.18.150 z maksymalną liczbą 30 przeskoków.
0 10.115.69.176
1 10.9.216.1
2 10.9.216.2
3 10.9.221.5
4 10.9.220.253
5 213.158.195.53
6 213.158.198.198
7 213.248.89.153
8 80.91.250.40
9 80.91.249.151
10 80.91.253.45
11 80.91.253.154
12 213.244.165.249
13 4.69.139.161
14 4.69.132.133
15 4.69.137.78
16 4.69.134.74
17 4.69.134.121
18 4.69.135.185
19 4.69.134.242
20 4.68.18.3
21 4.53.16.186
22 137.164.24.106
23 128.32.0.58
24 128.32.255.110
25 * * *
Wyliczanie statystyk dla 600 sekund...
Źródło Ten węzeł/Łącze
Przeskok RTT Zgubione/wysłane = Pct Zgubione/wysłane = adres Pct
0 10.115.69.176
2/ 100 = 2% |
1 331ms 3/ 100 = 3% 1/ 100 = 1% 10.9.216.1
0/ 100 = 0% |
2 321ms 3/ 100 = 3% 1/ 100 = 1% 10.9.216.2
0/ 100 = 0% |
3 328ms 3/ 100 = 3% 1/ 100 = 1% 10.9.221.5
0/ 100 = 0% |
4 341ms 3/ 100 = 3% 1/ 100 = 1% 10.9.220.253
0/ 100 = 0% |
5 351ms 3/ 100 = 3% 1/ 100 = 1% 213.158.195.53
0/ 100 = 0% |
6 346ms 3/ 100 = 3% 1/ 100 = 1% 213.158.198.198
0/ 100 = 0% |
7 373ms 3/ 100 = 3% 1/ 100 = 1% 213.248.89.153
0/ 100 = 0% |
8 392ms 3/ 100 = 3% 1/ 100 = 1% 80.91.250.40
0/ 100 = 0% |
9 382ms 3/ 100 = 3% 1/ 100 = 1% 80.91.249.151
0/ 100 = 0% |
10 383ms 3/ 100 = 3% 1/ 100 = 1% 80.91.253.45
0/ 100 = 0% |
11 400ms 3/ 100 = 3% 1/ 100 = 1% 80.91.253.154
0/ 100 = 0% |
12 --- 100/ 100 =100% 98/ 100 = 98% 213.244.165.249
0/ 100 = 0% |
13 369ms 3/ 100 = 3% 1/ 100 = 1% 4.69.139.161
0/ 100 = 0% |
14 391ms 3/ 100 = 3% 1/ 100 = 1% 4.69.132.133
0/ 100 = 0% |
15 479ms 3/ 100 = 3% 1/ 100 = 1% 4.69.137.78
0/ 100 = 0% |
16 466ms 2/ 100 = 2% 0/ 100 = 0% 4.69.134.74
0/ 100 = 0% |
17 481ms 2/ 100 = 2% 0/ 100 = 0% 4.69.134.121
0/ 100 = 0% |
18 550ms 2/ 100 = 2% 0/ 100 = 0% 4.69.135.185
0/ 100 = 0% |
19 534ms 2/ 100 = 2% 0/ 100 = 0% 4.69.134.242
0/ 100 = 0% |
20 --- 100/ 100 =100% 98/ 100 = 98% 4.68.18.3
0/ 100 = 0% |
21 517ms 2/ 100 = 2% 0/ 100 = 0% 4.53.16.186
0/ 100 = 0% |
22 517ms 2/ 100 = 2% 0/ 100 = 0% 137.164.24.106
0/ 100 = 0% |
23 505ms 2/ 100 = 2% 0/ 100 = 0% 128.32.0.58
0/ 100 = 0% |
24 512ms 2/ 100 = 2% 0/ 100 = 0% 128.32.255.110
Śledzenie zakończone.
c:\Download> Regards Wojtekz ____________ | |
| ID: 978279 · | |
|
Uploading results, downloading new work units and even updating one's project has become such a mission that one is forced to suggest shutting the project down until it can be made to work reliably at least some of the time. While I do appreciate the efforts of the project leaders, let us not forget that the contributors to the project are the ones who are paying to make it run through increased electricity bills - something we are no doubt happy to do, but I think users would be happier contributing to a project that actually works more often than not and bears some fruit. | |
| ID: 978398 · | |
Uploading results, downloading new work units and even updating one's project has become such a mission that one is forced to suggest shutting the project down until it can be made to work reliably at least some of the time. While I do appreciate the efforts of the project leaders, let us not forget that the contributors to the project are the ones who are paying to make it run through increased electricity bills - something we are no doubt happy to do, but I think users would be happier contributing to a project that actually works more often than not and bears some fruit. To which more damage to the project might happen if it were to close down since things more than likely won't change. To make the project more reliable, you'd need more hardware and more manpower thrown at the problem, both of which costs money. Since the project has neither, it won't be any better after it's shut down. Further, if users are unhappy about paying their electric bill for a distributed computing project that is having problems, there are two answers to rectify the situation more realistically: 1) join another project to keep those CPUs busy and thus not "waste" any electricity or failing that 2) accept that the project is doing the best they can and there will be periods of understandable and unavoidable downtime given the resources they have, and simply accept that if you don't have any work, your wasted electric bill is on you given the 1st option. ____________ | |
| ID: 978411 · | |
Uploading results, downloading new work units and even updating one's project has become such a mission that one is forced to suggest shutting the project down until it can be made to work reliably at least some of the time. While I do appreciate the efforts of the project leaders, let us not forget that the contributors to the project are the ones who are paying to make it run through increased electricity bills - something we are no doubt happy to do, but I think users would be happier contributing to a project that actually works more often than not and bears some fruit. You forgot #3: Send some cash to keep the lights on. ____________ BOINC WIKI | |
| ID: 978491 · | |
|
Good Morning, | |
| ID: 978580 · | |
|
Uploads in queue here also since last night, at least now I'm sure its not my fault | |
| ID: 978615 · | |
|
[quote]...with splitters, the second condition is most commonly the case...[quote] | |
| ID: 978616 · | |
looks like the project completely went off line last night at 24:00, humm... Exactly at midnight GMT? Perhaps some obscure problem related to Daylight Savings Time starting early this year in the USA? {Pure conjecture....} ____________ | |
| ID: 978633 · | |
looks like the project completely went off line last night at 24:00, humm... No, it was midnight, PST (-8 then, -7 now with DST) C ____________ Join Team MacNN | |
| ID: 978647 · | |
it doesn't request the right amount of work for the cpu or gpu, and then sometimes it gorges! What version of BOINC are you using? I'd certainly have to agree with ^^ statement. And the problem seems to be in the 6.10.xx series, after 6.10.18. At least for me. With 7 GPU's running in one cruncher (not using CPU's to crunch)... I usually kept about 3,000 work units in the queue. One morning I awoke to find almost 6,000 WU's in the queue. And I had the "Addtional Work Buffer" set to only 5.95 days. That was in BOINC 6.10.36. It suddenly gorged overnight. I dropped back to 6.10.29 just an hour before the latest SETI problems started so I have no idea if 6.10.29 will handle the work queue right. ____________ I DONATE money to SETI@home.... DO YOU? I'm just slowly BOINC'ing along. Hey... ET... you have a sister who likes earthlings? | |
| ID: 978679 · | |
Message boards : Technical News : The more things change, the more they stay the same.
| Copyright © 2013 University of California |