Databases
StackOverflow2013
Postsdbo
POStack Level Too Deep in Production Rails App - How to Get Details?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStack Level Too Deep in Production Rails App - How to Get Details?
    primarykey
    data
    text
    <p>I am getting up and running with Spree in production on a 256MB Slicehost slice with MySQL, Mongrel, and Nginx. I am getting this error every time I try to access any URL in the app:</p> <pre> SystemStackError (stack level too deep): compass (0.8.17) lib/compass/app_integration/rails/action_controller.rb:7:in `process' vendor/plugins/haml/rails/./lib/sass/plugin/rack.rb:44:in `call' </pre> <p>(Some more test url requests are in this <a href="http://pastie.org/806646" rel="nofollow noreferrer">pastie</a>)</p> <p>What are the advanced (but free and open source) debugging strategies/tools I should use while in production mode so I can do better at solving this problem?</p> <p>It's slightly different each time depending on the controller. I have tried <a href="https://stackoverflow.com/questions/242617/how-to-increase-stack-size-for-a-ruby-app-recursive-app-getting-stack-level-too">increasing my stack size</a>, but that doesn't help because there's probably just some loop I can't find.</p> <p>The question is, how do I get a more detailed report of the exact output while in production?</p> <p>I am using <a href="http://deprec.failmode.com/" rel="nofollow noreferrer">Deprec</a> and Capistrano to execute all server side commands. I am running a mongrel cluster of 3. The log files I see are:</p> <pre> current/log$ ls development.log testsite.com-error.log mongrel.8000.log mongrel.8001.log mongrel.8002.log mongrel.log production.log testsite.com-access.log </pre> <p>I'm just looking for some advanced debugging strategies/tools while in production mode so I can do better at solving this problem. Maybe some cap tasks for streaming/debugging (or conditionally break-pointing!) the production app (really, a staging app) locally (do people do that?), or something that spits out every single thing that executes in code?</p> <p>Thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USLance Pollard
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStack Level Too Deep in Production Rails App - How to Get Details?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POStack Level Too Deep in Production Rails App - How to Get Details?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHave you yet checked production.log? That's where I'd first expect errors in production to be... though I'm not necessarily sure it would give you any more data.
      singulars
      1. POStack Level Too Deep in Production Rails App - How to Get Details?
      1. USMatchu
    2. COyeah that first snippet is from production.log, and I have temporarily set "config.log_level = :debug" in production mode, but they don't give me too much info :/
      singulars
      1. POStack Level Too Deep in Production Rails App - How to Get Details?
      1. USLance Pollard
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload