Use tail command to see the last line changes of your production.log file. "tail -f log/production.log"
Reproduce the error again. Now you can see the actual error in the log file. On Tue, May 5, 2009 at 11:30 AM, Mike C <[email protected]> wrote: > > I'm getting 500 errors on my production server running Passenger. I > cannot, for the life of me, find out what the problem is. Everything > works fine on my local machine. However, on my production machine, I > can't even get logs since I don't know where Passenger keeps the logs. > So I'm scrolling through the production.log on the production server, > which seems to be endless. Is there an easier way to find out what > went wrong? > > > -- With regards, Arunkumar B. 9789980534. http://thinkingrails.blogspot.com --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
