Oh, so it does. It looks like Gofer is trying to connect to a public host/port (RHN) but it really probably should be trying to connect to my Katello server. The error itself is an SSL error, but I feel confident it's more of a destination issue than an actual certificate error.
Should I specify the URL in goferd/agent.conf, and if yes, what port should I trying to be connecting to on the Katello server? On Monday, October 31, 2016 at 8:10:01 AM UTC-4, Chris Duryee wrote: > > > > On 10/28/2016 04:32 PM, Kendall Moore wrote: > > Sure, it's a boring list of one (pending) task: > > > > +----------------------------------------------------------------------+ > > > > Tasks > > > > +----------------------------------------------------------------------+ > > > > > > > > Operations: unit_uninstall > > > > Resources: 0aa08fe4-a2e9-46f0-8566-8ec890d2a913 (consumer) > > > > State: Waiting > > > > Start Time: Unstarted > > > > Finish Time: Incomplete > > Task Id: a7739b41-0730-4407-b821- > > > > 7073d7dd0cf0 > > Does the consumer system have any errors in /var/log/messages related to > gofer? > > > > > > > > On Friday, October 28, 2016 at 2:40:15 PM UTC-4, Chris Duryee wrote: > >> > >> > >> > >> On 10/28/2016 02:37 PM, Kendall Moore wrote: > >>> I can, and they are. > >>> > >>> I should add that several restarts of these services plus a > >> katello-service > >>> restart has not had any impact on fixing the problem. > >> > >> Can you paste a list of all running tasks, via "pulp-admin tasks list"? > >> > >>> > >>> On Friday, October 28, 2016 at 2:34:04 PM UTC-4, Chris Duryee wrote: > >>>> > >>>> > >>>> > >>>> On 10/28/2016 02:32 PM, Kendall Moore wrote: > >>>>> Hello All, > >>>>> > >>>>> I'm running Katello 3.2-RC3, and have just successfully installed > the > >>>>> Katello server and sync'd a few repositories. This all seems to > have > >>>>> worked correctly, but when I go to the Content Host page and try to > do > >>>>> anything with one of my registered hosts, the task hangs > indefinitely. > >> > >>>>> This was happening on RC2 as well yesterday, but was hoping an > upgrade > >>>>> today would have fixed the problem. > >>>>> > >>>>> Here's what I've checked so far: > >>>>> - I checked qpid, and it does seem to have both enqueued and > dequeued > >>>> the > >>>>> task, so I don't think it's hung in the qpid queue. > >>>>> - The tasks appear in the mongo database. > >>>>> - pulp-admin shows me that it knows the task exists, but it is > stuck > >> in > >>>> an > >>>>> unstarted/waiting stage. > >>>>> > >>>>> Thoughts on what I should look for or how I can proceed? > >>>>> > >>>>> Thanks! > >>>>> Kendall > >>>>> > >>>> > >>>> can you confirm that the following are running? > >>>> > >>>> * pulp_workers > >>>> * pulp_celerybeat > >>>> * pulp_resource_manager > >>>> > >>> > >> > > > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
