Project

General

Profile

Bug #11971

Generate Capsule Metadata and Sync fails - Host did not respond within 20 seconds. Is katello-agent installed and goferd running on the Host

Added by Sameer Syed over 3 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
High
Category:
Foreman Proxy Content
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

I've a Katello V2.3 setup with 1 Katello server and about 15 Capsules/Smart Proxies. Every-time I publish and promote a content view the 'Generate Capsule Metadata and Sync' fails with the error messages:

"Host did not respond within 20 seconds. Is katello-agent installed and goferd running on the Host?"

from every Smart proxy. When I restart the goferd on the smart proxy and initiates a manual sync using hammer the sync completes (hammer capsule content synchronize --id xx), but when I try to sync again next day it fails with same error message - "Host did not respond within 20 seconds. Is katello-agent installed and goferd running on the Host?" even though the goferd daemon is running. I again have to restart the goferd for it work.

Please advise any suggestions or corrective measures.

capsule.log capsule.log 1000 KB Logs from Capsule Sameer Syed, 03/23/2016 06:39 PM
capsule.log capsule.log 1000 KB Capsule logs Sameer Syed, 03/23/2016 07:07 PM
katello-acls.png View katello-acls.png 26.2 KB Firewall Ports Sameer Syed, 04/05/2016 04:14 PM
Katello acls

Related issues

Related to Katello - Bug #12427: Unable to apply updates/erratasClosed2015-11-09

History

#1 Updated by Stephen Benjamin over 3 years ago

Do you have a firewall between the capsule and katello? We're aware of a case where the connection will time out, we're working on a solution with the qpid folks to setup heartbeats, but for now you'll have to restart the goferd on the capsule service periodically.

#2 Updated by Sameer Syed over 3 years ago

Stephen Benjamin wrote:

Do you have a firewall between the capsule and katello? We're aware of a case where the connection will time out, we're working on a solution with the qpid folks to setup heartbeats, but for now you'll have to restart the goferd on the capsule service periodically.

Thanks Stephen for the response. Yes I've firewall between Capsule and Katello, but we have opened up the ports. Do you know an approx fix release of the heartbeat?

#3 Updated by Christophe Roux over 3 years ago

I'm having the exact same issue. Need to restart goferd to make sync work again.
FW between Katello and Capsule. Correct ports opened.

#4 Updated by Sameer Syed over 3 years ago

Stephen Benjamin wrote:

Do you have a firewall between the capsule and katello? We're aware of a case where the connection will time out, we're working on a solution with the qpid folks to setup heartbeats, but for now you'll have to restart the goferd on the capsule service periodically.

Hello Stephen,

I am seeing this issue with the Katello clients as well, with this issue it will become a challenge to manage client depending on goferd, or for that matter running any updates on clients from foreman console. Do you have any update on the heartbeat or roadmap for this fix?

#5 Updated by Christophe Roux over 3 years ago

Hi,

I am also waiting desperately for a fix for this issue. I was also having the same issue with a Red Hat Satellite deployment and the Red Satellite 6.1.3 update did fix the issue.

#6 Updated by Eric Helms over 3 years ago

  • Tracker changed from Support to Bug
  • Legacy Backlogs Release (now unused) set to 70

#7 Updated by Justin Sherrill about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 70 to 113

#8 Updated by Eric Helms about 3 years ago

  • Related to Bug #12427: Unable to apply updates/erratas added

#9 Updated by Justin Sherrill about 3 years ago

  • Assignee set to Justin Sherrill
  • Status changed from New to Closed

As part of katello 2.4.1 we are updating a new qpid stack with a bunch of bug fixes around stability. I think this will fix a ton of the qpid related issues we are seeing including this one. Could you try out this release when it is out and give it a try?

The updated packages include:

libqpid-dispatch x86_64 0.4-11.el7
python-qpid noarch 0.30-9.el7
qpid-cpp-client x86_64 0.30-8.el7
qpid-cpp-client-devel x86_64 0.30-8.el7
qpid-cpp-server x86_64 0.30-8.el7
qpid-cpp-server-linearstore x86_64 0.30-8.el7
qpid-dispatch-router x86_64 0.4-11.el7
qpid-proton-c x86_64 0.9-13.el7

I will go ahead and close. Please re-open if you continue to have the issue after 2.4.1 is released and you have tried these updated packages.

Thanks!

#10 Updated by Sameer Syed about 3 years ago

Thanks Justin, can I know when is the 2.4.1 scheduled to be released? I am looking at the release planning and the release end date show as 2016-01-15:

http://projects.theforeman.org/rb/release/113

#11 Updated by Justin Sherrill about 3 years ago

It is now released! Thanks for pointing out that release schedule page, I just updated it.

#12 Updated by Sameer Syed about 3 years ago

I've upgraded to katello 2.4.1 version on the Katello Server and the Capsules, but I still see the error 'Host did not respond within 20 seconds. Sync has been cancelled. Is katello-agent installed and goferd running on the Host?' when publishing new content or when I sync using hammer. Do I have to change/add any configurations?

#13 Updated by Sameer Syed about 3 years ago

Sameer Syed wrote:

I've upgraded to katello 2.4.1 version on the Katello Server and the Capsules, but I still see the error 'Host did not respond within 20 seconds. Sync has been cancelled. Is katello-agent installed and goferd running on the Host?' when publishing new content or when I sync using hammer. Do I have to change/add any configurations?

Here are the version after I upgraded:

rpm -qa | grep qpid
python-qpid-proton-0.9-13.el6.x86_64
python-gofer-qpid-2.6.2-1.el6.noarch
capsule.example.com-qpid-router-client-1.0-1.noarch
qpid-cpp-client-0.30-8.el6.x86_64
python-qpid-0.30-9.el6.noarch
python-qpid-qmf-0.30-5.el6.x86_64
qpid-dispatch-router-0.4-11.el6.x86_64
capsule.example.com-qpid-broker-1.0-1.noarch
libqpid-dispatch-0.4-11.el6.x86_64
qpid-qmf-0.30-5.el6.x86_64
qpid-tools-0.30-4.el6.noarch
capsule.example.com-qpid-router-server-1.0-1.noarch
qpid-cpp-server-0.30-8.el6.x86_64
qpid-cpp-server-linearstore-0.30-8.el6.x86_64
qpid-proton-c-0.9-13.el6.x86_64
capsule.example.com-qpid-client-cert-1.0-1.noarch

Attaching the logs as well.

#14 Updated by Sameer Syed about 3 years ago

Sameer Syed wrote:

Sameer Syed wrote:

I've upgraded to katello 2.4.1 version on the Katello Server and the Capsules, but I still see the error 'Host did not respond within 20 seconds. Sync has been cancelled. Is katello-agent installed and goferd running on the Host?' when publishing new content or when I sync using hammer. Do I have to change/add any configurations?

#15 Updated by Sameer Syed about 3 years ago

Hi Justin,

Here are the version after I upgraded:

rpm -qa | grep qpid
python-qpid-proton-0.9-13.el6.x86_64
python-gofer-qpid-2.6.2-1.el6.noarch
capsule.example.com-qpid-router-client-1.0-1.noarch
qpid-cpp-client-0.30-8.el6.x86_64
python-qpid-0.30-9.el6.noarch
python-qpid-qmf-0.30-5.el6.x86_64
qpid-dispatch-router-0.4-11.el6.x86_64
capsule.example.com-qpid-broker-1.0-1.noarch
libqpid-dispatch-0.4-11.el6.x86_64
qpid-qmf-0.30-5.el6.x86_64
qpid-tools-0.30-4.el6.noarch
capsule.example.com-qpid-router-server-1.0-1.noarch
qpid-cpp-server-0.30-8.el6.x86_64
qpid-cpp-server-linearstore-0.30-8.el6.x86_64
qpid-proton-c-0.9-13.el6.x86_64
capsule.example.com-qpid-client-cert-1.0-1.noarch

Attaching the logs as well.

#16 Updated by Sameer Syed almost 3 years ago

Hi Justin

Apart from sosreport that I had provided I also wanted to confirm teh ACLs/Firewall rules:

#17 Updated by Justin Sherrill almost 3 years ago

  • Status changed from Closed to Assigned
  • Legacy Backlogs Release (now unused) changed from 113 to 150

#18 Updated by Justin Sherrill almost 3 years ago

  • Legacy Backlogs Release (now unused) changed from 150 to 144

#19 Updated by Justin Sherrill almost 3 years ago

  • Status changed from Assigned to Resolved
  • Legacy Backlogs Release (now unused) changed from 144 to 86

This is now permanently resolved in Katello 3.0. Capsule syncing does not use gofer.

Also available in: Atom PDF