Greetings,

That proxy setup worked for about half the WUs SETI was trying to send. This message was in the log:

10/2/2015 8:25:03 AM |  | BOINC can't access Internet - check network connection or proxy configuration.

I disabled the proxy and the rest of the WUs downloaded posthaste. Hopefully this will be the end of the routing situation at Berkeley for the foreseeable future. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

With all the pinging and crying going on, I find it hard to believe you folks volunteered for this. Obviously, at least on my kit, things are moving. Albeit a bit slowly. My RAC is still going up, although decelerating, and my overall credit is in the same shape.

I don't expect a personal call from Berkley to explain the problem. I only hope they get it fixed. Otherwise, my machine will continue to crunch until it is out of work, whenever that may be.

Peace and happy crunching!

---

Greetings,

... and then, perhaps I spoke too soon. I now have this showing up in the log again:

10/2/2015 8:46:35 AM | SETI@home | Sending scheduler request: To fetch work.
10/2/2015 8:46:35 AM | SETI@home | Requesting new tasks for CPU
10/2/2015 8:46:58 AM |  | Project communication failed: attempting access to reference site
10/2/2015 8:46:58 AM | SETI@home | Scheduler request failed: Couldn't connect to server
10/2/2015 8:46:59 AM |  | Internet access OK - project servers may be temporarily down.

Perhaps activating and deactivating the proxy will help... :/

Keep on BOINCing...! :)

[edit] Going back to the proxy did not work, I got the same message in the log that I posted earlier. Soooo... [/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Well, I tried the proxy mentioned above, and improved things from "can't contact server" to "timeout". Whoopie!

I tried it as SOCKS proxy and HTTP Proxy, since in my vast ignorance, I don't know which one to use...which is it, by the way? And the port is listed as 8080. Is that the normal default for a proxy, or what is?

Thanks

---

It's two full days now and I still can not reach the scheduler. My last successful connection was 10:00AM on 9/30/2015.

All of my tests come up with the same results as yesterday.
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi still just times out, and trace route still ends with:
16 * et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable.

If there is anything that I can do to help diagnose the problem, let me know.

I wonder if the problem might be at ucb--oak-agg4-10g.cenic.net [137.164.50.31].

Hope this gets figured out soon.

---

Bruce

Even proxies won't work for me, all that changes is the error message.

Like

02-Oct-2015 16:19:52 [SETI@home] Sending scheduler request: To report completed tasks.
02-Oct-2015 16:19:52 [SETI@home] Reporting 38 completed tasks
02-Oct-2015 16:19:52 [SETI@home] Requesting new tasks for AMD/ATI GPU
02-Oct-2015 16:19:52 [SETI@home] [sched_op] CPU work request: 0.00 seconds; 0.00 devices
02-Oct-2015 16:19:52 [SETI@home] [sched_op] AMD/ATI GPU work request: 425891.06 seconds; 0.00 devices
02-Oct-2015 16:20:53 [SETI@home] Scheduler request failed: HTTP service unavailable
02-Oct-2015 16:20:53 [SETI@home] [sched_op] Deferring communication for 00:07:22
02-Oct-2015 16:20:53 [SETI@home] [sched_op] Reason: Scheduler request failed

and

02-Oct-2015 16:21:25 [SETI@home] Sending scheduler request: To report completed tasks.
02-Oct-2015 16:21:25 [SETI@home] Reporting 38 completed tasks
02-Oct-2015 16:21:25 [SETI@home] Requesting new tasks for AMD/ATI GPU
02-Oct-2015 16:21:25 [SETI@home] [sched_op] CPU work request: 0.00 seconds; 0.00 devices
02-Oct-2015 16:21:25 [SETI@home] [sched_op] AMD/ATI GPU work request: 425943.46 seconds; 0.00 devices
02-Oct-2015 16:21:29 [SETI@home] Scheduler request failed: Server returned nothing (no headers, no data)

---

Greetings,

Nah, I doubt this idea is valid. But then... One never knows. Could the new Internet Protocol possibly be interfering? I'm speaking of IPv6. Nah, I cannot see that happening, knowing what little I know about IPv4 and IPv6 and how neither are compatible. IPv4 is not forward and IPv6 is not backward compatible.

Nah, forget I even mentioned it. I'm just thinking out loud... ;)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Seems to have cleared. Maybe I shouldn't have said that!

---

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

Seems to have cleared. Maybe I shouldn't have said that!

Greetings Iona,

You may just be correct. :) I just looked in my log and BOINC has successfully made contact with SETI@Home. That, without a proxy. Woohoo! :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Looks like all my machines are now making it through. No contact since 9/30 about 14:00 UTC. Now today at around 14:30 UTC all of my machines made contact. Busy filling EMPTY caches. Now on to RAC recovery.

Herb

2 days work now all reported ok and new work downloaded. Thank you to whoever fixed it.

---

Seems to have cleared. Maybe I shouldn't have said that!

Yup, that reported all my work.

BOINC Dev forums are still unreachable though.

---

Will wonders never cease? As soon as I give up, bang, the problem is resolved and WUs are downloading ....Thanks, to whoever cleared up the problem. (Sound of knuckles rapping loudly on wood...),

---

"Sour Grapes make a bitter Whine." <(0)>

183 WUs were acknowledged at 14:27 UTC and I have work coming in again. Life is good.

i keep my machines on a vpn so next time that happens im on a california network that seemed to not have any issues

---

I came down with a bad case of i don't give a crap

Normal service resumed over here.

Yup - one of my machines started receiving WUs about an hour ago, without a manual update. I just did a manual update on the other, and the floodgates opened (170 WUs in the first shot!).

Looks like all is well, at long last.

---

I'm done. This is ridiculous! I will not wast electricity and computer wear and tear waiting on an unreachable server. I'll check back in a couple days from now and if SETI still exists I may process some work again.

Berkeley IT,...........your Education tax dollars at work.........

[edit] At least the 'reset project' button clears out the 95 tasks 'waiting to report'.

And wastes all the work you did on them.

Instead of getting angry, just leave it sitting, trying on its own whenever it feels like it. As you now know, shortly after you got mad and trashed all your work, the problem was (apparently) fixed and your work would have been reported.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Since I still can't reach the BOINC domain, two traces. One done from my computer, one done with my phone.

PC:
racing route to boinc.berkeley.edu [208.68.240.115]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 6 ms 10.254.138.1
3 8 ms 7 ms 8 ms tb-rc0001-cr101-xe-0-3-4-0.core.as9143.net [213.51.186.180]
4 10 ms 10 ms 10 ms asd-tr0042-cr101-ae5-0.core.as9143.net [213.51.158.18]
5 11 ms 10 ms 10 ms lag-19.ear2.Amsterdam1.Level3.net [212.72.42.245]
6 * * 154 ms ae-2-70.ear1.SanJose1.Level3.net [4.69.152.87]
7 161 ms 155 ms 155 ms ae-2-70.ear1.SanJose1.Level3.net [4.69.152.87]
8 172 ms 173 ms 173 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46]
9 174 ms 174 ms 175 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
10 189 ms 174 ms 175 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
11 174 ms 174 ms 175 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37]
12 174 ms 175 ms 173 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101]
13 * et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable.


Phone:
1. 192.168.1.1; 2.015, 2.022, 2.161
2. 10.254.138.1; 17.766, 18.058, 18.253
3. 213.51.186.180; tb-rc0001-cr101-xe-0-3-4-0.core.as9143.net; 18.841, 21.572, 21.560
4. 213.51.158.18; asd-tr0042-cr101-ae5-0.core.as9143.net; 45.025, 45.045, 45.122
5. 212.72.42.245; lag-19.ear2.Amsterdam1.Level3.net; 45.075, 45.038, 45.278
6. *
7. *
8. 4.15.122.46; CENIC.ear1.SanJose1.Level3.net; 199.451, 199.467, 196.421
9. 137.164.46.144; dc-oak-agg4--svl-agg4-100ge.cenic.net; 196.438, 173.022, 179.544
10. 137.164.50.31; ucb--oak-agg4-10g.cenic.net; 190.762, 190.958, 190.846
11. 128.32.0.39; t2-3.inr-202-reccev.Berkeley.EDU; 190.439, 181.440
11. 128.32.0.37; t2-3.inr-201-sut.Berkeley.EDU; 182.416
12. 128.32.0.103; et3-47.inr-311-ewdc.Berkeley.EDU; 188.228
12. 128.32.0.101; et3-48.inr-311-ewdc.Berkeley.EDU; 186.585, 188.051
13. 128.32.0.101; et3-48.inr-311-ewdc.Berkeley.EDU; 975.784, !H 964.417, !H
13. 128.32.0.103; et3-47.inr-311-ewdc.Berkeley.EDU; 963.858, !H

*****
Why the different end of the route on my phone trace, when done from the same internet connection? Mind, I can't reach the domain from it either. I could earlier today with the other two traces at Mom's home and her temporary home.

Trace on PC done with tracert on Windows 7 command line.
Trace on phone done with the Traceroute app.

---

The problem persists, and as many of you already know there's a router on campus at the root of said problem. This is very similar to problems with had with our PAIX router where the solution was a memory upgrade.

Campus is aware of the issues. It's out of our control.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude