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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
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 On Jul 11, 6:44 pm, "Bill Walton" <bill.wal...-xwVYE8SWAR3R7s880joybQ@public.gmane.org> wrote:> Hi, > > lunaclairewrote: > > 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--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Happy that helped. Best regards, Bill ----- Original Message ----- From: "lunaclaire" <szagerman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> To: "Ruby on Rails: Talk" <rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Sent: Thursday, July 12, 2007 6:15 PM Subject: [Rails] Re: how to debug failure on start from InstantRails> > 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 > > On Jul 11, 6:44 pm, "Bill Walton" <bill.wal...-xwVYE8SWAR3R7s880joybQ@public.gmane.org> wrote: >> Hi, >> >> lunaclairewrote: >> > 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 > > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---