Started a ticket: https://github.com/whit537/www.gittip.com/issues/143

whit537 · on July 13, 2012

Okay, I'm sorry for this. I don't have good logging set up yet (see https://github.com/whit537/www.gittip.com/issues/115), so I'm not easily able to recover the traceback. :^(

Obviously this is a big problem. Has anyone else seen this?

chubot · on July 13, 2012

If it helps, when I click 0.25 cents, there is a modal popup that says "sorry something went wrong :(" I guess that is your unhandled traceback message?

If so there are a bunch of error logging services you can sign up for... or some you can download and run yourself.

After I click get that message, it appears that I'm signed out, and I have to sign back in.

I wish you luck with Gittip! It is a model I hope will become viable soon.

whit537 · on July 13, 2012

I wired up Loggly's Heroku app. It was really easy. I'm seeing a few "out of memory" errors connecting to the db. My current theory is that one of these at just the wrong moment got your account in an inconsistent state.

whit537 · on July 13, 2012

Can I ask your username?

Also, I'm back online and logging. Any chance you'd be willing to trigger the error again?

whit537 · on July 13, 2012

I've started tailing and storing logs locally to try to capture this.

whit537 · on July 13, 2012

I've got to turn my laptop off for a while. :-(

I've ticketed setting up a log tail somewhere else:

https://github.com/whit537/www.gittip.com/issues/144

I did catch one other (less significant) error by watching the logs.

I'm sorry for the bad experience. :-(