Project

General

Profile

Bug #16897

goferd reports Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')

Added by Matthew Riedel over 4 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Using Katello 3.1, and a CentOS 6.8 content host, the content host reports:

Oct 12 21:35:11 localhost goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://katello.server:5647
Oct 12 21:35:11 localhost goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://katello.server:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Oct 12 21:35:21 localhost goferd: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://katello.server:5647, failed: Connection amqps://katello.server:5647 disconnected: Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
Oct 12 21:35:21 localhost goferd: [INFO][worker-0] gofer.messaging.adapter.connect:35 - retry in 51 seconds

Foreman server reports

Host did not respond within 20 seconds
when trying to run commands on the content host.

qpid-dispatch-router-0.6.1-2.el7.x86_64 is installed on Foreman server.

Commenting out

idle-timeout-seconds
in
/etc/qpid-dispatch/qdrouterd.conf
is a workaround.

History

#1 Updated by Eric Helms over 4 years ago

  • Category set to 91
  • Status changed from New to Assigned
  • Assignee set to Justin Sherrill

We should raise this issue with the Qpid team to see if they have any idea what the issue may be.

#2 Updated by Eric Helms almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 166

Can you let us know if you are still seeing this after upgrading to the latest 3.3.0 version of Katello?

#3 Updated by Justin Sherrill almost 4 years ago

  • Status changed from Assigned to Rejected

Going ahead and closing this, feel free to reopen if you are still seeing it on 3.3. We did chat with the qpid team and they seemed to think this shouldn't be a problem, but weren't able to give many more details.

#4 Updated by Justin Sherrill almost 4 years ago

  • Status changed from Rejected to New
  • Assignee deleted (Justin Sherrill)

reopening as there was a second report of this.

#5 Updated by Justin Sherrill almost 4 years ago

  • Status changed from New to Needs design
  • Legacy Backlogs Release (now unused) deleted (166)

#6 Updated by John Mitsch almost 4 years ago

  • Assignee set to Justin Sherrill

#7 Updated by John Mitsch almost 4 years ago

Matthew,

Can you upload a foreman-debug from the katello server and an SOS report from the client so we can investigate this further?

#8 Updated by John Mitsch almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 250

#9 Updated by Andrew Kofink over 3 years ago

  • Status changed from Needs design to Closed
  • Legacy Backlogs Release (now unused) changed from 250 to 166

If you see this on Katello 3.4, please attach logs and reopen this issue.

#10 Updated by Justin Sherrill about 3 years ago

  • Assignee deleted (Justin Sherrill)

#11 Updated by Justin Sherrill about 3 years ago

  • Status changed from Closed to Rejected

Also available in: Atom PDF