Broken Ruby 3.1 on Ruby Selector

[Mos]

Ruby 3.1 does not run properly on Cloudlinux EL8. Whenever I set up a ruby 3.1 website from Ruby selector, the simple hello world script does not even run and I see the following error in apache2 error_log:

App 2586878 output:  [passenger_native_support.so] not found for current Ruby interpreter.
App 2586878 output:      This library provides various optimized routines that make
App 2586878 output:      Phusion Passenger(R) faster. Please run 'sudo yum install passenger-devel-6.0.17'
App 2586878 output:      so that Phusion Passenger(R) can compile one on the next run.
App 2586878 output:  [passenger_native_support.so] not downloading because passenger wasn't installed from a release package
App 2586878 output:  [passenger_native_support.so] will not be used (can't compile or download)
App 2586878 output:   --> Passenger will still operate normally.
App 2586878 output: Error: The application encountered the following error: cannot load such file -- rack
App 2586878 output: Did you mean?  racc (LoadError)
App 2586878 output:     <internal:/opt/alt/ruby31/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
App 2586878 output:     <internal:/opt/alt/ruby31/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/phusion_passenger/loader_shared_helpers.rb:380:in `activate_gem'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/helper-scripts/rack-preloader.rb:93:in `preload_app'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/helper-scripts/rack-preloader.rb:189:in `block in <module:App>'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/phusion_passenger/loader_shared_helpers.rb:397:in `run_block_and_record_step_progress'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/helper-scripts/rack-preloader.rb:188:in `<module:App>'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
App 2586878 output:     /opt/cpanel/ea-ruby27/root/usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `<main>'
[ E 2023-05-09 16:47:50.8984 2338310/T2i age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /home/USERNAME/APPNAME: The application encountered the following error: cannot load such file -- rack
Did you mean?  racc (LoadError)
  Error ID: bdf46958
  Error details saved to: /var/run/ea-ruby27-passenger/passenger-error-o834ut.html

[ E 2023-05-09 16:47:50.9031 2338310/Ta age/Cor/Con/CheckoutSession.cpp:283 ]: [Client 2-3] Cannot checkout session because a spawning error occurred. The identifier of the error is bdf46958. Please see earlier logs for details about the error.​

This happens only on EL8, both on alt-ruby31 packages installed cloudlinux-updates-testing repo or the main cloudlinux repo:

alt-ruby31-3.1.3-3.x86_64
alt-ruby31-default-gems-3.1.3-3.noarch
alt-ruby31-devel-3.1.3-3.x86_64
alt-ruby31-libs-3.1.3-3.x86_64
alt-ruby31-rubygem-bigdecimal-3.1.1-3.x86_64
alt-ruby31-rubygem-bundler-2.3.26-3.noarch
alt-ruby31-rubygem-io-console-0.5.11-3.x86_64
alt-ruby31-rubygem-json-2.6.1-3.x86_64
alt-ruby31-rubygem-lsapi-5.2-4.el8.x86_64
alt-ruby31-rubygem-psych-4.0.4-3.x86_64
alt-ruby31-rubygem-rack-1.6.4-12.el8.x86_64
alt-ruby31-rubygem-rake-13.0.6-3.noarch
alt-ruby31-rubygem-rdoc-6.4.0-3.noarch
alt-ruby31-rubygems-3.3.26-3.noarch​

[Mos]

Update: According to ruby walkthrough on official passenger website, This error can be resolved by entering the ruby virtualenv, adding

gem "passenger", ">= 5.0.25", require: "phusion_passenger/rack_handler"

to a Gemfile, running bundle install and finally restarting the ruby application.

Hope this is fixed in alt-ruby31 CloudLinux packages.

[bogdan.sh]

I was able to reproduce it on our lab servers. Thanks for reporting and for the solution! Will update this thread as soon as we have more information.

[bogdan.sh]

And the fastest solution is to add a 'rack' module from the user interface.

[Mos]

And the fastest solution is to add a 'rack' module from the user interface.

This did not work for me actually, it shows the selected rack version to be installed with orange color in the list, and when I click on Update, it shows that modules have been installed, however nothing is actually installed and rack does not appear in the modules list even after refreshing it.

[bogdan.sh]

I guess you have to click the "Update" button after adding the rack module. By the way, the issue has been fixed by developers and going to be released pretty soon, the rack will be enabled by default.