[Pulp-list] unable to use pulp-admin after upgrade to 2.4.1

[Jake Davis]

Just to follow up, this was caused by an update to /etc/hosts on this test
machine that clobbered the entry that pointed fqdn to 127.0.0.1. It just
happened to coincide exactly with the 2.4.1 upgrade time frame. Meh...


On Wed, Sep 24, 2014 at 5:03 PM, Randy Barlow <rbarlow at redhat.com> wrote:

> On 09/24/2014 02:57 PM, Jake Davis wrote:
> > Going from 2.4.0 to 2.4.1 on a centos6 host using instructions here
> >
> https://pulp-user-guide.readthedocs.org/en/latest/release-notes/2.4.x.html#pulp-2-4-1
> >
> > I'm getting connection refused any time I try to run pulp-admin login.
> >
> > Downgraded m2crypto to the standard os version.
> > All pulp related services restart without error.
> > server.conf and admin.conf are unchanged.
> > Rest API still works.
> > Tried removing ~/.pulp in case it was a user-cert issue.
> > The only information that gets logged is a lonely python traceback in ~/
> > .pulp/admin.log seen here... http://paste.fedoraproject.org/136193/
>
> The "Connection Refused" error sounds like either httpd isn't running,
> or perhaps Pulp didn't start correctly. Anything interesting in syslog?
> Did you run pulp-manage-db? Did pulp-manage-db complete successfully?
>
>
> _______________________________________________
> 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/20140926/01faeb0c/attachment.htm>