| Subject: Connections to ssl.berkeley not propagated yet? |
| From: John |
| Date: 27/07/2005, 09:18 |
Since about 22.45 pm (UTC) last night my small PC farm is working on the
BOINC-SETI reserves. I am of the believe this is as a result of the DNS
switch announced on the Technical News yesterday ...
Quote -
July 26, 2005 - 19:00 UTC
Over the past week the BOINC data server finally caught up (after moving
this service off a D220 and onto a E3500 with three times the CPU and
memory). However, after the floodgates opened up the splitters couldn't
keep up with the large backlog of work.
<Snip to the relevant bit>
ALSO! Part of this grand Gigabit switch endeavor, we had to free up a
port on the scheduler, so we made a DNS switch this morning moving all
scheduler traffic off the Cogent link and onto the Berkeley campus net.
This should be transparent to all parties involved as the scheduler
bandwidth is minimal (far less than the SETI@home web server, which is
also on the campus net), but while the new DNS maps propogate some users
will be unable to contact the scheduler. This should clear up relatively
quickly (several hours for most of the world, maybe days for the few
with ISPs that have finicky DNS servers).
COMMENT
I assume my ISP is one of those with a finicky DNS server, or the DNS
change has yet to propagate in my ISPs direction.
QUESTION
Anyone else from the UK (or other areas) currently with the problem of
"No schedulers responded" on the BOINC messages tab?
--
Hugh Janus Constipation is the thief of time, but diaorrehia waits
for no man!!