I'm a relative new foreman user (from an administrative standpoint, at
least), and I've inherited a bit of an issue.
I've got an instance of foreman running on a rhel 6 ec2 instance, and,
after some upgrades were done to the instance (specifically, mysql was
upgraded from 5.6.37 to 5.6.38), my instance has stopped starting.
One of my co-workers spent a few days on this before handling it over to
me, and I've spent a few days beating on this as well, to no avail.
When I attempt to start it up, I get the following error:
strict_error': Gem loading error: cannot load such file -- foreman_memcache (RuntimeError) from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:56:inrescue in block in system_require'
block in system_require' from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:ineach'
system_require' from /usr/share/foreman/config/application.rb:16:in<top
require' from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:inrequire'
block in server' from /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-18.104.22.168/lib/rails/commands/commands_tasks.rb:75:intap'
server' from /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-22.214.171.124/lib/rails/commands/commands_tasks.rb:39:inrun_command!'
<top (required)>' from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:128:inrequire'
rescue in require' from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:39:inrequire'
from /usr/share/foreman/bin/rails:4:in `<main>'
I've verified that foreman_memcache is installed and accessible, though I
fear that it may be showing as accessible to me, but not the foreman
The specific instance details are as follows:
RELEASE: Red Hat Enterprise Linux Server release 6.9 (Santiago)
RUBY: ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
I'm painfully aware the the ruby, foreman, and puppet versions are horribly
out of date, but, due to circumstances beyond my control, I'm unable to
change them currently.
Anyone have any ideas what could be done to potentially fix this beast?
Wouldn't be as much of an issue if it weren't blocking deployment of a
newer version/instance of it as well…
Thanks in advance!