And the heroku console is working fine again. Thanks

On Fri, Sep 12, 2008 at 12:25 AM, erick beans <[EMAIL PROTECTED]> wrote:

> Thanks :-)
>
>
> On Thu, Sep 11, 2008 at 11:42 PM, Morten Bagai <[EMAIL PROTECTED]> wrote:
>
>>
>> Hi Erick,
>>
>> Should be back now.
>>
>> /Morten
>>
>> On Sep 11, 2008, at 7:26 AM, erick wrote:
>>
>> >
>> > I forgot to mention, I also tried to revert to the snapshots. No
>> > luck. :-(
>> >
>> > On Sep 11, 10:23 pm, erick <[EMAIL PROTECTED]> wrote:
>> >> Hi Adam,
>> >>
>> >> I am experiencing the same problem.
>> >> Mongrel failed to start.
>> >> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.0/lib/eventmachine.rb:
>> >> 500:in `start_tcp_server': no acceptor (RuntimeError)
>> >>
>> >> As you have suggested I tried accessing urls inside the app, same
>> >> error appears.
>> >> I also tried accessing the Rails Console inside heroku and this is
>> >> what I get when I enter something:
>> >> Your mongrel is not responding, check to see if there is a crash log.
>> >>
>> >> I wish I could understand what the crash log is saying but I really
>> >> have no idea.
>> >> App is hosted at dyokbox.heroku.com
>> >>
>> >> Thanks.
>> >>
>> >> On Sep 8, 12:56 pm, "Adam Wiggins" <[EMAIL PROTECTED]> wrote:
>> >>
>> >>> Good question.  It's often challenge to figure out which things are
>> >>> problems on our side, which are problems with your app, and which
>> >>> are
>> >>> simple incompatibilities (like using a version of Rails we don't
>> >>> support).  This is just one of the things that's hard about
>> >>> building a
>> >>> platform.
>> >>
>> >>> Generally speaking, a good trick is to visit the edit url for your
>> >>> app.  If that's broken it's definitely a Heroku issue.  If it isn't,
>> >>> try deleting development.log (this is all assuming you put your app
>> >>> into development mode) and then visiting your app's front page.
>> >>> Reload the page and click on development.log; if it's empty or
>> >>> doesn't
>> >>> exist, it's probably something wrong on our end.  But if there's
>> >>> something in it, it's probably a problem with your app, and you can
>> >>> diagnose based on the contents of the log.
>> >>
>> >>> Either way, you're always welcome to post here for help.
>> >>
>> >>> Adam
>> > >
>>
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to