StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>ANSWER:</strong> After extensive work by EngineYard (they're awesome!) they were able to diagnose the issue. The root cause of this issue is a bug with mongrel clusters. Mongrel doesn't seem to see the first post request after being started. EngineYard did extensive work to diagnose this: </p> <blockquote> <p>There doesn't appear to be anything in your code causing the issue and I have found people outside of our environment that have experienced the bug as well (<a href="http://www.thought-scope.com/2009/07/mongrelcluster-rails-23x-bad-post.html" rel="noreferrer">http://www.thought-scope.com/2009/07/mongrelcluster-rails-23x-bad-post.html</a>). I suppose a lot of people don't see it because the first request to a site generally isn't a post or they chalk it up to flukes.</p> <p>[There is a potential workaround using CURL.] The curl work around would do a simple GET request to each of your mongrels on the server to prime them so to speak. You could do this with capistrano, but that won't work if you deploy via the dashboard. You can find a short section on deploy hooks we have built into the infrastructure here: <a href="https://cloud-support.engineyard.com/faqs/overview/getting-started-with-engine-yard-cloud" rel="noreferrer">https://cloud-support.engineyard.com/faqs/overview/getting-started-with-engine-yard-cloud</a></p> <p>Adding a simple run curl <a href="http://localhost:500x" rel="noreferrer">http://localhost:500x</a> > /dev/null should work (where x is the port you have 5000-50005 on your current setup).</p> </blockquote> <p>We have addressed the issue by switching our stack from Mongrel to Passenger, but apparently, a fix for Mongrel is in the works. Hopefully, this helps someone who sees this same strange issue.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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