-
Notifications
You must be signed in to change notification settings - Fork 547
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
passenger_native_support.so not being downloaded/built #1950
Comments
Couple more questions: how did you install the ruby you are using? And how are you specifying the ruby to passenger? In the http context or the server context? Lastly what happens if you run |
From the BrightBox PPA (
In the The Ruby itself is
|
As a follow up, now that this is built, looking over the logs I still see:
which may indicate that |
Just as a heads-up this is the last deb package we will be providing for Ubuntu 12.04, as it EOL'd in April. (see: https://lists.ubuntu.com/archives/ubuntu-announce/2017-March/000218.html and https://www.phusionpassenger.com/library/install/standalone/apt_repo/#limited-package-support-for-non-lts-ubuntu-versions) As for the PATH issue, can you please set the passenger_log_level to 7 and grab the logs from the startup of passenger and your app, I recreated your setup as closely as I could and didn't run into this issue so I suspect that your |
The writing was on that wall :) Just to confirm, by that you that mean that version
Attached is the full
|
Yes |
Putting the following just before
prints the following in the log:
which seems to indicate that |
Ok, so can you try setting |
With
|
what does |
@CamJN sorry about the delay there, I missed the notification.
|
Ok so Does the line in your bash config that looks something like this: |
If this is not relevant to this issue I can open a separate one I'm having the same problem on heroku, relevant logs:
We are using ruby 2.2.7, but if I check https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/5.1.4/ there is only a native binary for ruby 2.2.5. |
Hey @fschwahn looks like that is a bit of a different issue, as in your case there is an attempt to fetch the extension, so it would be worth creating a new issue for this. More information for what went wrong is likely in |
@fschwahn the info you pasted is not enough to be considered an issue at this point. Native support is not required, and it's normal that not all binaries are available (we supply a few for convenience). It usually fails to compile if you don't have the necessary development tools installed (as @msbit said check the log). |
Ok, the message threw me off, I thought this download is supposed to succeed - it seems having the download fail is the common case. Sorry for interrupting! |
@CamJN interesting idea!. My
so no explicit |
@msbit interesting, |
No shebang, full content of
I've been looking through the code, and it does look like a login shell is created via the |
Using |
@CamJN for me, if I replace
I can confirm that adding
in the logs. It's a little odd from my point of view though, as the server is effectively a completely new reinstall, and the
Out of curiosity more than anything, I removed the I've been trying to trace the execution flow, but I'm not sure where the Nginx code initially hands off to either |
Bash is supposed to pass environment variables to its children, and after a variable is exported once it's supposed to be treated like an environment variable even if it gets shadowed but bash isn't doing that for some reason. |
@msbit did you ever solve this? |
@jmeridth unfortunately not. It was for an older, unsupported version of Ubuntu and from memory it could be worked around so I didn’t look any further. My guess is the version of bash or general sh for that version of Ubuntu didn’t pass environment variables properly, but can’t be sure. |
@jmeridth feel free to include the details from your setup, especially a startup log with log level set to 7. |
Still happens to me with 5.2.0 and 5.3.4 on heroku.
|
Ran into this today. I can compile passenger_native_support.so from similar tarball source than the (failed) url that it tried. Where do I put it to make passenger stop complaining? |
A year and a half later...isn't this just an issue of putting the binaries on the proper cdn urls? |
@jemminger the actual issue is not being able to compile |
@Tectract the best way to compile the missing file is via:
This will build the file in the correct location, for me:
|
Closing as this is an issue with certain versions of bash not working correctly. |
I was seeing this same problem and it turned out to be a configuration issue. Similar to OP we have For some reason we were setting |
Answer to questions below, but it looks like it's an issue with the
PATH
being cleared out somehow before/during invocation of/usr/share/passenger/helper-scripts/rack-preloader.rb
.Question 1: What is the problem?
On start, passenger is unable to build or fetch the passenger_native_support.so. In the logs we have the following:
Contents of temp file:
Contents of
mkmf.log
:Manually running the
extconf.rb
:Presence of
curl
:Question 2: Passenger version and integration mode:
Open-source 5.1.4/nginx
Question 3: OS or Linux distro, platform (including version):
Ubuntu 12.04.5 LTS i386
Question 4: Passenger installation method:
[ ] RubyGems + Gemfile
[ ] RubyGems, no Gemfile
[x] Phusion APT repo
[ ] Phusion YUM repo
[ ] OS X Homebrew
[ ] source tarball
[ ] Other, please specify:
Question 5: Your app's programming language (including any version managers) and framework (including versions):
Ruby 2.1.9
Rails 3.2.22.5
Question 6: Are you using a PaaS and/or containerization? If so which one?
No
Question 7: Anything else about your setup that we should know?
No
The text was updated successfully, but these errors were encountered: