Unable to register systems to Satellite : "Unable to register system, not all services available"

Solution Verified - Updated -

Environment

Red Hat Satellite 6.x
Red Hat Enterprise Linux 7.5

Issue

Unable to register systems to Satellite : "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
# katello-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
# satellite-installer --scenario satellite --upgrade
# satellite-maintain service restart
  • Now, hammer ping should return all services to be OK.

Root Cause

Satellite pulp services are not working because after 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

1-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

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.

2 Comments

I am still seeing this behaviour in 6.4.2 (can this be added to impacted Environments on this solution?). I have also seen this occur multiple times without a reboot/restart being involved. Is there an associated Bugzilla for this bug so I can follow updates and vote on getting it fixed? Having Pulp randomly stop, impacting all server registrations (especially in automated environments) is a fairly critical issue.

satellite-maintain service restart - - - this should resolve the issue.