Difference between revisions of "OpsGuide/Determining Which Component Is Broken"
(Created page with "OpenStack’s collection of different components interact with each other strongly. For example, uploading an image requires interaction from <code>nova-api</code>, <code>glan...")
m (David.desrosiers moved page Determining Which Component Is Broken to OpsGuide/Determining Which Component Is Broken without leaving a redirect)
Latest revision as of 13:57, 14 November 2017
OpenStack’s collection of different components interact with each other strongly. For example, uploading an image requires interaction from
glance-registry, keystone, and potentially
swift-proxy. As a result, it is sometimes difficult to determine exactly where problems lie. Assisting in this is the purpose of this section.
The first place to look is the log file related to the command you are trying to run. For example, if
openstack server list is failing, try tailing a nova log file and running the command again:
Look for any errors or traces in the log file. For more information, see Logging and Monitoring.
If the error indicates that the problem is with another component, switch to tailing that component’s log file. For example, if nova cannot access glance, look at the
Wash, rinse, and repeat until you find the core cause of the problem.
Running Daemons on the CLI
Unfortunately, sometimes the error is not apparent from the log files. In this case, switch tactics and use a different command; maybe run the service directly on the command line. For example, if the
glance-api service refuses to start and stay running, try launching the daemon from the command line:
This might print the error and cause of the problem.