Live data from Hacker News

Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

status.linode.com

1–10 of 106 posts

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#2
They were just bought by Akamai so unfortunately things like this are bound to happen if they are trying to integrate with Akamai the way they'd need to successfully keep growing. I'm not talking just software integration but process and people integration as well. We'll see I guess!

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#3

They were just bought by Akamai so unfortunately things like this are bound to happen if they are trying to integrate with Akamai the way they'd need to successfully keep growing. I'm not talking just software integration but process and people integration as well. We'll see I guess!

I don't think many users will be affected by dhcp outage. Most linodes have fixed IPs.

Mine don't seem to be affected

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#5

They were just bought by Akamai so unfortunately things like this are bound to happen if they are trying to integrate with Akamai the way they'd need to successfully keep growing. I'm not talking just software integration but process and people integration as well. We'll see I guess!

I don't think many users will be affected by dhcp outage. Most linodes have fixed IPs. Mine don't seem to be affected

> Most linodes have fixed IPs

I would expect the opposite. Doesn't DHCP make more sense, for example, if the user creates a snapshot and restores it with a new IP? I don't use Lenode, so I can't judge, but I would expect DHCP to be default.

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#6
Arrgh! :( Just this week I needed to do some emergency rearranging of personal infrastructure, and moved one nameserver to Linode Fremont, while the other nameserver is in Linode Dallas. I was fully aware that I needed a more diverse long-term solution, but I figured "What are the chances that both Fremont and Dallas will go down in the next week or two?"

Sorry, folks. I hate that my dangerous flirting with Murphy's Law is hurting other people.

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#7

They were just bought by Akamai so unfortunately things like this are bound to happen if they are trying to integrate with Akamai the way they'd need to successfully keep growing. I'm not talking just software integration but process and people integration as well. We'll see I guess!

I don't think many users will be affected by dhcp outage. Most linodes have fixed IPs. Mine don't seem to be affected

That being said, maybe check if you have `dhclient`, `dhcpcd`, `systemd-resolved`, or (less likely) `dnsmasq` or `bind` running (htop / ps aux).

If you do, your instance may fall over after its DHCP lease expires and it then presumably fails to acquire a new one and goes all 169.254.x.x on you.

The possible counterpoint / information-vacuum bit here is that I don't know what the DHCP lease time is, so the expiry may already have happened.

IOW, apparently this started 4h ago, and so the last leases were presumably issued 4h ago, and maybe the lease length is 1h, so everything's already as dead as it's going to get, so maybe if you're not already dead, you're fine.

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#9
That’s too bad. Which other vps hosts are folks using these days besides aws/azure/gc?

If anyones thinking of switching to digitalocean, I’m currently switching linode from digitalocean who had an unforgivable, catastrophic loss of vm.

Digitalocean also prevebts customers from downloading disk image backups offsite for any kind of adult DR. Linode lets you download backup images right from the admin console.

Re: Linode Outage in Dallas, Fremont, Atlanta, Newark, and Toronto Data Centers

#10

Earlier quoted context omitted.

I don't think many users will be affected by dhcp outage. Most linodes have fixed IPs. Mine don't seem to be affected

> Most linodes have fixed IPs I would expect the opposite. Doesn't DHCP make more sense, for example, if the user creates a snapshot and restores it with a new IP? I don't use Lenode, so I can't judge, but I would expect DHCP to be default.

Default created Debian based linodes use a static IP. How they assign you the IP is they have an initial network boot script that injects that static IP into your config.

I learned this because I wanted to test image recovery of deleted linode. When I restored it, I got a different IP address from linode (the static IP assigned to me), and I couldn't connect to it. Using the web console I found the IP address was hard coded to the old one still.

Post reply on HN