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?
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.
What platform/OS are you using for production? What database. Inquiring minds want to know. 
Cheers–
Charles
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?
Try your apache error logs, as well as your system logs.
Cheers–
Charles
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.
Try the Phusion site and see if the online docs are helpful. I have always been able to diagnose problems with the rails log files coupled with the apache logs. Sorry. 
Cheers–
Charles