Yes, seeing the same error message for one of our apps on a shared db. On Apr 22, 8:41 pm, Wes Gamble <[email protected]> wrote: > Anyone seeing anything like this? > > 2011-04-22T18:35:40+00:00 app[web.1]: Started POST > "/start.json?auth_token=xxxxxxxxxx" for 66.193.54.21 at Fri Apr 22 > 11:35:40 -0700 2011 > 2011-04-22T18:35:40+00:00 app[web.1]: PGError (FATAL: connection limit > exceeded for non-superusers > > I'm assuming this is a shared DB issue still. > > Wes > > On 4/22/11 1:03 PM, John McCaffrey wrote: > > > > > > > > > > > I have a lot of single dyno free apps on heroku, and they are all > > reachable except for 2. > > >http://simple-captcha-demo.heroku.com/ is a live demo of the > > different captcha tools available in Rails. > > > 1. The app is running, (not getting the generic heroku > > 'Application Error') page, but is failing on db access > > 2. tailing the logs shows the error is 'PGError: FATAL: sorry, too > > many clients already' > > 3. I can get into heroku console, but if I try to access the db I > > also get 'PGError: FATAL: sorry, too many clients already' > > > I have another app that is a beta site for a client (so its pretty > > important that it functions) > > > 1. I get generic 'Application Error' when hitting home page > > 2. heroku logs --tail shows 'heroku[router]: Error H10 (App > > crashed) -> GET <my_website.com <http://my_website.com>>/ > > dyno=none queue=0 wait=0ms service=0ms bytes=0 > > 3. attempting to increase the number of dynos did not help > > 4. I can't get in to the console, I get the error > > > Your application is too busy to open a console session. > > Console sessions require an open dyno to use for execution. > > > I'm not freaking out about this, and I haven't opened a ticket. I'm > > not paying for this dyno yet, so I don't expect too much, and I > > realize the Heroku team has been working like crazy to resolve this. > > (last year at RailsConf they had a big outage, and had to explain it > > there at the conference, and I bet its going to be a big topic this > > year as well. Hopefully they'll be in a good position to give some > > pointers on how we could architect our apps to be ready for this) > > > I just wanted to report that almost all of my free dynos are working, > > which is great, and I'm sure these last 2 will come back soon. > > > As a side note, I learned that you can configure new relic to ping > > your app at a specified interval, and notify you if the app is not up. > > Thanks New Relic! (wish I would have had this installed 2 days ago!) > > > -John McCaffrey > > -- > > You received this message because you are subscribed to the Google > > Groups "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en.
-- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
