Is OpenStack internal server error creating problems for you?

OpenStack works as a decent choice to manage your cloud. But it can have some errors too.

At Bobcares, we often get the request to solve such cloud hosting errors. We provide fixes for our customers as a part of our Server Management Services.

Today, let’s analyze the cause and see how our Support Team fix OpenStack internal server error.

What is OpenStack?

In simple terms, it is a user-friendly cloud OS. Therefore, we can manage and control a large pool of resources using this. Simply, through APIs and interface, we can manage Storage and Network resources.

Also, there is a dashboard with different access levels. It also helps to manage containers and bare metal storage from the same dashboard. Similarly, it provides easy use of applications. Moreover, there are various useful built-in tools making works easy. As a result, we can deploy 3rd party services as well.

Cause and Fix for OpenStack Internal Server Error?

Its time now to see the major reasons that can result in OpenStack errors.

1. Incorrect  configuration

Recently, one of our customers faced the same problem. He was trying OpenStack in Ubuntu.

When he started using it, he was unable to access it from the web browser. As a result, it was showing OpenStack internal server error like the below image.

Let’s see how our support team fixed the issue.

We found that the problem was due to missing hosts. When we are running OpenStack in live server and not for testing, we need to add the server IP or the domain name in the “ALLOWED_HOSTS” property. It filters and allows only the mentioned domains to serve contents.

We edited the property from the file located at "/opt/stack/horizon/openstack_dashboard/local/local_settings.py" and added the server IP.

After that, we restarted the Apache service. Restarting is necessary so that the changes take effect.

It opened fine from the browser without any issue.

2. Token Mismatch causes OpenStack Internal Server Error

There are other reasons due to which this error can happen. We will discuss a few more reasons that could lead to such error.

The error may occur due to a token mismatch in config. In such cases, we check "keystone.conf".
We confirm the value exported for “OS_TOKEN” matches the “admin_token” value in “FILE”. If the values are different then we change the value. If the values matches then we check for values exported for OS_URL. We also check for OS_IDENTITY_API_VERSION. These are the common issues that lead to such errors.

If we still receive the error, we delete the keystone database. Then we recreate it again and grant all permissions. We do this with the below command :

su -s /bin/sh -c "keystone-manage db_sync" keystone

And finally the below command :

keystone-manage fernet_setup --keystone-user keystone --keystone-group keystone

Again, we restart the httpd service.

[Having trouble in fixing OpenStack errors? – We’ll fix it for you.]

Conclusion

In short, OpenStack internal server error may occur due to multiple reasons like incorrect settings, token mismatch, etc. Today, we saw how our Support Engineers fixed errors related to the OpenStack.