Troubleshooting¶
Log location¶
By default, logs are sent to stdout. Let’s consider how log files can be set up.
Murano API + Engine¶
To define a file where to store logs, use the log_file
option in the
murano.conf
file. You can provide an absolute or relative path.
To enable detailed log file configuration, set up logging.conf
.
The example is provided in etc/murano
directory. The log configuration
file location is set with the log_config_append
option in the murano
configuration file.
Murano applications¶
Murano applications have a separate logging handler and a separate file
where all logs from application definitions should be provided.
Open the logging.conf
file and check the
args: ('applications.log',)
option in the handler_applications
section.
Verify that log_config_append
is not empty and set to the
logging.conf
location.
Problems during configuration¶
If any problems occur, first of all verify that:
- All murano components have consistent versions: murano-dashboard and
murano-engine should use the same or compatible python-muranoclient version.
Dependent component versions can be found in
requirements.txt
file. - The database is synced with code by running:
Failed to execute `murano-db-manage`
- Make sure
--config-file
option is provided. - Check connection parameter in provided configuration file. It should be a connection string.
- Check that MySQL or PostgreSQL (depending of what you provided in connection string) Python modules are installed on the system.
Murano panel is not seen in horizon
- Make sure that
_50_murano.py
file is copied toopenstack-dashboard/local/enabled
directory and there is no other file, starting with_50
. - Check that murano data is not inserted twice in the settings file and as a plugin.
Murano panel can be browsed, but ‘Unable to communicate to murano-api server.’ appears
If you have murano registered in keystone, verify the endpoint URL is valid
and service has application_catalog name. If you don’t want to register
murano service in keystone, just add MURANO_API_URL
option to the horizon
local setting.
Problems during deployment¶
Besides identifying errors from log files, there is another and more flexible way to browse deployment errors - directly from UI. When the Deploy Failed status appears, navigate to
and click the Latest Deployment Log tab. You can see steps of the deployment and the one that failed would have red color.while scanning a simple key in “<string>”, line 32, column 3: ...
There is an error in YAML file format. Before uploading a package, validate your file in an online yaml validator like YAMLint. Later validation tool to check package closely while uploading will be added.
NoPackageForClassFound: Package for class io.murano.Environment is not found
Verify that murano core package is uploaded. If not, the content of meta/io.murano folder should be zipped and uploaded to Murano.
The murano-agent did not respond within 3600 seconds
- Need to check transport access to the virtual machine (verify that the router has a gateway).
- Check the RabbitMQ settings: verify that the agent has valid RabbitMQ
parameters.
Go to the spawned virtual machine and open
*/etc/murano/agent.conf
on the Linux-based machine orC:\Murano\Agent\agent.conf
on Windows-based machine. Also, you can examine agent logs, located by default at/var/log/murano-agent.log
The first part of the log file contains reconnection attempts to the RabbitMQ since the valid RabbitMQ address and queue have not been obtained yet. - Verify that the
notification_driver
option is set tomessagingv2
murano.engine.system.agent.AgentException
Agent started the execution plan, but something went wrong. Examine agent logs (see the previous paragraph for the logs placement information). Also, try to manually execute the application scripts.
[exceptions.EnvironmentError]: Unexpected stack state NOT_FOUND or UPDATE_FAILED
A problem with heat stack creation, examine the heat log file. Try to
manually spawn the instance. If in the reason of stack creation fail is
no valid host was found
, probably there is not enough resources or
something is wrong with nova-scheduler.
Router could not be created, no external network found
Find the external_network
parameter in the networking section of
murano configuration file and verify that the specified external network does exist
through Web UI or by executing the neutron net-external-list command.
Deployment log in the UI contains incomplete reports
Sometimes logs contain only two messages after the application deployment. There are no messages, provided in applications themselves:
2015-09-21 11:14:58 — Action deploy is scheduled
2015-09-21 11:16:43 — Deployment finished successfully
To fix the problem, set the notification_driver
option in the murano.config
file to messagingv2
.