6:18 a.m.
yes infortunately i did it with pip. Ok i'll start from scratch. are their
any methods to clean my CentOs from Openstack?
2015-05-06 12:25 GMT+02:00 Javier Pena <javier.pena(a)redhat.com>:
----- Original Message -----
> Actually I don't know much. Until yesterday keystone was just fine. and
as I
> had some issues with heat I tried to install os-collect-config.( I don't
> know if this info is relevant). but it didn't work as I had some errors
> pumping out ( Command /usr/bin/python -c "import setuptools,
>
tokenize;__file__='/tmp/pip-build-7ApEOu/lxml/setup.py';exec(compile(getattr(tokenize,
> 'open', open)(__file__).read().replace('\r\n', '\n'),
__file__, 'exec'))"
> install --record /tmp/pip-1psZ04-record/install-record.txt
> --single-version-externally-managed --compile failed with error code 1 in
> /tmp/pip-build-7ApEOu/lxml )
> after that i couldn't connect to the dashboard nor any other service. I
had
> the errors
> Traceback (most recent call last):
> File "/usr/bin/heat", line 7, in <module>
> from heatclient.shell import main
> File "/usr/lib/python2.7/site-packages/heatclient/shell.py", line 30, in
> <module>
> from keystoneclient import discover
> File "/usr/lib/python2.7/site-packages/keystoneclient/discover.py", line
20,
> in <module>
> from keystoneclient import session as client_session
> File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line
22,
> in <module>
> from oslo_serialization import jsonutils
> ImportError: No module named oslo_serialization
> so I reinstalled oslo.serialization and oslo.concurrency. Here I was
able to
> get my dashboard UI in in the browser (which i couldn't do earlier) but i
> can't log in.
Did you try to install os-collect-config using pip? If you did that, pip
might have tried to update several Python libraries used by OpenStack
components, and that usually creates a mess in your system.
It is possible to recover from it by manually uninstalling and
reinstalling the modules updated by pip, but it can be complicated. If it
is a test system I would suggest reinstalling.
Regards,
Javier
> 2015-05-06 11:27 GMT+02:00 Javier Pena < javier.pena(a)redhat.com > :
> > ----- Original Message -----
>
> > > I'm afaraid it is not, here is the output of lsof -i -n -P|grep httpd
>
> > > httpd 1855 root 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 1855 root 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 1855 root 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > Actually, this is what I meant. Keystone is running as a WSGI process
> > inside
> > Apache, so this is why you see httpd listening on ports 5000 and 35357.
>
> > The next question would be why you are having trouble connecting to the
> > dashboard. Could you provide some more details on that issue?
>
> > Regards,
>
> > Javier
>
> > > httpd 3969 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3969 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3969 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3970 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3970 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3970 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3971 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3971 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3971 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3972 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3972 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3972 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3973 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3973 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3973 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3974 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3974 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3974 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3975 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3975 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3975 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > httpd 3976 apache 4u IPv6 35701 0t0 TCP *:35357 (LISTEN)
>
> > > httpd 3976 apache 6u IPv6 35705 0t0 TCP *:5000 (LISTEN)
>
> > > httpd 3976 apache 8u IPv6 35709 0t0 TCP *:80 (LISTEN)
>
> > > 2015-05-06 11:14 GMT+02:00 Javier Pena < javier.pena(a)redhat.com > :
>
> > > > ----- Original Message -----
>
> > >
>
> > > > > hi,
>
> > >
>
> > > > > I have some issues with keystone since this morning, I
couldn't
> > > > > connect
>
> > > > > to
>
> > >
>
> > > > > the dashboard so I checked my keystone service and found out
that it
> > > > > was
>
> > > > > not
>
> > >
>
> > > > > running. I tried to restart it but no luck.
>
> > >
>
> > > > > I did some changes in the keystone.conf to make this work but
no
> > > > > chance.
>
> > > > > The
>
> > >
>
> > > > > changes I did are:
>
> > >
>
> > > > > cp /usr/share/keystone/keystone-dist-paste.ini /etc/keystone/
>
> > >
>
> > > > > chown keystone:keystone /etc/keystone/*
>
> > >
>
> > > > > updated keystone.conf with the new config_file value
>
> > >
>
> > > > > /etc/keystone/keystone.conf sql connection
mysql://keystone:PASSWD@
>
> > >
>
> > > > > controller/keystone
>
> > >
>
> > > > > and I got this logs errors :
>
> > >
>
> > > > > 2015-05-06 10:17:28.352 24135 ERROR
>
> > >
>
> > > > > keystone.common.environment.eventlet_server [-] Could not bind
to
>
> > >
>
> > > > > 0.0.0.0:35357
>
> > >
>
> > > > > 2015-05-06 10:17:28.353 24135 ERROR root [-] Failed to start
the
> > > > > admin
>
> > > > > server
>
> > >
>
> > > > > 2015-05-06 10:17:29.221 24145 ERROR
>
> > >
>
> > > > > keystone.common.environment.eventlet_server [-] Could not bind
to
>
> > >
>
> > > > > 0.0.0.0:35357
>
> > >
>
> > > > > 2015-05-06 10:17:29.221 24145 ERROR root [-] Failed to start
the
> > > > > admin
>
> > > > > server
>
> > >
>
> > > > > 2015-05-06 10:17:30.059 24151 ERROR
>
> > >
>
> > > > > keystone.common.environment.eventlet_server [-] Could not bind
to
>
> > >
>
> > > > > 0.0.0.0:35357
>
> > >
>
> > > > > 2015-05-06 10:17:30.060 24151 ERROR root [-] Failed to start
the
> > > > > admin
>
> > > > > server
>
> > >
>
> > > > > 2015-05-06 10:17:30.895 24158 ERROR
>
> > >
>
> > > > > keystone.common.environment.eventlet_server [-] Could not bind
to
>
> > >
>
> > > > > 0.0.0.0:35357
>
> > >
>
> > > > > 2015-05-06 10:17:30.896 24158 ERROR root [-] Failed to start
the
> > > > > admin
>
> > > > > server
>
> > >
>
> > > > > 2015-05-06 10:17:31.727 24167 ERROR
>
> > >
>
> > > > > keystone.common.environment.eventlet_server [-] Could not bind
to
>
> > >
>
> > > > > 0.0.0.0:35357
>
> > >
>
> > > > > 2015-05-06 10:17:31.728 24167 ERROR root [-] Failed to start
the
> > > > > admin
>
> > > > > server
>
> > >
>
> > > > Hi,
>
> > >
>
> > > > It is possible that keystone is running as a wsgi process under
apache.
>
> > > > That
>
> > > > would explain why it cannot bind to port 35357.
>
> > >
>
> > > > Can you check if your httpd process is running? If so, please
check if
> > > > it
>
> > > > is
>
> > > > bound to port 35357 (lsof -i -n -P|grep httpd).
>
> > >
>
> > > > Regards,
>
> > >
>
> > > > Javier
>
> > >
>
> > > > > _______________________________________________
>
> > >
>
> > > > > Rdo-list mailing list
>
> > >
>
> > > > > Rdo-list(a)redhat.com
>
> > >
>
> > > > > https://www.redhat.com/mailman/listinfo/rdo-list
>
> > >
>
> > > > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
> > >
>
> > > _______________________________________________
>
> > > Rdo-list mailing list
>
> > > Rdo-list(a)redhat.com
>
> > > https://www.redhat.com/mailman/listinfo/rdo-list
>
> > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com