debugging - Stack Level Too Deep in Production Rails App - How to Get Details? -


I am running 256MB slice on the slices with a production spree on MySQL, Mongrel, and Nginx. I get this error every time I try to access any URL in the app:

 SystemStackError (stack level too deep): compass (0.8.17) BB / compass / APIAnation / Rail / Action_ Controller RB: 7: `Process' vendor / plugins / hamel / rail /. / Lib / sass / plugin / rack.rb: 44: `in call '

(some more test url requests are in this)

Devaging strategy / tools I use in advanced mode What should be advanced (but free and open source), so can I improve my problem?

It is slightly different each time depending on the controller. I have tried, but it does not help because maybe there is probably no loop getting me.

The question is how do I get more detailed reports of exact output during production?

I am using and all server-side commands to execute Capistrano. I am running a Mongrale cluster of 3. I see that log files are:

 current / log $ ls development.log testite.com-error.log mongrel.8000.log mongrel.8001.log mongrel. 8002.log mongrel.log production.log testite.com-access.log 

I am looking for some advanced debugging strategies / devices in production mode so I can improve the problem solving. Probably doing some cap work locally (in fact, a staging app) for streaming / debugging (or conditionally break pointing!) (What people do?), Or something that is in the code P <

Thank you

I have all my gems and plugins and any other dependencies The application can be checked: I thought that you have forgotten something (or something wrong) Skrn) and it's going to fail so badly that he could not find any need that message is not being able to spit


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -