Nope. I had the app working. I came back a couple hours later and got
this error.

On Mar 2, 8:49 pm, "Chris W." <[EMAIL PROTECTED]> wrote:
> Have you done anything with the new Heroku API?  I saw the same
> problem after I pushed a repo up.
>
> On Mar 2, 7:53 pm, Mike <[EMAIL PROTECTED]> wrote:
>
> > I tried to view my app and got the following error:
>
> > ** Daemonized, any open files are closed. Look at /userapps/8590/log/
> > mongrel.19486.pid and /userapps/8590/log/mongrel.19486.log for info.
> > ** Starting Mongrel listening at 0.0.0.0:19486 /usr/lib/ruby/gems/1.8/
> > gems/mongrel-1.1.3/bin/../lib/mongrel/tcphack.rb:12:in
> > `initialize_without_backlog': Address already in use - bind(2)
> > (Errno::EADDRINUSE) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/
> > bin/../lib/mongrel/tcphack.rb:12:in `initialize' from /usr/lib/ruby/
> > gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:93:in `new' from /
> > usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:93:in
> > `initialize' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/
> > mongrel/configurator.rb:139:in `new' from /usr/lib/ruby/gems/1.8/gems/
> > mongrel-1.1.3/bin/../lib/mongrel/configurator.rb:139:in `listener'
> > from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/mongrel_rails:99:in
> > `cloaker_' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/
> > mongrel/configurator.rb:50:in `call' from /usr/lib/ruby/gems/1.8/gems/
> > mongrel-1.1.3/bin/../lib/mongrel/configurator.rb:50:in `initialize'
> > from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/mongrel_rails:84:in
> > `new' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/mongrel_rails:
> > 84:in `run' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/
> > mongrel/command.rb:212:in `run' from /usr/lib/ruby/gems/1.8/gems/
> > mongrel-1.1.3/bin/mongrel_rails:281 from /usr/bin/mongrel_rails:19:in
> > `load' from /usr/bin/mongrel_rails:19
>
> > After googling the error message, it seems that a tcp process didn't
> > shut down. Is there a way for me to fix this through heroku or do the
> > developers need to do this?
>
> > Thanks,
> > Mike
--~--~---------~--~----~------------~-------~--~----~
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