I'm getting a "Request limit exceeded" error in my EC2 panel.
Tell HN: Heroku is Down (update: recovering as of 10PM PST)
91–100 of 116 posts
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#92If Heroku moved off of AWS they'd have better uptime and lower prices.
I'm sure that some Heroku customers already depend on the fact they're hosted on EC2 for accessing other instances or AWS services.
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#93I've had so much more downtime with heroku/AWS than I ever had back when I was running my sites on slicehost. I also feel like I've let my admin skills deteriorate because I've been dependent on heroku. Back when I was running everything myself, worst case scenario I could set up a new VPS from a backup in another datacenter. Now if heroku goes out I just have to twiddle my thumbs while I wait for updates.
...or you can keep on working knowing that your services will be magically back online without you lifting a finger.
except for any potential data loss that just happened
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#94Earlier quoted context omitted.
It looks like Amazon are worse at reporting their outages than Heroku...
During the previous outage (which wasn't AWS related), Heroku's status page was down entirely (among other things, it relied on static assets from heroku.com), so I can't say I agree with that.
Yep, but they saw that flaw and addressed it and it's ok for the time being. Amazons has been and still is crappy.
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#95Seems like someone posted a link to a project that made self-hosting a previously Heroku hosted site simple, but I can't find it now... ...would be cool if there was a Linux package (or distro) that you could boot-up and then just change your git remote to and have your app up-and-running on your own hardware.
I made Dokuen a few weeks ago, maybe that's what you're thinking of? If you're willing to live with a few warts, it's working pretty well for my personal use. My blog is still on Heroku so you can't really read about it now, but you can check out the code. https://github.com/peterkeen/dokuen
This looks very interesting; thanks for the link!
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#96I've had so much more downtime with heroku/AWS than I ever had back when I was running my sites on slicehost. I also feel like I've let my admin skills deteriorate because I've been dependent on heroku. Back when I was running everything myself, worst case scenario I could set up a new VPS from a backup in another datacenter. Now if heroku goes out I just have to twiddle my thumbs while I wait for updates.
I understand what you are saying. I host most of my projects on Rackspace. I've been intending to convert current ideas to Heroku because learning SysAdmin stuff doesn't seem to have much upside potential. However, these multiple outages while Rackspace (seemingly) keeps chugging along are discouraging. That being said, every Heroku outage makes front page of HN, and there could have been Rackspace downtimes much more often that I didn't notice.
Eh, I'll probably continue converting to Heroku and not look back.
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#97That's odd, because I thought the error occurred in my application. No? You sure? Just look at this error message, "An error occurred in the application and your page could not be served." Oh, so you mean the error message aren't accurate? That even though the error is actually above Heroku, a much greater failure, that my application will still be blamed, and that's what my users and bosses are going to see? And you…
You can serve your own error pages instead of Heroku's and show your boss whatever you want. They're specified as URLs, so they can be hosted on some other platform. I don't know if that feature works when AWS is failing Heroku, but if Heroku's up enough to serve the error page, maybe it's up enough to serve the error page you configured instead of its own.
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#98That's odd, because I thought the error occurred in my application. No? You sure? Just look at this error message, "An error occurred in the application and your page could not be served." Oh, so you mean the error message aren't accurate? That even though the error is actually above Heroku, a much greater failure, that my application will still be blamed, and that's what my users and bosses are going to see? And you…
Isn't it your fault you didn't build a fault tolerant application? The first rule of building services is assume everything is broken.
Honestly, I haven't the resources to guarantee site uptime, and have accepted this will happen as a result; my complaint was more targeted at the default error messages.
It seems this can be changed, though, fortunately for Heroku.
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#99Related: Right now when I try to cat /proc/mdstat or use mdstat to look at my RAID status, it just hangs. Seems it's trying to contact the EBS volumes and it's just failing. Any way to actually view my raid status?
It's probably best not to muck around with the RAID right now when the drives it thinks are there aren't actually there. If it were me, I wouldn't touch anything until Amazon fixes itself.
Re: Tell HN: Heroku is Down (update: recovering as of 10PM PST)
#100That's odd, because I thought the error occurred in my application. No? You sure? Just look at this error message, "An error occurred in the application and your page could not be served." Oh, so you mean the error message aren't accurate? That even though the error is actually above Heroku, a much greater failure, that my application will still be blamed, and that's what my users and bosses are going to see? And you…
You can serve your own error pages instead of Heroku's and show your boss whatever you want. They're specified as URLs, so they can be hosted on some other platform. I don't know if that feature works when AWS is failing Heroku, but if Heroku's up enough to serve the error page, maybe it's up enough to serve the error page you configured instead of its own. https://devcenter.heroku.com/articles/error-pages
Solid, thanks for the heads up!