Forum: Ruby on Rails how to debug failure on start from InstantRails

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
2b56c94654029f0b6e400f127b74921d?d=identicon&s=25 lunaclaire (Guest)
on 2007-07-12 01:17
(Received via mailing list)
I made some change that I cant track down by looking at source code
that prevents my app from starting when launching from InstantRails.

The console window that InstantRails opens displays some info, but it
closes the window before I can read any of it, so does anybody have a
tip on how I can "freeze" that window to see what's getting spit back?

Alternatively, is there a log file that would give me some info on
what's failing? (I tried development.log but that only seems to have
logged stuff from the last time I launched and ran successfully)

TIA
2b891e820c238ded365d035771603f21?d=identicon&s=25 Bill Walton (Guest)
on 2007-07-12 03:45
(Received via mailing list)
Hi,

lunaclaire wrote:

> I made some change that I cant track down by looking
> at source code that prevents my app from starting when
> launching from InstantRails.

It's possible, but somewhat unlikely, that your problem is rooted in
your
code.

> The console window that InstantRails opens displays some
> info, but it closes the window before I can read any of it, so
> does anybody have a tip on how I can "freeze" that window
> to see what's getting spit back?

Launch a command window, rather than trying to start your app, from IR
manager.  I -> Rails Applications -> Launch Ruby Console Window.  If
this
window opens and stays open, try to start mongrel with
c:\{RAILS_ROOT}\mongrel_rails start
If the window closes shortly thereafter, you've got a port conflict you
need
to investigate.  Run netstat -a to find out what posts are being used by
other apps and either shut down the one that's running on mongrel's
default
port (3000 or 3001) or start mongrel on another port (see
mongrl_rails --help).  Holler if you need more help.

hth,
Bill
2b56c94654029f0b6e400f127b74921d?d=identicon&s=25 lunaclaire (Guest)
on 2007-07-13 01:15
(Received via mailing list)
Thanks Bill -

Didnt know that I could do things that way to start mongrel and keep
the window open to see the err msgs.

That helped me see a typo created by my editor (UltraEdit) when it
tried to be smart and "correct" what it thought was a keyword by
putting a leading upper case on a config.action_controller.xxx
property in development.rb

all cleaned up now, thanks to you
2b891e820c238ded365d035771603f21?d=identicon&s=25 Bill Walton (Guest)
on 2007-07-13 01:59
(Received via mailing list)
Happy that helped.

Best regards,
Bill

----- Original Message -----
From: "lunaclaire" <szagerman@gmail.com>
To: "Ruby on Rails: Talk" <rubyonrails-talk@googlegroups.com>
Sent: Thursday, July 12, 2007 6:15 PM
Subject: [Rails] Re: how to debug failure on start from InstantRails
This topic is locked and can not be replied to.