<p dir="ltr"><br /> On Oct 6, 2015 4:36 AM, "Stephen Frost" <<a
href="mailto:sfrost@snowman.net">sfrost@snowman.net</a>>wrote:<br /> ><br /> > * Bruce Momjian (<a
href="mailto:bruce@momjian.us">bruce@momjian.us</a>)wrote:<br /> > > I am seeing a 503 error from our
archives:<br/> > ><br /> > > <a
href="http://www.postgresql.org/message-id/54B70C3F.4020102@dunslane.net">http://www.postgresql.org/message-id/54B70C3F.4020102@dunslane.net</a><br
/>> ><br /> > > Error 503 Backend fetch failed<br /> > ><br /> > > Backend
fetchfailed<br /> > > Guru Meditation:<br /> > ><br /> > > XID: 13756651<br /> >
><br/> > > Varnish cache server<br /> ><br /> > Yeah, zalkon was having issues resolving DNS for
wrigleys. Seemed to be<br /> > some kind of intermittent ipv6 or possibly ipv6+DNS issue. Also appears<br /> >
tohave now cleared by itself..<br /><p dir="ltr">Just to be clear, neither DNS or wrigleys have anything at all to do
withdelivering the archives Web pages. And I'm pretty sure the backend communication is actually ally v4 on that one.<p
dir="ltr">Thatsaid, general network issues obviously does, so that's probably what the issue was. <p dir="ltr">/Magnus