<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">diary of a window system hacker</title>
<subtitle type="html"><![CDATA[
can't think of a clever byline
]]></subtitle>
<id>http://www.fooishbar.org/blog/2007/May/08</id>
<link rel="alternate" type="text/html" href="http://www.fooishbar.org/blog" />
<link rel="self" type="text/xml" href="http://www.fooishbar.org/blog/2007/May/08" />

<author>
<name>Daniel Stone</name>
<uri>http://www.fooishbar.org/blog/2007/May/08</uri>
<email>daniel@fooishbar.org</email>
</author>
<rights>Copyright 2004-2009 Daniel Stone, licensed under Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License</rights>
<generator uri="http://pyblosxom.sourceforge.net/" version="1.3.2 2/13/2006">
PyBlosxom http://pyblosxom.sourceforge.net/ 1.3.2 2/13/2006
</generator>

<updated>2007-05-08T16:27:00Z</updated>
<!-- icon?  logo?  -->

<entry>
<title type="html">freedesktop.org downtime</title>
<category term="/tech/fdo" />
<id>http://www.fooishbar.org/blog/2007/05/08/gabe-2007-05-08-17-27</id>
<updated>2007-05-08T16:27:00Z</updated>
<published>2007-05-08T16:27:00Z</published>
<link rel="alternate" type="text/html" href="http://www.fooishbar.org/blog/tech/fdo/gabe-2007-05-08-17-27" />
<content type="html">It&apos;s just not our week, I guess.  For the past couple of days,
gabe.freedesktop.org (www.fd.o, ns1.fd.o, lists.fd.o) has been playing up: it
will just mysteriously die with no explanation.  It appears to still be alive,
but we can&apos;t access it at all.  Bringing it back up yields nothing suspicious
before it dies, so we&apos;re suspecting some bad hardware.  This wouldn&apos;t be too
major a problem, bar the loss of the above-named services and dri.fd.o,
openclipart.org, and a few other services, if it weren&apos;t for other things
conspiring against us.
&lt;br /&gt;&lt;br /&gt;
All revision control services (git/CVS/SVN committing and checkout, web access
to same), Bugzilla, xorg.fd.o, people.fd.o and planet.fd.o, are on separate
machines which are unaffected by this failure.  But, unfortunately, we got less
than 24 hours notice that our secondary DNS server at MIT was being moved, and
would be offline for a while.  Two DNS servers gone.  Our third DNS server,
hosted in the UK, is still servicing requests just fine, but apparently our
registrar never noticed the update.  So the third DNS server according to the
glue records is home.keithp.com, which is also off the air right now for some
reason.
&lt;br /&gt;&lt;br /&gt;
So, ns0.bluelinux.co.uk is still serving names, and you can still access some
services if you use that, but we&apos;re not sure how long until normal DNS is back
up, let alone how long it will take us to get gabe fully fixed.
&lt;br /&gt;&lt;br /&gt;
Sorry for the outage, please bear with us.  If you think it&apos;s frustrating not
being able to check www.fd.o, try checking the remote console and watching
/proc/meminfo hopelessly spew into the serial console as you are unable to log
in ...
</content>
</entry>
</feed>
