tburch/jsonblob

The API is 500ing

captn3m0 opened this issue · 5 comments

jsonblob was working fine, and all of a sudden, we started receiving 500, server errors from the API.

The homepage works fine, but the xhr on the save event is 500ing as well.

Everything seems to be working for me right now. I tried saving from the homepage (POST), updating a blob (PUT), and retrieving a blob (GET). Is there a particular blob that's still returning errors?

Every blob I had was returning errors at that time (its fine now). Can you check the logs possibly?

It looks like there were some connectivity issues to MongoHQ.

Is mongo down again?

I'm not sure what was going on. It looked like the Heroku Dyno wasn't responding. I ended up bouncing it twice and now it seems to be responding. I have CloudFlare in front of Heroku, so that's why the site responds but the API doesn't.

I've been working on porting jsonblob from Grails to DropWizard because it uses about 75% less memory and I'm running close to the max 512mb that I get for free with the Heroku Dyno. I think getting to close to the maximum memory might be causing problems (it's currently running at 447MB of 512 MB after the restart)...