Thread: gemulon migration upcoming
Hi all! As mentioned in: https://www.postgresql.org/message-id/c29f7334-6695-512f-905a-919c1be676fd%40kaltenbrunner.cc we are will migrate gemulon (aka gitmaster) to a different datacenter today (20.10.2018) at ~16:00 UTC. actualy downtime is expected to only last for ~15 minutes - will send a second notice once done. Stefan
On 10/20/18 4:48 PM, Stefan Kaltenbrunner wrote: > Hi all! > > As mentioned in: > > https://www.postgresql.org/message-id/c29f7334-6695-512f-905a-919c1be676fd%40kaltenbrunner.cc > > we are will migrate gemulon (aka gitmaster) to a different datacenter > today (20.10.2018) at ~16:00 UTC. > > actualy downtime is expected to only last for ~15 minutes - will send a > second notice once done. migration completed Stefan
On 10/20/18 4:48 PM, Stefan Kaltenbrunner wrote: > Hi all! > > As mentioned in: > > https://www.postgresql.org/message-id/c29f7334-6695-512f-905a-919c1be676fd%40kaltenbrunner.cc > > we are will migrate gemulon (aka gitmaster) to a different datacenter > today (20.10.2018) at ~16:00 UTC. > > actualy downtime is expected to only last for ~15 minutes - will send a > second notice once done. migration completed Stefan
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> migration completed
Hmm ...
ssh: connect to host gitmaster.postgresql.org port 22: Network is unreachable
Maybe that's just me, but it's happening through two different ISPs.
I tried flushing local nameserver cache, but it doesn't seem that
gemulon's IP address has changed (I still see 72.32.157.198).
Should it have?
regards, tom lane
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> migration completed
Hmm ...
ssh: connect to host gitmaster.postgresql.org port 22: Network is unreachable
Maybe that's just me, but it's happening through two different ISPs.
I tried flushing local nameserver cache, but it doesn't seem that
gemulon's IP address has changed (I still see 72.32.157.198).
Should it have?
regards, tom lane
On 10/20/18 6:15 PM, Tom Lane wrote: > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: >> migration completed > > Hmm ... > > ssh: connect to host gitmaster.postgresql.org port 22: Network is unreachable > > Maybe that's just me, but it's happening through two different ISPs. hmm - please try again now... > > I tried flushing local nameserver cache, but it doesn't seem that > gemulon's IP address has changed (I still see 72.32.157.198). > Should it have? yes - that is already the new ipv4 address for gemulon. Stefan
On 10/20/18 6:15 PM, Tom Lane wrote: > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: >> migration completed > > Hmm ... > > ssh: connect to host gitmaster.postgresql.org port 22: Network is unreachable > > Maybe that's just me, but it's happening through two different ISPs. hmm - please try again now... > > I tried flushing local nameserver cache, but it doesn't seem that > gemulon's IP address has changed (I still see 72.32.157.198). > Should it have? yes - that is already the new ipv4 address for gemulon. Stefan
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> On 10/20/18 6:15 PM, Tom Lane wrote:
>> Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
>> Maybe that's just me, but it's happening through two different ISPs.
> hmm - please try again now...
Ah, I get a connection now.
>> I tried flushing local nameserver cache, but it doesn't seem that
>> gemulon's IP address has changed (I still see 72.32.157.198).
>> Should it have?
> yes - that is already the new ipv4 address for gemulon.
Yeah, now my ssh is complaining about the address change, but I see
it's still the same server key, so all good.
regards, tom lane
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> On 10/20/18 6:15 PM, Tom Lane wrote:
>> Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
>> Maybe that's just me, but it's happening through two different ISPs.
> hmm - please try again now...
Ah, I get a connection now.
>> I tried flushing local nameserver cache, but it doesn't seem that
>> gemulon's IP address has changed (I still see 72.32.157.198).
>> Should it have?
> yes - that is already the new ipv4 address for gemulon.
Yeah, now my ssh is complaining about the address change, but I see
it's still the same server key, so all good.
regards, tom lane