Setup Ruby Applications keeps loading and produces Error 500

Issue

One of our clients on server hertz.superhosting.bg has setup two Redmine applications via Setup Ruby Application menu of their cpanel account:
version 5.1.1 running on Ruby 2.7 in /home/gcrbgcaa/redmine
version 6.1.0 running on Ruby 3.2 in /home/gcrbgcaa/redminetest

The Setup Ruby Applications menu in their account cannot be opened and only keeps loading until cPanel produces error 500 page and the following messages are logged in /usr/local/cpanel/logs/error_log:

[2025-10-21 16:41:22 +0300] warn [cpaneld] The subprocess (cpanel (cpanel)) exited with an error (ID 582125397007079): The subprocess ended prematurely because it received the “ALRM” (14) signal.
[2025-10-21 16:41:22 +0300] info [cpaneld] Internal Server Error: "GET /cpsess2981566112/frontend/jupiter/lveversion/ruby-selector.html.tt HTTP/1.1" 500 Internal Error (ID 582125397007079)

The only way I have found to get the menu to actually load is by disabling the Redmine v5.1.1 application's virtualenvironment by renaming /home/gcrbgcaa/rubyvenv/redmine/2.7 directory and reloading cagefs for the client with "cagefsctl -m gcrbgcaa" however when the menu loads it cannot find either of the Ruby applications for the cPanel account. 

Can you please take a look and let us know what might be causing the problem with the menu? Please note that /home/gcrbgcaa/redmine is production and the client wants it to continue operating with Ruby 2.7. 

Additionally when trying to run Redmine v6.1.1( /home/gcrbgcaa/redminetest ) apache indicates that one of the gems nokogiri is incompatible with the server's glibc version:

[ E 2025-10-21 16:59:21.9736 845439/T6q age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /home/gcrbgcaa/redminetest: The application encountered the following error: There was an er
ror while trying to load the gem 'roadie-rails'.
Gem Load Error is: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.18.10-x86_64-linux-gnu/lib/nokogiri/3.2/nokogiri.so) - /home/
gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.18.10-x86_64-linux-gnu/lib/nokogiri/3.2/nokogiri.so
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.18.10-x86_64-linux-gnu/lib/nokogiri/extension.rb:7:in `require_relative'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.18.10-x86_64-linux-gnu/lib/nokogiri/extension.rb:7:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.18.10-x86_64-linux-gnu/lib/nokogiri.rb:8:in `require_relative'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.18.10-x86_64-linux-gnu/lib/nokogiri.rb:8:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.7.3/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/roadie-5.2.1/lib/roadie/inliner.rb:4:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.7.3/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/roadie-5.2.1/lib/roadie.rb:31:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.7.3/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/roadie-rails-3.3.0/lib/roadie/rails.rb:8:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.7.3/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/roadie-rails-3.3.0/lib/roadie-rails.rb:3:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.7.3/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.7.3/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/gcrbgcaa/rubyvenv/redminetest/3.2/gems/bundler-2.7.2/lib/bundler/runtime.rb:63:in `block (2 levels) in require'
/home/gcrbgcaa/rubyvenv/redminetest/3.2/gems/bundler-2.7.2/lib/bundler/runtime.rb:58:in `each'
/home/gcrbgcaa/rubyvenv/redminetest/3.2/gems/bundler-2.7.2/lib/bundler/runtime.rb:58:in `block in require'
/home/gcrbgcaa/rubyvenv/redminetest/3.2/gems/bundler-2.7.2/lib/bundler/runtime.rb:52:in `each'
/home/gcrbgcaa/rubyvenv/redminetest/3.2/gems/bundler-2.7.2/lib/bundler/runtime.rb:52:in `require'
/home/gcrbgcaa/rubyvenv/redminetest/3.2/gems/bundler-2.7.2/lib/bundler.rb:214:in `require'
/home/gcrbgcaa/redminetest/config/application.rb:18:in `<top (required)>'
/home/gcrbgcaa/redminetest/config/environment.rb:4:in `<top (required)>'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/rack-3.1.18/lib/rack/builder.rb:124:in `instance_eval'
/home/gcrbgcaa/redminetest/vendor/bundle/ruby/3.2.0/gems/rack-3.1.18/lib/rack/builder.rb:124:in `initialize'

Do you know if there is a way to recompile the nokogiri gem within the client's environment?

Environment

• Ruby Selector

Solution

The resolution involved reinstalling the alt-ruby packages and then setting the current Ruby version for the user using CLI:

# selectorctl --interpreter=ruby --user=gcrbgcaa --set-user-current --version=3.3 cltest 
#

Cause

Useful links