Ask Your Question
0

Nothing works after reboot of controller node - internal server error 500

asked 2016-05-02 17:25:52 -0500

D3LTA9 gravatar image

So this error seems to be constantly occurring in different places in my openstack implementation.

But specifically, do I need to do something to restart services on reboot of my controller node? If I reboot it I cannot get any openstack command to run and get this error:

Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Internal Server Error (HTTP 500)

This person seems to have had a similar issue: https://ask.openstack.org/en/question/85577/discovering-versions-from-the-identity-service-failed-when-creating-the-password-plugin/ (https://ask.openstack.org/en/question...)

But again this seems to refer to a local_settings.py file that as far as I can tell is part of the horizon/dashboard configuration which I have not got to yet as I only have identity and image services running so far.

I have tried restarting apache2 and checked that keystone is running but didnt help.

Thanks for any advice

edit retag flag offensive close merge delete

Comments

Check the following:

# rabbitmqctl list_users

This command should show openstack as one of the user.

pjb gravatar imagepjb ( 2016-05-03 06:56:06 -0500 )edit

It returns this:

Listing users ... guest [administrator] openstack []

I get the same output after a reboot when nothing is working also.

D3LTA9 gravatar imageD3LTA9 ( 2016-05-03 19:43:29 -0500 )edit

RabbitMQ seems working. Check what all services on controller are up and running [1/3]:

systemctl status chronyd.service
systemctl status mariadb.service
systemctl status rabbitmq-server.service
systemctl status httpd.service 
systemctl status memcached.service
pjb gravatar imagepjb ( 2016-05-04 01:46:02 -0500 )edit

[2/3]

systemctl status openstack-glance-api.service 
systemctl status openstack-glance-registry.service
systemctl status openstack-nova-api.service 
systemctl status openstack-nova-cert.service
systemctl status openstack-nova-consoleauth.service
pjb gravatar imagepjb ( 2016-05-04 01:47:19 -0500 )edit

[3/3]

systemctl status openstack-nova-scheduler.service 
systemctl status openstack-nova-conductor.service 
systemctl status openstack-nova-novncproxy.service
systemctl status neutron-server.service
pjb gravatar imagepjb ( 2016-05-04 01:47:46 -0500 )edit
see more comments

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-05-04 23:38:16 -0500

D3LTA9 gravatar image

updated 2016-05-04 23:38:45 -0500

I think I have fixed the problem, still holding my breath as I already had a random internal server error earlier today but everything has been working since.

Due to me being an idiot when I disabled the temporary authentication token mechanism I deleted an extra character after admin_token_auth in the [pipeline:public_api] section of keystone-paste.ini file.

Gonna blame it on the terrible internet here in Hawaii and the lag over my VPN into my home network in New Zealand, the delay in the CLI input meant I deleted more than I meant to...haha.

I really hope this is the issue as everything has worked so far other than that one random internal server error.

Thanks for helping me though, it is appreciated!

edit flag offensive delete link more

Comments

Glad to hear that. :) J

pjb gravatar imagepjb ( 2016-05-05 00:26:55 -0500 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2016-05-02 17:25:52 -0500

Seen: 964 times

Last updated: May 04 '16

Related questions

Problem with Swift endpoints

controller node unexpectedly reboots [closed]

Error instance state after host reboot

Reboot Openstack Details

How to make devstack configuration persistent between reboots on Fedora 21?

ovs-vswitchd crashing continuously on reboot of network node

Juno controller random reboot or crash

Which is the right procedure to reboot the quantum network server?

Glance error in Icehouse stable release

VM's becomes unreachable after 4-5 hrs repeatedly.