public inbox for [email protected]help / color / mirror / Atom feed
archives.postgresql.org not responding 10+ messages / 6 participants [nested] [flat]
* archives.postgresql.org not responding @ 2008-06-21 17:57 Tom Lane <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Tom Lane @ 2008-06-21 17:57 UTC (permalink / raw) To: pgsql-www I've been seeing connection timeouts for the last little while ... regards, tom lane ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-21 18:01 Stefan Kaltenbrunner <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Stefan Kaltenbrunner @ 2008-06-21 18:01 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: pgsql-www Tom Lane wrote: > I've been seeing connection timeouts for the last little while ... AFAIK - currently there is maintainance work going on at the CMD hosting facility besides archives also search,planet and the buildfarm are down currently ... Stefan ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 06:14 Joshua D. Drake <[email protected]> parent: Stefan Kaltenbrunner <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Joshua D. Drake @ 2008-06-22 06:14 UTC (permalink / raw) To: Stefan Kaltenbrunner <[email protected]>; +Cc: Tom Lane <[email protected]>; pgsql-www Stefan Kaltenbrunner wrote: > Tom Lane wrote: >> I've been seeing connection timeouts for the last little while ... > > AFAIK - currently there is maintainance work going on at the CMD hosting > facility besides archives also search,planet and the buildfarm are down > currently ... Longer than expected, but everything should be up but buildfarm. I am out of caffeine at this point but will look at buildfarm first thing in the morning. Joshua D. Drake > > > Stefan > ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 06:45 Tom Lane <[email protected]> parent: Joshua D. Drake <[email protected]> 0 siblings, 2 replies; 10+ messages in thread From: Tom Lane @ 2008-06-22 06:45 UTC (permalink / raw) To: Joshua D. Drake <[email protected]>; +Cc: Stefan Kaltenbrunner <[email protected]>; pgsql-www "Joshua D. Drake" <[email protected]> writes: > Stefan Kaltenbrunner wrote: >> Tom Lane wrote: >>> I've been seeing connection timeouts for the last little while ... >> >> AFAIK - currently there is maintainance work going on at the CMD hosting >> facility besides archives also search,planet and the buildfarm are down >> currently ... > Longer than expected, but everything should be up but buildfarm. I am > out of caffeine at this point but will look at buildfarm first thing in > the morning. Fully understand about lack of caffeine --- but if this was a planned service outage, some advance notice to pgsql-www would've been appropriate, no? Or did I just miss it? regards, tom lane ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 19:43 Joshua D. Drake <[email protected]> parent: Tom Lane <[email protected]> 1 sibling, 0 replies; 10+ messages in thread From: Joshua D. Drake @ 2008-06-22 19:43 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Stefan Kaltenbrunner <[email protected]>; pgsql-www Tom Lane wrote: > "Joshua D. Drake" <[email protected]> writes: >> Stefan Kaltenbrunner wrote: >>> Tom Lane wrote: > Fully understand about lack of caffeine --- but if this was a planned > service outage, some advance notice to pgsql-www would've been > appropriate, no? Or did I just miss it? I sent it to sysadmins, but your point is taken. I will send to both in the future. Joshua D. Drake ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 21:43 Robert Treat <[email protected]> parent: Tom Lane <[email protected]> 1 sibling, 1 reply; 10+ messages in thread From: Robert Treat @ 2008-06-22 21:43 UTC (permalink / raw) To: pgsql-www; +Cc: Tom Lane <[email protected]>; Joshua D. Drake <[email protected]>; Stefan Kaltenbrunner <[email protected]> On Sunday 22 June 2008 02:45:07 Tom Lane wrote: > "Joshua D. Drake" <[email protected]> writes: > > Stefan Kaltenbrunner wrote: > >> Tom Lane wrote: > >>> I've been seeing connection timeouts for the last little while ... > >> > >> AFAIK - currently there is maintainance work going on at the CMD hosting > >> facility besides archives also search,planet and the buildfarm are down > >> currently ... > > > > Longer than expected, but everything should be up but buildfarm. I am > > out of caffeine at this point but will look at buildfarm first thing in > > the morning. > > Fully understand about lack of caffeine --- but if this was a planned > service outage, some advance notice to pgsql-www would've been > appropriate, no? Or did I just miss it? > He sent notice to sysadmins, but not pgsql-www. I'm not sure what the policy is, but seems like it might be good to send these outage notices to a more public list as well. (For example, there is currently a notice from Marc about doing maintanance on mail.postgresql.org which I believe was supposed to happen last night, though we haven't recieved a followup mail yet) -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 22:05 Marc G. Fournier <[email protected]> parent: Robert Treat <[email protected]> 0 siblings, 2 replies; 10+ messages in thread From: Marc G. Fournier @ 2008-06-22 22:05 UTC (permalink / raw) To: Robert Treat <[email protected]>; pgsql-www; +Cc: Tom Lane <[email protected]>; Joshua D. Drake <[email protected]>; Stefan Kaltenbrunner <[email protected]> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If it involves web infrastructure (ie. archives.postgresql.org), it should go to pgsql-www ... if it involves non-web infrastructure (ie. ftp) it should go to sysadmins ... - --On Sunday, June 22, 2008 17:43:13 -0400 Robert Treat <[email protected]> wrote: > On Sunday 22 June 2008 02:45:07 Tom Lane wrote: >> "Joshua D. Drake" <[email protected]> writes: >> > Stefan Kaltenbrunner wrote: >> >> Tom Lane wrote: >> >>> I've been seeing connection timeouts for the last little while ... >> >> >> >> AFAIK - currently there is maintainance work going on at the CMD hosting >> >> facility besides archives also search,planet and the buildfarm are down >> >> currently ... >> > >> > Longer than expected, but everything should be up but buildfarm. I am >> > out of caffeine at this point but will look at buildfarm first thing in >> > the morning. >> >> Fully understand about lack of caffeine --- but if this was a planned >> service outage, some advance notice to pgsql-www would've been >> appropriate, no? Or did I just miss it? >> > > He sent notice to sysadmins, but not pgsql-www. I'm not sure what the policy > is, but seems like it might be good to send these outage notices to a more > public list as well. (For example, there is currently a notice from Marc > about doing maintanance on mail.postgresql.org which I believe was supposed > to happen last night, though we haven't recieved a followup mail yet) > > -- > Robert Treat > Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL > > -- > Sent via pgsql-www mailing list ([email protected]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [email protected] MSN . [email protected] Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhezKEACgkQ4QvfyHIvDvMovgCfSVhDZUHJNvhUcvJnppUy265P iBoAn0WbfwLgXe13PlPb50Z9esjBHDJu =th8R -----END PGP SIGNATURE----- ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 22:22 Joshua D. Drake <[email protected]> parent: Marc G. Fournier <[email protected]> 1 sibling, 0 replies; 10+ messages in thread From: Joshua D. Drake @ 2008-06-22 22:22 UTC (permalink / raw) To: Marc G. Fournier <[email protected]>; +Cc: Robert Treat <[email protected]>; pgsql-www; Tom Lane <[email protected]>; Stefan Kaltenbrunner <[email protected]> Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > If it involves web infrastructure (ie. archives.postgresql.org), it should go > to pgsql-www ... if it involves non-web infrastructure (ie. ftp) it should go > to sysadmins ... Yeah, like I said, next time I will just email both. There are too many "other" facets to what you just said. Joshua D. Drake ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-22 22:43 Tom Lane <[email protected]> parent: Marc G. Fournier <[email protected]> 1 sibling, 1 reply; 10+ messages in thread From: Tom Lane @ 2008-06-22 22:43 UTC (permalink / raw) To: Marc G. Fournier <[email protected]>; +Cc: Robert Treat <[email protected]>; pgsql-www; Joshua D. Drake <[email protected]>; Stefan Kaltenbrunner <[email protected]> "Marc G. Fournier" <[email protected]> writes: > If it involves web infrastructure (ie. archives.postgresql.org), it > should go to pgsql-www ... if it involves non-web infrastructure > (ie. ftp) it should go to sysadmins ... Well, the point to me is that planned outages should be announced somewhere where non-admins can see them. Which service is involved shouldn't determine that. regards, tom lane ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: archives.postgresql.org not responding @ 2008-06-23 01:48 Bruce Momjian <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 0 replies; 10+ messages in thread From: Bruce Momjian @ 2008-06-23 01:48 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Marc G. Fournier <[email protected]>; Robert Treat <[email protected]>; pgsql-www; Joshua D. Drake <[email protected]>; Stefan Kaltenbrunner <[email protected]> Tom Lane wrote: > "Marc G. Fournier" <[email protected]> writes: > > If it involves web infrastructure (ie. archives.postgresql.org), it > > should go to pgsql-www ... if it involves non-web infrastructure > > (ie. ftp) it should go to sysadmins ... > > Well, the point to me is that planned outages should be announced > somewhere where non-admins can see them. Which service is involved > shouldn't determine that. Agreed. There should be a join-able list that will tell us about such things. I can't join sysadmins to find out about outages, and www seems to fit that role fine. -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ^ permalink raw reply [nested|flat] 10+ messages in thread
end of thread, other threads:[~2008-06-23 01:48 UTC | newest] Thread overview: 10+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2008-06-21 17:57 archives.postgresql.org not responding Tom Lane <[email protected]> 2008-06-21 18:01 ` Stefan Kaltenbrunner <[email protected]> 2008-06-22 06:14 ` Joshua D. Drake <[email protected]> 2008-06-22 06:45 ` Tom Lane <[email protected]> 2008-06-22 19:43 ` Joshua D. Drake <[email protected]> 2008-06-22 21:43 ` Robert Treat <[email protected]> 2008-06-22 22:05 ` Marc G. Fournier <[email protected]> 2008-06-22 22:22 ` Joshua D. Drake <[email protected]> 2008-06-22 22:43 ` Tom Lane <[email protected]> 2008-06-23 01:48 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox