Problem with log files not being written to
439 views
Skip to first unread message
BobCalco
Jul 10, 2009, 5:55:33 PM7/10/09
to Phusion Passenger Discussions
Someone helping maintain an app in production today tried to install
phpmysql admin for some reason and brought down apache, which was
running our rails app.
After apache was restarted properly with pass phrase for SSL cert and
all that, all appeared well. Except the only page that comes up on the
rails 2.3.2 app is the "We're sorry but something went wrong" page.
Passenger stopped writing to the production.log file when Apache got
borked, and despite all appearances of everything being up and
running, it still isn't. I am not getting anything useful in the
apache logs, even after upping the debug log level.
Basically I'm looking for clues. I double checked permissions on
production.log to ensure it's executable, and I've run passenger-
memory-stats which seem to show the VM for my app and its spawner
running OK.
The only symptoms I have now are: all of my rails pages give me "We're
sorry but something went wrong" and nothing is being written to any
log files.
even going into the production console gives no hint of a problem I
can access various models and the data in the DB OK.
Any advice?
TIA!
- Bob
phpmysql admin for some reason and brought down apache, which was
running our rails app.
After apache was restarted properly with pass phrase for SSL cert and
all that, all appeared well. Except the only page that comes up on the
rails 2.3.2 app is the "We're sorry but something went wrong" page.
Passenger stopped writing to the production.log file when Apache got
borked, and despite all appearances of everything being up and
running, it still isn't. I am not getting anything useful in the
apache logs, even after upping the debug log level.
Basically I'm looking for clues. I double checked permissions on
production.log to ensure it's executable, and I've run passenger-
memory-stats which seem to show the VM for my app and its spawner
running OK.
The only symptoms I have now are: all of my rails pages give me "We're
sorry but something went wrong" and nothing is being written to any
log files.
even going into the production console gives no hint of a problem I
can access various models and the data in the DB OK.
Any advice?
TIA!
- Bob
BJ Neilsen
Jul 10, 2009, 6:17:10 PM7/10/09
to phusion-...@googlegroups.com
Had this exact issue (no logging on 500 error), where you are
wondering "what in the world just happened to my app" when I did a
passenger update two weeks ago (I've just resolved it). The best
advice I was given (which solved things for me quickly) was to make
SURE your connection to the db is working properly from rails.
Installing phpmyadmin may have messed with user premissions or
whatnot, so that's what I'd start debugging. When my issue came up I
assumed it was Passenger, but it was actually a bad socket path for my
production setup in database.yml, which I happened to update at the
same time I upgraded Passenger. Hope any of this helps.
BJ Neilsen
wondering "what in the world just happened to my app" when I did a
passenger update two weeks ago (I've just resolved it). The best
advice I was given (which solved things for me quickly) was to make
SURE your connection to the db is working properly from rails.
Installing phpmyadmin may have messed with user premissions or
whatnot, so that's what I'd start debugging. When my issue came up I
assumed it was Passenger, but it was actually a bad socket path for my
production setup in database.yml, which I happened to update at the
same time I upgraded Passenger. Hope any of this helps.
BJ Neilsen
Robert Calco
Jul 10, 2009, 6:27:57 PM7/10/09
to phusion-...@googlegroups.com
It's working .... I was able to go into script/console and access data via various app models, and the sock file pointed-to in the database.yml is where it's supposed to be. So I believe the DB connection to be working fine.
I'm totally blind on this without any clues from any logs...
- Bob
BJ Neilsen
Jul 10, 2009, 6:30:33 PM7/10/09
to phusion-...@googlegroups.com
I'm afraid I won't be of much help on this then, sorry. That's a good idea to access the model data from the console, I'll remember that next time. Good luck.
BJ
Kai Krakow
Jul 12, 2009, 7:28:15 AM7/12/09
to Phusion Passenger Discussions
I had this because passenger guys changed the symlink resolver in
passenger. Make sure it only needs to resolve one symlink deep or
things screw up. It won't correctly find the application's pathes
otherwise.
On 11 Jul., 00:27, Robert Calco <bobca...@gmail.com> wrote:
> It's working .... I was able to go into script/console and access data via
> various app models, and the sock file pointed-to in the database.yml is
> where it's supposed to be. So I believe the DB connection to be working
> fine.
>
> I'm totally blind on this without any clues from any logs...
>
> - Bob
>
passenger. Make sure it only needs to resolve one symlink deep or
things screw up. It won't correctly find the application's pathes
otherwise.
On 11 Jul., 00:27, Robert Calco <bobca...@gmail.com> wrote:
> It's working .... I was able to go into script/console and access data via
> various app models, and the sock file pointed-to in the database.yml is
> where it's supposed to be. So I believe the DB connection to be working
> fine.
>
> I'm totally blind on this without any clues from any logs...
>
> - Bob
>
Reply all
Reply to author
Forward
0 new messages