On Red Hat Satellite/Capsule foreman-proxy service is in failed state.

Solution Verified - Updated -

Issue

  • foreman-proxy service failed to start with below error.

    ●  foreman-proxy.service - Foreman Proxy
    Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/foreman-proxy.service.d
              └─90-limits.conf
    Active: failed (Result: exit-code) since Tue 2023-01-17 06:59:27 EST; 24s ago
    Process: 7329 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy --no-daemonize (code=exited, status=1/FAILURE)
    Main PID: 7329 (code=exited, status=1/FAILURE)
    Jan 17 06:59:26 satellilte.example.com systemd[1]: Starting Foreman Proxy...
    Jan 17 06:59:27 satellilte.example.com smart-proxy[7329]: /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file --    smart_proxy_main (LoadError)
    Jan 17 06:59:27 satellilte.example.com smart-proxy[7329]: from /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:83:in `require'
    Jan 17 06:59:27 satellilte.example.com smart-proxy[7329]: from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
    Jan 17 06:59:27 satellilte.example.com systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
    Jan 17 06:59:27 satellilte.example.com systemd[1]: Failed to start Foreman Proxy.
    Jan 17 06:59:27 satellilte.example.com systemd[1]: Unit foreman-proxy.service entered failed state.
    Jan 17 06:59:27 satellilte.example.com systemd[1]: foreman-proxy.service failed.
    

Environment

  • Red Hat Satellite 6.x.
  • Red Hat Capsule 6.x.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content