[Pulp-list] sasl negotiation failed when doing sync

Alex Harvey alexharv074 at gmail.com
Mon Jan 5 00:22:07 UTC 2015


Hi Brian

Thanks for your help.

It turns out the issue was this:
https://bugzilla.redhat.com/show_bug.cgi?id=1164324

Thus it worked after I added auth=no to qpidd.conf.

Kind regards
Alex

On 3 January 2015 at 03:30, Brian Bouterse <bbouters at redhat.com> wrote:

> Hi Alex,
>
> Usually the 'no mechanisms agreed' is due to Pulp not being able to
> communicate with the Qpid broker using SASL. This is typically caused by
> either a package being missing on the Qpid broker machine or the SASL
> database and/or Qpid's use of SASL is misconfigured. This Pulp docs discuss
> the Pulp portion of this config here [0]. Also ANONYMOUS support is being
> added (a SASL alternative) with the not-yet-released 2.6.0, and you can
> read about related improvements in the upcoming version through this bug
> [1].
>
> To solve your current problem I recommend using the SASL command line
> tools to verify the SASL database can be found and has the right username
> and password in it. Also use the trace option of Qpid to verify that as
> Qpid starts it is using the right SASL database.
>
> Generally the verify_ssl setting in admin.conf should not be related at
> all. I expect that with Pulp cannot communicate with Qpid it should fail on
> migration 0009 when you run `sudo -u apache pulp-manage-db` which is
> probably an easier way to cause Pulp to attempt to connect to Qpid and fail
> immediately if it cannot.
>
> [0]:
> https://pulp-user-guide.readthedocs.org/en/latest/broker-settings.html#qpid-with-username-and-password-authentication
> [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1124589
>
> -Brian
>
>
> ----- Original Message -----
> > From: "Alex Harvey" <alexharv074 at gmail.com>
> > To: pulp-list at redhat.com
> > Sent: Monday, December 29, 2014 10:37:04 PM
> > Subject: [Pulp-list] sasl negotiation failed when doing sync
> >
> > Hi all
> >
> > I'm new to Pulp and have run into an issue that I can't find an answer
> to.
> >
> > I'm running the latest version Pulp 2.5.1 on CentOS 6.5.
> >
> > I've followed the installation steps at
> > https://pulp-user-guide.readthedocs.org/en/2.5-release/installation.html
> >
> > After installing I also set verify_ssl to False in
> > /etc/pulp/admin/admin.conf.
> >
> > I then created a repo using:
> > # pulp-admin -u admin -p admin rpm repo create --repo-id
> centos-6.5-x86_64
> > --feed http://centos.mirror.crucial.com.au/6.5/os/x86_64/
> >
> > And when I try the first synchronise operation I get the following:
> > # pulp-admin -u admin -p admin rpm repo sync run --repo-id
> centos-6.5-x86_64
> > +----------------------------------------------------------------------+
> > Synchronizing Repository [centos-6.5-x86_64]
> > +----------------------------------------------------------------------+
> >
> > An internal error occurred on the Pulp server:
> >
> > RequestException: POST request
> > on /pulp/api/v2/repositories/centos-6.5-x86_64/actions/sync/ failed with
> 500
> > -
> > sasl negotiation failed: no mechanism agreed
> >
> > Then I note all through the logs messages like
> > Dec 30 14:27:47 ainslie pulp: celery.worker.consumer:ERROR: consumer:
> Cannot
> > connect to qpid:// guest at 127.0.0.1:5672// : sasl negotiation failed: no
> > mechanism agreed.
> > Dec 30 14:27:47 ainslie pulp: celery.worker.consumer:ERROR: Trying again
> in
> > 32.00 seconds...
> >
> > Best regards
> > Alex
> >
> >
> > _______________________________________________
> > Pulp-list mailing list
> > Pulp-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20150105/6b2cca1f/attachment.htm>


More information about the Pulp-list mailing list