Обсуждение: Windows binary downloads/www.enterprisedb.com off the net
Hi all! It seems like that EDB has some serious issues with (non) availability of its main domain (looks like somebody forgot to renew the domainname and is now waiting for getting the delegation added back to the TLD or such). This means that it is not impossible for our users to actually download the windows binary packages - in the interest of redundancy it would probably be a good idea if we at least mirrored those packages on our own existing mirror network as well. This would allow us to at least offer people an alternative - just in case something like this happens again... comments? Stefan
Stefan Kaltenbrunner wrote: > Hi all! > > It seems like that EDB has some serious issues with (non) availability > of its main domain (looks like somebody forgot to renew the domainname > and is now waiting for getting the delegation added back to the TLD or > such). > This means that it is not impossible for our users to actually download > the windows binary packages - in the interest of redundancy it would > probably be a good idea if we at least mirrored those packages on our > own existing mirror network as well. > This would allow us to at least offer people an alternative - just in > case something like this happens again... I talked to Jim Mlodgenski of EnterpriseDB and he is working on the problem with other EDB employees. :-O -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
2010/3/7 Bruce Momjian <bruce@momjian.us>: > Stefan Kaltenbrunner wrote: >> Hi all! >> >> It seems like that EDB has some serious issues with (non) availability >> of its main domain (looks like somebody forgot to renew the domainname >> and is now waiting for getting the delegation added back to the TLD or >> such). >> This means that it is not impossible for our users to actually download >> the windows binary packages - in the interest of redundancy it would >> probably be a good idea if we at least mirrored those packages on our >> own existing mirror network as well. >> This would allow us to at least offer people an alternative - just in >> case something like this happens again... > > I talked to Jim Mlodgenski of EnterpriseDB and he is working on the > problem with other EDB employees. :-O I think you are missing the point Stefan is trying to make. We're all sure EDB will fix the problem. But it outlines the fact that the ability for our community to be able to access the official community binaries relies solely on infrastructure the community does not control - in this caes it was the edb domain, it could also be the webservers or whatever. For example, the core RPMs are available both at the pgsqlrpms project *and* through the main mirroring network. We recommend people use the YUM repository on pgsqlrpms.org, but they are still available through the main web/ftp system (without the nice automated features and instructions, but the core packages are there) if it goes down. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
On Sun, Mar 7, 2010 at 2:04 PM, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> wrote: > Hi all! > > It seems like that EDB has some serious issues with (non) availability of > its main domain (looks like somebody forgot to renew the domainname and is > now waiting for getting the delegation added back to the TLD or such). Yeah, I'm on it :-( -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do
Bruce Momjian wrote: > Stefan Kaltenbrunner wrote: > > Hi all! > > > > It seems like that EDB has some serious issues with (non) availability > > of its main domain (looks like somebody forgot to renew the domainname > > and is now waiting for getting the delegation added back to the TLD or > > such). > > This means that it is not impossible for our users to actually download > > the windows binary packages - in the interest of redundancy it would > > probably be a good idea if we at least mirrored those packages on our > > own existing mirror network as well. > > This would allow us to at least offer people an alternative - just in > > case something like this happens again... > > I talked to Jim Mlodgenski of EnterpriseDB and he is working on the > problem with other EDB employees. :-O I can now access the Postgres binary downloads and enterprisedb.com, so at least from here, it is working. I believe it has not propogated to all other places. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
Bruce Momjian wrote: > Bruce Momjian wrote: >> Stefan Kaltenbrunner wrote: >>> Hi all! >>> >>> It seems like that EDB has some serious issues with (non) availability >>> of its main domain (looks like somebody forgot to renew the domainname >>> and is now waiting for getting the delegation added back to the TLD or >>> such). >>> This means that it is not impossible for our users to actually download >>> the windows binary packages - in the interest of redundancy it would >>> probably be a good idea if we at least mirrored those packages on our >>> own existing mirror network as well. >>> This would allow us to at least offer people an alternative - just in >>> case something like this happens again... >> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the >> problem with other EDB employees. :-O > > I can now access the Postgres binary downloads and enterprisedb.com, so > at least from here, it is working. I believe it has not propogated to > all other places. afaiks it is still dead(as in no delegation to ns1.contegix.com/ns2.contegix.com - maybe it works for you because your resolver has it still cached? Stefan
Stefan Kaltenbrunner wrote: > Bruce Momjian wrote: > > Bruce Momjian wrote: > >> Stefan Kaltenbrunner wrote: > >>> Hi all! > >>> > >>> It seems like that EDB has some serious issues with (non) availability > >>> of its main domain (looks like somebody forgot to renew the domainname > >>> and is now waiting for getting the delegation added back to the TLD or > >>> such). > >>> This means that it is not impossible for our users to actually download > >>> the windows binary packages - in the interest of redundancy it would > >>> probably be a good idea if we at least mirrored those packages on our > >>> own existing mirror network as well. > >>> This would allow us to at least offer people an alternative - just in > >>> case something like this happens again... > >> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the > >> problem with other EDB employees. :-O > > > > I can now access the Postgres binary downloads and enterprisedb.com, so > > at least from here, it is working. I believe it has not propogated to > > all other places. > > afaiks it is still dead(as in no delegation to > ns1.contegix.com/ns2.contegix.com - maybe it works for you because your > resolver has it still cached? No, it was dead for me at the time I got your email. FYI, I am not using Comcast's DNS servers but rather my own DNS server. I see Comcast does sometimes have the updated DNS, and sometimes not, so it must be propagating within their DNS farm: dig @ns.snj.comcastcommercial.net. enterprisedb.com -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
Bruce Momjian wrote: > Stefan Kaltenbrunner wrote: >> Bruce Momjian wrote: >>> Bruce Momjian wrote: >>>> Stefan Kaltenbrunner wrote: >>>>> Hi all! >>>>> >>>>> It seems like that EDB has some serious issues with (non) availability >>>>> of its main domain (looks like somebody forgot to renew the domainname >>>>> and is now waiting for getting the delegation added back to the TLD or >>>>> such). >>>>> This means that it is not impossible for our users to actually download >>>>> the windows binary packages - in the interest of redundancy it would >>>>> probably be a good idea if we at least mirrored those packages on our >>>>> own existing mirror network as well. >>>>> This would allow us to at least offer people an alternative - just in >>>>> case something like this happens again... >>>> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the >>>> problem with other EDB employees. :-O >>> I can now access the Postgres binary downloads and enterprisedb.com, so >>> at least from here, it is working. I believe it has not propogated to >>> all other places. >> afaiks it is still dead(as in no delegation to >> ns1.contegix.com/ns2.contegix.com - maybe it works for you because your >> resolver has it still cached? > > No, it was dead for me at the time I got your email. FYI, I am not > using Comcast's DNS servers but rather my own DNS server. I see Comcast > does sometimes have the updated DNS, and sometimes not, so it must be > propagating within their DNS farm: > > dig @ns.snj.comcastcommercial.net. enterprisedb.com well it is still dead as far as I can see because there is no delegation to in the root tld servers - try using "dig +trace" to make it chase the delegation down from the root servers and see if that works for you. Not sure why it works with your local resolver but I guess the reason for the comcast thingy is that some of their boxes still have the records cached from before the event... Stefan
Magnus Hagander wrote: > 2010/3/7 Bruce Momjian <bruce@momjian.us>: >> Stefan Kaltenbrunner wrote: >>> Hi all! >>> >>> It seems like that EDB has some serious issues with (non) availability >>> of its main domain (looks like somebody forgot to renew the domainname >>> and is now waiting for getting the delegation added back to the TLD or >>> such). >>> This means that it is not impossible for our users to actually download >>> the windows binary packages - in the interest of redundancy it would >>> probably be a good idea if we at least mirrored those packages on our >>> own existing mirror network as well. >>> This would allow us to at least offer people an alternative - just in >>> case something like this happens again... >> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the >> problem with other EDB employees. :-O > > I think you are missing the point Stefan is trying to make. We're all > sure EDB will fix the problem. But it outlines the fact that the > ability for our community to be able to access the official community > binaries relies solely on infrastructure the community does not > control - in this caes it was the edb domain, it could also be the > webservers or whatever. > > For example, the core RPMs are available both at the pgsqlrpms project > *and* through the main mirroring network. We recommend people use the > YUM repository on pgsqlrpms.org, but they are still available through > the main web/ftp system (without the nice automated features and > instructions, but the core packages are there) if it goes down. yeah that is pretty much what I was trying to say - we don't even have the official binaries on a community box right now, it seems sensible that we should mirror them just as we do with the other stuff so we can actually react in case something happens again. Stefan
On Sun, Mar 7, 2010 at 2:25 PM, Dave Page <dpage@pgadmin.org> wrote: > On Sun, Mar 7, 2010 at 2:04 PM, Stefan Kaltenbrunner > <stefan@kaltenbrunner.cc> wrote: >> Hi all! >> >> It seems like that EDB has some serious issues with (non) availability of >> its main domain (looks like somebody forgot to renew the domainname and is >> now waiting for getting the delegation added back to the TLD or such). > > Yeah, I'm on it :-( I've updated the URL to a temporary one so everything is working. Hopefully it won't take too long to kick the registrar back into action. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do
On Sun, Mar 7, 2010 at 10:31 AM, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> wrote: > Magnus Hagander wrote: >> 2010/3/7 Bruce Momjian <bruce@momjian.us>: >>> Stefan Kaltenbrunner wrote: >>>> Hi all! >>>> >>>> It seems like that EDB has some serious issues with (non) availability >>>> of its main domain (looks like somebody forgot to renew the domainname >>>> and is now waiting for getting the delegation added back to the TLD or >>>> such). >>>> This means that it is not impossible for our users to actually download >>>> the windows binary packages - in the interest of redundancy it would >>>> probably be a good idea if we at least mirrored those packages on our >>>> own existing mirror network as well. >>>> This would allow us to at least offer people an alternative - just in >>>> case something like this happens again... >>> >>> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the >>> problem with other EDB employees. :-O >> >> I think you are missing the point Stefan is trying to make. We're all >> sure EDB will fix the problem. But it outlines the fact that the >> ability for our community to be able to access the official community >> binaries relies solely on infrastructure the community does not >> control - in this caes it was the edb domain, it could also be the >> webservers or whatever. >> >> For example, the core RPMs are available both at the pgsqlrpms project >> *and* through the main mirroring network. We recommend people use the >> YUM repository on pgsqlrpms.org, but they are still available through >> the main web/ftp system (without the nice automated features and >> instructions, but the core packages are there) if it goes down. > > yeah that is pretty much what I was trying to say - we don't even have the > official binaries on a community box right now, it seems sensible that we > should mirror them just as we do with the other stuff so we can actually > react in case something happens again. Except - are these really a community product? When bug reports are filed on pgsql-bugs, I thought we fairly routinely referred the poster to EDB. Or am I confused? ...Robert
2010/3/8 Robert Haas <robertmhaas@gmail.com>: > On Sun, Mar 7, 2010 at 10:31 AM, Stefan Kaltenbrunner > <stefan@kaltenbrunner.cc> wrote: >> Magnus Hagander wrote: >>> 2010/3/7 Bruce Momjian <bruce@momjian.us>: >>>> Stefan Kaltenbrunner wrote: >>>>> Hi all! >>>>> >>>>> It seems like that EDB has some serious issues with (non) availability >>>>> of its main domain (looks like somebody forgot to renew the domainname >>>>> and is now waiting for getting the delegation added back to the TLD or >>>>> such). >>>>> This means that it is not impossible for our users to actually download >>>>> the windows binary packages - in the interest of redundancy it would >>>>> probably be a good idea if we at least mirrored those packages on our >>>>> own existing mirror network as well. >>>>> This would allow us to at least offer people an alternative - just in >>>>> case something like this happens again... >>>> >>>> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the >>>> problem with other EDB employees. :-O >>> >>> I think you are missing the point Stefan is trying to make. We're all >>> sure EDB will fix the problem. But it outlines the fact that the >>> ability for our community to be able to access the official community >>> binaries relies solely on infrastructure the community does not >>> control - in this caes it was the edb domain, it could also be the >>> webservers or whatever. >>> >>> For example, the core RPMs are available both at the pgsqlrpms project >>> *and* through the main mirroring network. We recommend people use the >>> YUM repository on pgsqlrpms.org, but they are still available through >>> the main web/ftp system (without the nice automated features and >>> instructions, but the core packages are there) if it goes down. >> >> yeah that is pretty much what I was trying to say - we don't even have the >> official binaries on a community box right now, it seems sensible that we >> should mirror them just as we do with the other stuff so we can actually >> react in case something happens again. > > Except - are these really a community product? When bug reports are > filed on pgsql-bugs, I thought we fairly routinely referred the poster > to EDB. Or am I confused? They are a community product, built by EDB. Kind of like the RPMs are a community product, built by either commandprompt or devrim. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
On Mon, Mar 8, 2010 at 10:13 AM, Magnus Hagander <magnus@hagander.net> wrote: >> Except - are these really a community product? When bug reports are >> filed on pgsql-bugs, I thought we fairly routinely referred the poster >> to EDB. Or am I confused? > > They are a community product, built by EDB. > > Kind of like the RPMs are a community product, built by either > commandprompt or devrim. I see, that makes sense. ...Robert
On Monday 08 March 2010 10:13:31 Magnus Hagander wrote: > 2010/3/8 Robert Haas <robertmhaas@gmail.com>: > > On Sun, Mar 7, 2010 at 10:31 AM, Stefan Kaltenbrunner > > > > <stefan@kaltenbrunner.cc> wrote: > >> Magnus Hagander wrote: > >>> 2010/3/7 Bruce Momjian <bruce@momjian.us>: > >>>> Stefan Kaltenbrunner wrote: > >>>>> Hi all! > >>>>> > >>>>> It seems like that EDB has some serious issues with (non) > >>>>> availability of its main domain (looks like somebody forgot to renew > >>>>> the domainname and is now waiting for getting the delegation added > >>>>> back to the TLD or such). > >>>>> This means that it is not impossible for our users to actually > >>>>> download the windows binary packages - in the interest of redundancy > >>>>> it would probably be a good idea if we at least mirrored those > >>>>> packages on our own existing mirror network as well. > >>>>> This would allow us to at least offer people an alternative - just in > >>>>> case something like this happens again... > >>>> > >>>> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the > >>>> problem with other EDB employees. :-O > >>> > >>> I think you are missing the point Stefan is trying to make. We're all > >>> sure EDB will fix the problem. But it outlines the fact that the > >>> ability for our community to be able to access the official community > >>> binaries relies solely on infrastructure the community does not > >>> control - in this caes it was the edb domain, it could also be the > >>> webservers or whatever. > >>> > >>> For example, the core RPMs are available both at the pgsqlrpms project > >>> *and* through the main mirroring network. We recommend people use the > >>> YUM repository on pgsqlrpms.org, but they are still available through > >>> the main web/ftp system (without the nice automated features and > >>> instructions, but the core packages are there) if it goes down. > >> > >> yeah that is pretty much what I was trying to say - we don't even have > >> the official binaries on a community box right now, it seems sensible > >> that we should mirror them just as we do with the other stuff so we can > >> actually react in case something happens again. > > > > Except - are these really a community product? When bug reports are > > filed on pgsql-bugs, I thought we fairly routinely referred the poster > > to EDB. Or am I confused? > > They are a community product, built by EDB. > > Kind of like the RPMs are a community product, built by either > commandprompt or devrim. > That being the case, there's nothing that would prevent us from just downloading a copy each release and sticking them somewhere, right? -- Robert Treat Conjecture: http://www.xzilla.net Consulting: http://www.omniti.com
2010/3/10 Robert Treat <xzilla@users.sourceforge.net>: > On Monday 08 March 2010 10:13:31 Magnus Hagander wrote: >> 2010/3/8 Robert Haas <robertmhaas@gmail.com>: >> > On Sun, Mar 7, 2010 at 10:31 AM, Stefan Kaltenbrunner >> > >> > <stefan@kaltenbrunner.cc> wrote: >> >> Magnus Hagander wrote: >> >>> 2010/3/7 Bruce Momjian <bruce@momjian.us>: >> >>>> Stefan Kaltenbrunner wrote: >> >>>>> Hi all! >> >>>>> >> >>>>> It seems like that EDB has some serious issues with (non) >> >>>>> availability of its main domain (looks like somebody forgot to renew >> >>>>> the domainname and is now waiting for getting the delegation added >> >>>>> back to the TLD or such). >> >>>>> This means that it is not impossible for our users to actually >> >>>>> download the windows binary packages - in the interest of redundancy >> >>>>> it would probably be a good idea if we at least mirrored those >> >>>>> packages on our own existing mirror network as well. >> >>>>> This would allow us to at least offer people an alternative - just in >> >>>>> case something like this happens again... >> >>>> >> >>>> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the >> >>>> problem with other EDB employees. :-O >> >>> >> >>> I think you are missing the point Stefan is trying to make. We're all >> >>> sure EDB will fix the problem. But it outlines the fact that the >> >>> ability for our community to be able to access the official community >> >>> binaries relies solely on infrastructure the community does not >> >>> control - in this caes it was the edb domain, it could also be the >> >>> webservers or whatever. >> >>> >> >>> For example, the core RPMs are available both at the pgsqlrpms project >> >>> *and* through the main mirroring network. We recommend people use the >> >>> YUM repository on pgsqlrpms.org, but they are still available through >> >>> the main web/ftp system (without the nice automated features and >> >>> instructions, but the core packages are there) if it goes down. >> >> >> >> yeah that is pretty much what I was trying to say - we don't even have >> >> the official binaries on a community box right now, it seems sensible >> >> that we should mirror them just as we do with the other stuff so we can >> >> actually react in case something happens again. >> > >> > Except - are these really a community product? When bug reports are >> > filed on pgsql-bugs, I thought we fairly routinely referred the poster >> > to EDB. Or am I confused? >> >> They are a community product, built by EDB. >> >> Kind of like the RPMs are a community product, built by either >> commandprompt or devrim. >> > > That being the case, there's nothing that would prevent us from just > downloading a copy each release and sticking them somewhere, right? AFAIK, nothing, since it only has opensource bits. Other than that we want to do this in a structured and maintainable way. And I don't mind having the primary download go just the way it does now, since that's "the price we pay for having edb doing the packaging for us", so to speak. But it'd be good to have a backup. And it'd be even easier if Dave could just upload it to the ftp mirror network once he's done putting it on the edb site ;) Dave? -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/