Обсуждение: archives.postgresql.org not responding

http server crashed?  The machine responds to ping, but connections on
port 80 get "Connection refused".
        regards, tom lane

On 23 October 2011 17:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> http server crashed?  The machine responds to ping, but connections on
> port 80 get "Connection refused".

search.postgresql.org is also down.  I reported that there appeared to
be disk errors on it yesterday.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

<p><br /> On Oct 23, 2011 6:24 PM, "Thom Brown" <<a href="mailto:thom@linux.com">thom@linux.com</a>> wrote:<br />
><br/> > On 23 October 2011 17:21, Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>>
wrote:<br/> > > http server crashed?  The machine responds to ping, but connections on<br /> > > port 80
get"Connection refused".<br /> ><br /> > <a href="http://search.postgresql.org">search.postgresql.org</a> is also
down. I reported that there appeared to<br /> > be disk errors on it yesterday.<br /> ><p>Yeah, they are both in
thesame place. We are waiting on jd both for a report on what's actually wrong, and an actual fix. <p>There was some
reportsof hardware issues, and the root fs appears to have been recounted read only. But we don't know what and why on
thoseyet. <p>/Magnus  

On 10/23/2011 09:34 AM, Magnus Hagander wrote:
>
> On Oct 23, 2011 6:24 PM, "Thom Brown" <thom@linux.com
> <mailto:thom@linux.com>> wrote:
>  >
>  > On 23 October 2011 17:21, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>  > > http server crashed?  The machine responds to ping, but connections on
>  > > port 80 get "Connection refused".
>  >
>  > search.postgresql.org <http://search.postgresql.org> is also down.  I
> reported that there appeared to
>  > be disk errors on it yesterday.
>  >
>
> Yeah, they are both in the same place. We are waiting on jd both for a
> report on what's actually wrong, and an actual fix.
>
> There was some reports of hardware issues, and the root fs appears to
> have been recounted read only. But we don't know what and why on those yet.

Working on it.

JD

>
> /Magnus
>


-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

Hello,

Technician has been dispatched. Will report back when I hear what is on 
the screen.

JD

-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

Hello,

Technician has been dispatched. Will report back when I hear what is on the screen.

On 10/24/2011 01:05 AM, Magnus Hagander wrote:
> On Sunday, October 23, 2011, Joshua D. Drake wrote:
>
>
>     Hello,
>
>     Technician has been dispatched. Will report back when I hear what is
>     on the screen.
>
>
> Hi!
>
> Slow technician, or did you forget to forward his response? ;)


PCI Parity, that was the only error. I have not yet researched it.

JD



-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579