I did take a look in my apache logs and it only seemed to log warnings; I didn't see anything that pertained to the error or exception I got.
On May 5, 12:36 pm, Charles Johnson <[email protected]> wrote: > Try your apache error logs, as well as your system logs. > Cheers-- > > Charles > > On Tue, May 5, 2009 at 12:35 PM, Mike C <[email protected]> wrote: > > > Hi, the problem has been fixed but I was basically shooting in the > > dark and happened to get a hit. I'm using Debian 5.0 with MySQL 5 for > > my production. How does Passenger keep its logs, if any? > > > On May 5, 7:20 am, Charles Johnson <[email protected]> wrote: > > > What platform/OS are you using for production? What database. Inquiring > > > minds want to know. :) > > > Cheers-- > > > > Charles > > > > On Tue, May 5, 2009 at 1:00 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? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
