General Notes. The following debug sequence should be used when you have no idea about why the system isn't working. If you have one, you may skip unnecessary sections.
Set debug options to "True" in the following Murano configuration files:
/etc/murano-api/murano-api.conf
/etc/murano-conductor/conductor.conf
Stop both murano-api and murano-conductor services. We will start them one by one from the console.
murano-api. First, the murano-api must be started.
Open new console
Start murano-api service manually
># murano-api --config-dir /etc/murano-api 2>&1 >\ /var/log/murano-api-live.log & ># tailf /var/log/murano-api-live.log
Open dashboard, create and send to deploy some simple environment.
Open RabbitMQ web console, open your vhost and ensure that queues were created and there is at least one message.
Check log for errors - there shouldn't be any
Keep murano-api service running
murano-conductor. Next to the murano-api the murano-conductor should be started
Open new console
Start conductor from console
># muranoconductor --config-dir /etc/murano-conductor >\ /var/log/murano-conductor-live.log & ># tailf /var/log/murano-conductor-live.log
Check that there is no python exceptions in the log. Some errors like 404 are ok, as conductor tries to delete environment that doesn't exist
Check heat stack status. It should not be in FAILED state. If it is - check heat and nova error log to find the cause.
Keep murano-conductor service running.
Log Files. There are various log files which will help you to debug the system.
Murano Log Files
/var/log/murano-api.log
/var/log/murano-conductor.log
/var/log/apache2/errors.log
/var/log/httpd/errors.log
Windows Log Files
C:\Program Files (x86)\CloudBase Solutions\logs\log.txt
C:\Murano\Agent\log.txt
C:\Murano\PowerShell.log