Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE OpenStack Cloud Crowbar 9

6 Troubleshooting

Before contacting support to help you with a problem on SUSE OpenStack Cloud, we strongly recommended that you gather as much information about your system and the problem as possible. For this purpose, SUSE OpenStack Cloud Crowbar ships with a tool called supportconfig. It gathers system information such as the current kernel version being used, the hardware, RPM database, partitions, and other items. supportconfig also collects the most important log files, making it easier for the supporters to identify and solve your problem.

6.1 Shard Failures

This problem may occur the first time the Log Management Window is opened. It occurs because the Elasticsearch index for the monasca project does not yet exist. A browser reload should fix the problem in most cases.

Kibana shard failure

6.2 Oops! Looks like something went wrong

This problem happens when you were previously logged into horizon and the session expired, leaving a stale session state that confuses Kibana. In this case, re-login to horizon and then reload Kibana to fix the problem.

Oops!

6.3 No results found

This may be due to an overly narrow time window (that is, no logs were sent in the last 15 minutes, which is the default time window). Try increasing the time window with the drop-down box in the screen's top right corner. If the problem persists verify that log agents are running properly; make sure the openstack-monasca-log-agent service is running and check /var/log/monasca-log-agent/agent.log for errors on the agent nodes.

No results
Print this page