Thread: planetpostgresql.org is down?
Just wanted to read new PostgreSQL Weekly News from David... :-) Cannot reach it, pinging 207.173.203.166 also fails -- Best regards, Nikolay
> Just wanted to read new PostgreSQL Weekly News from David... :-) > > Cannot reach it, pinging 207.173.203.166 also fails Seems commandprompt is having network issues, and they're hosting it. They have been pinged and are assumed to be working on the problem. //Magnus
Hi, On Mon, 2006-10-16 at 16:29 +0200, Magnus Hagander wrote: > > Just wanted to read new PostgreSQL Weekly News from David... :-) > > > > Cannot reach it, pinging 207.173.203.166 also fails > > Seems commandprompt is having network issues, and they're hosting it. > They have been pinged and are assumed to be working on the problem. Yeah, we had a network problem. I don't know about the details yet. We are back online now. Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
Attachment
Magnus Hagander wrote:
>> Just wanted to read new PostgreSQL Weekly News from David... :-)
>>
>> Cannot reach it, pinging 207.173.203.166 also fails
>
> Seems commandprompt is having network issues, and they're hosting it.
> They have been pinged and are assumed to be working on the problem.
>
> //Magnus
As an answer to this. We noticed a problem at 3:30 am. After trying a
several remote administrative options, it was determined to be a
hardware issue (which can't be solved at 4:00am ;).
Network was back up by 7:10am PST or so.
Sorry for the problem, mother nature got the best of us this time.
Sincerely,
Joshua D. Drake
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake > Sent: 17 October 2006 03:15 > To: Magnus Hagander > Cc: nikolay@samokhvalov.com; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] planetpostgresql.org is down? > > Magnus Hagander wrote: > >> Just wanted to read new PostgreSQL Weekly News from David... :-) > >> > >> Cannot reach it, pinging 207.173.203.166 also fails > > > > Seems commandprompt is having network issues, and they're > hosting it. > > They have been pinged and are assumed to be working on the problem. > > > > //Magnus > > As an answer to this. We noticed a problem at 3:30 am. After trying a > several remote administrative options, it was determined to be a > hardware issue (which can't be solved at 4:00am ;). > > Network was back up by 7:10am PST or so. > > Sorry for the problem, mother nature got the best of us this time. You have organic routers/switches? Cool. /D
>> Network was back up by 7:10am PST or so. >> >> Sorry for the problem, mother nature got the best of us this time. > > You have organic routers/switches? Cool. Hand routed packets ;) > > /D > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
On Tue, Oct 17, 2006 at 06:15:00PM -0700, Joshua D. Drake wrote: > > >> Network was back up by 7:10am PST or so. > >> > >> Sorry for the problem, mother nature got the best of us this time. > > > > You have organic routers/switches? Cool. > > Hand routed packets ;) > greetings, as a backup plan to the organically routed packets, might I suggest implementation of RFC2549? regards, J