:)

Interesting twist.

---

The mind is a weird and mysterious place

Might add a bit of zest

Interesting twist.

---

:)))



........................................Gordon.........................................



:)

Upun my word, they struck upun it again!

---

Like a local place that offered limes with fish and chips.

---

Back online early today ...

---

Back online early today ...

That may because we are having a solstice?

Got a bit warm today up to 43 and there is a bit of a breeze, call it light and variable. At this temperature the body can no longer cool itself and heat stroke is likely.

---

Getting DNS errors on

Main project upload server
Main project scheduler
Beta project website

6/25/2017 3:27:53 PM | | Project communication failed: attempting access to reference site

$ ping setiathome.ssl.berkeley.edu
ping: cannot resolve setiathome.ssl.berkeley.edu: Unknown host

http://downforeveryoneorjustme.com/setiathome.ssl.berkeley.edu

---

It's bad. Very bad.

$ ping seti.berkeley.edu
ping: cannot resolve seti.berkeley.edu: Unknown host

And seti.berkeley.edu is not related to seti@home, but is the labs many other seti projects.

---

Seti seems to have crawled back, but the Boinc forums are very slow here. But this is pretty much standard these days. If you wish to support Seti you have to put up with it, or decide to go and crunch elsewhere.

Well SETI for me is not working correctly, uploads not going through, posting and moderating taking forever, whereas here is really fast. As to SETI and "having to put up with it" this is the first problem that might actually effect my machines for a long while.

Only having two slow CPU sing GPU machines, I can get an RAC of around 30K without getting problems with the odd outage here and there.

I suspect the "average users" don't notice the Tuesday outage, neither of my machine usually runs out.

$ ping setiathome.ssl.berkeley.edu
ping: cannot resolve setiathome.ssl.berkeley.edu: Unknown host

Like I said, DNS is down. These are the notes I made last time.

208.68.240.118	setiboincdata.ssl.berkeley.edu	# upload server Oct 2016
208.68.240.119	boinc2.ssl.berkeley.edu		# download server Oct 2016
208.68.240.126	setiboinc.ssl.berkeley.edu	# scheduler Oct 2016

Yep it is a DNS problem. If you can be bothered to do anything about it , Richard has shown you how to do it. Me? i'm spending the day in the garden with the DT crossword and a beer (or 2 or 3).

And for once you can bitch at the UNI. ADNS1.berkeley.edu has no clue Seti exists. Did Eric forget to pay the bill before he went on vacation? ;-)

---

Yep it is a DNS problem. If you can be bothered to do anything about it , Richard has shown you how to do it. Me? i'm spending the day in the garden with the DT crossword and a beer (or 2 or 3).

And for once you can bitch at the UNI. ADNS1.berkeley.edu has no clue Seti exists. Did Eric forget to pay the bill before he went on vacation? ;-)

It'll be interesting to watch

Domain expires: 31-Jul-2017

Someone remind me to ask Jord about this curiosity when he gets back from holiday, please...

As you can see, my last post is stamped 14:00:00 UTC. But it was 6-7 minutes before the 'Last Post' column was updated on the index pages. Do we have a master/replica database structure here, and might the current DNS problems delay transaction processing?

I ask, because it's taking ages for my browser to re-display the thread after I've posted to it (normally immediate).