Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
A candlepin service seems to die on its own after some time. This is a second occurrence for sat 6.2.0 Beta (GA10.1).
I don't have a clear replication steps, so I'll attach the foreman-debug tarball.
This happend on CI machine long time (days) after the automation finished
Version-Release number of selected component (if applicable):
6.2.0 Beta (GA10.1)
Actual results:
"Oops, we're sorry but something went wrong A backend service [ Candlepin ] is unreachable"
# hammer -u admin -p changeme ping
candlepin:
Status: FAIL
Server Response:
candlepin_auth:
Status: FAIL
Server Response:
pulp:
Status: ok
Server Response: Duration: 380ms
foreman_tasks:
Status: ok
Server Response: Duration: 12ms
production.log:
2016-05-10 11:53:08 [app] [W] Connection refused - connect(2) for "localhost" port 8443
I don't see any specific errors in Candlepin however it looks like the katello_event_queue is not being drained of the messages that candlepin is sending.
From the qpid_stat_queues file in the foreman debug info. 2.4k messages in the katello_event_queue and no connections draining them.
Brad, how should that be routed?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501
Description of problem: A candlepin service seems to die on its own after some time. This is a second occurrence for sat 6.2.0 Beta (GA10.1). I don't have a clear replication steps, so I'll attach the foreman-debug tarball. This happend on CI machine long time (days) after the automation finished Version-Release number of selected component (if applicable): 6.2.0 Beta (GA10.1) Actual results: "Oops, we're sorry but something went wrong A backend service [ Candlepin ] is unreachable" # hammer -u admin -p changeme ping candlepin: Status: FAIL Server Response: candlepin_auth: Status: FAIL Server Response: pulp: Status: ok Server Response: Duration: 380ms foreman_tasks: Status: ok Server Response: Duration: 12ms production.log: 2016-05-10 11:53:08 [app] [W] Connection refused - connect(2) for "localhost" port 8443