Created attachment 817933 [details] Stacktrace from the http error_log Description of problem: Admin console does not work in INT Version-Release number of selected component (if applicable): 2.0.35 How reproducible: Always Steps to Reproduce: 1. Deploy admin console 2. Set up routes 3. Try access the admin console Actual results: Get a 503 with a stack trace inside our http error_log Expected results: We should see the pretty admin console Additional info: See attached for the stacktrace
Ruby appears to be choking at a very low level while initializing libv8 from therubyracer. This is used to compile JS assets, but I don't think it's even getting as far as trying to compile something, just loading the code. Given I have no idea what causes this and can't reproduce in a devenv, my suggestion would be to do what we're going to have to do eventually anyway, and precompile the assets. Hopefully that will allow us to remove the asset pipeline from even needing to load in production mode.
We've seen this before, usually relates to therubyracer picking up the wrong runtim env.
I thought this might be due to the admin-console having an unstated dependency that wouldn't get installed on a broker-only host. So, under OSE I installed a broker-only host. I removed v8, which I thought might be the thing missing Online (only needed by broker-utils via mongodb). I removed the rhc client. Still I did not see this problem. admin-console requires therubyracer, which requires v8, both from SCL. So I don't think it's a dependency issue, unless something is quite different in Online.
We haven't seen this issue in ages. No need to keep tracking, I don't think.