Passenger 4.0.53 + ruby 2.1.3, fails to download native support

683 views
Skip to first unread message

David Salgado

unread,
Oct 13, 2014, 12:12:57 PM10/13/14
to phusion-...@googlegroups.com
With ruby 2.1.3 (installed from the BrightBox PPA), and passenger 4.0.53 installed according to these instructions;


I'm seeing these errors in the nginx log;

App 7836 stdout:
App 7836 stderr:  --> Compiling passenger_native_support.so for the current Ruby interpreter...
App 7836 stderr:
App 7836 stderr:      (set PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable)
App 7836 stderr:
App 7836 stderr:      Warning: compilation didn't succeed. To learn why, read this file:
App 7836 stderr:      /tmp/passenger_native_support-1pnyet0.log
App 7836 stderr:  --> Downloading precompiled passenger_native_support.so for the current Ruby interpreter...
App 7836 stderr:      (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to disable)
App 7836 stderr:      Could not download https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/4.0.53/rubyext-ruby-2.1.3-x86_64-linux-gnu.tar.gz: no download tool found (curl or wget required)
App 7836 stderr:      Trying next mirror...
App 7836 stderr:      Could not download https://s3.amazonaws.com/phusion-passenger/binaries/passenger/by_release/4.0.53/rubyext-ruby-2.1.3-x86_64-linux-gnu.tar.gz: no download tool found (curl or wget required)
App 7836 stderr:  --> Continuing without passenger_native_support.so.
App 7836 stderr:
App 7836 stderr: sh: 1:
App 7836 stderr: env: not found

Curl is installed on the machine, but I think the problem is that the link it's trying to download from is incorrect. If I visit this URL in a browser;


...there is no "rubyext-ruby-2.1.3-x86-linux-gnu.tar.gz"  file, but there is a "rubyext-ruby-2.1.3-x86-linux.tar.gz"

Is the incorrect file URL compiled into passenger? None of the files at that S3 URL match /linux-gnu/

David

Scott Martin

unread,
Nov 24, 2014, 2:54:39 PM11/24/14
to phusion-...@googlegroups.com
This looks like a bug somewhere in the 'nginx-extras' package.  I switched to 'nginx-full' and everything started working correctly.

Scott

Hongli Lai

unread,
Nov 26, 2014, 9:14:57 AM11/26/14
to phusion-...@googlegroups.com
The wrong filename is caused by a bug in the OS name detection code. It has been fixed here: https://github.com/phusion/passenger/commit/495941239107750b6f3f8168c3ddf01f26faff53

Not being able to find curl and wget is another problem. It means that PATH isn't set correctly when your app is loaded.

David Salgado

unread,
Nov 26, 2014, 9:19:37 AM11/26/14
to phusion-...@googlegroups.com
Many thanks for these replies. I'll give it another try.

David

Akshay Vishnoi

unread,
Apr 28, 2016, 1:08:20 PM4/28/16
to Phusion Passenger Discussions
Hey I am also facing same issue. I installed passenger through apt-get. Can you please suggest what should I do to resolve this.

Daniel Knoppel

unread,
Apr 28, 2016, 2:02:10 PM4/28/16
to Phusion Passenger Discussions
Use the latest Passenger and the error message and logs contain hints on what to do.

Anyway native support is not needed for normal Passenger operation, as the message also says.

- Daniel
Reply all
Reply to author
Forward
0 new messages