-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combination of ruby-1.9.3-p286, passenger-enterprise 4.0.5 and rvm 1.25.17 creates endless pid spawn #2603
Comments
gist it if it is longer then few lines |
closing as there was no feedback in over 2 weeks, please let me know if you can provide details and I will reopen |
Hi there, I totally forgot about your request for feedback. I've created a Gist, which I think gives you what you're asking for. Did I miss anything? https://gist.github.com/everestx/7aa392b039c2ad446d8a |
show the |
Hi There:
and
|
this looks good, the other thing I see here is rvm get stable --auto-dotfiles --debug and show me all output (gist it) |
This is a pseudo-production host, so can't do it at the moment. I'll get back to you. |
I ran into the exact same problem. Here's my gist. At least for me it looks like it's a permission problem after upgrading |
hmm, maybe try |
that says it set a few permissions but didn't change anything to do with On 18 March 2014 17:10, Michal Papis [email protected] wrote:
|
Has this been fixed? I seem to have run into it with rvm 1.25.26 (stable) and a new install of ruby-2.0.0-p451 . Him a missing gemset for the newly installed ruby was causing it for me. |
It was fixed in the cases where I had a problem.
|
I assume this is fixed, if anyone else hits such problem please open a new ticket with details of the problem. |
Recently I upgraded to rvm version 1.25.17 from 1.24.8 and I got very erratic behavior. I'm guessing it's related to the use of gem-wrappers in the new version of rvm.
The combination of ruby-1.9.3-p286 and passenger-enterprise 4.0.5 worked just fine with rvm 1.28.4, but with rvm version 1.25.17, passenger appears to spawn child processes indefinitely.
See this snippet from the process listing, where passenger fails to startup a ruby app and eventually crashes apache. Note that this occurred for every child 'httpd' process that the parent 'httpd' process started up.
The text was updated successfully, but these errors were encountered: