Unable to Register Systems to Red Hat Satellite 6: "Unable to register system, not all services available"

Solution Verified - Updated

Environment

  • Red Hat Satellite 6
  • Red Hat Enterprise Linux 7

Issue

  • Unable to register systems to Red Hat Satellite6 : "Unable to register system, not all services available"

     # subscription-manager register --org="ORG NAME " --activationkey="ActivationKey NAME"
     Unable to register system, not all services available
    

Resolution

  • Solution 1: Restart Satellite services

     # satellite-maintain service restart
     # hammer ping
      candlepin:
       Status:          ok
       Server Response: Duration: 31ms
      candlepin_auth:
       Status:          ok
       Server Response: Duration: 27ms
      pulp:
       Status:          ok
       Server Response: Duration: 34ms
      pulp_auth:
       Status:          ok
       Server Response: Duration: 18ms
      foreman_tasks:
       Status:          ok
       Server Response: Duration: 880ms
    
  • Solution 2: Re-run the installer script and then restart the services.

        # satellite-maintain service stop
    
        For Satellite < 6.9 run the installer
        # satellite-installer 
    
        For Capsule >= 6.9  run the installer
        # satellite-installer
    
        # satellite-maintain service restart
    
  • Now, hammer ping should return all services to be OK.

Root Cause

  • Satellite pulp services are not working because after the server reboot mongodb did not initialize correctly

        # hammer ping
    
        candlepin:      
          Status:          ok
          Server Response: Duration: 23ms
        candlepin_auth: 
          Status:          ok
          Server Response: Duration: 23ms
        pulp:           
          Status:          FAIL
          Server Response:
        pulp_auth:      
          Status: FAIL
        foreman_tasks:  
          Status:          ok
          Server Response: Duration: 12ms
    

Diagnostic Steps

  • Check Satellite running services :

        # hammer ping 
    
        candlepin:      
          Status:          ok
          Server Response: Duration: 23ms
        candlepin_auth: 
          Status:          ok
          Server Response: Duration: 23ms
        pulp:           
          Status:          FAIL
          Server Response:
        pulp_auth:      
          Status: FAIL
        foreman_tasks:  
          Status:          ok
          Server Response: Duration: 12ms
    
  • Errors on /var/log/messages

    
        pulp: pulp.server.db.connection:CRITICAL: Database initialization failed: localhost:27017: [Errno 111] Connection refused
        pulp: pulp.server.webservices.application:ERROR: (1601-37376) The Pulp server encountered an unexpected failure during initialization
        pulp_streamer: pulp.server.db.connection:CRITICAL: Database initialization failed: localhost:27017: [Errno 111] Connection refused
        pulp: pulp.server.db.connection:CRITICAL: Database initialization failed: localhost:27017: [Errno 111] Connection refused
       pulp_streamer: Unhandled Error
    
  • Check the /etc/rhsm/rhsm.conf file.

      # Server hostname:
      hostname = satellite-FQDN                 
     
      # Server prefix:
      prefix = /rhsm
    
      # Server port:
      port = 443
    
      [rhsm]
      # Content base URL:
      baseurl = https://satellite-FQDN/pulp/content/
    
      # Default CA cert to use when generating yum repo configs:
      repo_ca_cert = %(ca_cert_dir)skatello-server-ca.pem             
    

Note: This file looks like as above and it gets modified in the background when you register it with the activation key or with generated curl command.

SBR
Product(s)
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.