You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if I need to open this ticket here or on FFI issues, so I'll open in both. I'm using Passenger for years, and this is the first time I got such an error. On the Nginx log, I can see:
ruby/2.5.0/gems/ffi-1.17.1/lib/ffi/ffi.rb:72:in `fork': super: no superclass method `fork' for PhusionPassenger::PreloaderSharedHelpers:Module (NoMethodError)
Downgrading FFI to 1.17.0 everything is fine. Is this a FFI or a Passenger issue?
Are you sure this is a bug in Passenger?
As said above, not really sure, but something there is wrong.
Question 1: What is the problem?
Seems the fork method is missing.
Question 2: Passenger version and integration mode:
6.0.24-1, open source
Question 3: OS or Linux distro, platform (including version):
Issue report
Not sure if I need to open this ticket here or on FFI issues, so I'll open in both. I'm using Passenger for years, and this is the first time I got such an error. On the Nginx log, I can see:
Downgrading FFI to 1.17.0 everything is fine. Is this a FFI or a Passenger issue?
Are you sure this is a bug in Passenger?
As said above, not really sure, but something there is wrong.
Question 1: What is the problem?
Seems the fork method is missing.
Question 2: Passenger version and integration mode:
6.0.24-1, open source
Question 3: OS or Linux distro, platform (including version):
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.5.1, Rails 5.2.0
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?
Not really.
The text was updated successfully, but these errors were encountered: