"service unavailable" in Heroku instance
Closed this issue · 6 comments
Hah, interesting. Well, there's quite a lot of things this could be. Does Heroku give you access to the server logs?
Aha:
2013-08-23T17:36:52.597344+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
Well, that makes sense. Is there a way the quota could be detected and have it so people wouldn't try uploading things bigger than that?
https://devcenter.heroku.com/articles/dynos#memory-behavior says that R14 shouldn't actually kill it, though. I didn't get any R15s.
All logs: http://ix.io/7wz
Ahh, that does make a lot of sense. I'm actually running into the same problem on my server.
Memory management and figuring out what the actual max upload size is (and getting a server with more memory) is next on my todo list. I'm thinking of upping the limit significantly once I get the new server and charging $1/month for people that want to upload files over 50 megs (or more than 500 files a month or something).