How to troubleshoot deployment issues

Navigating to the deployment log file

 ![TODO](images/)

Analyzing the deployment failure

The first thing you should verify is that the three prerequisite services (pipes-cloudant-service, pipes-dashdb-service and pipes-dataworks-service) were created successfully.

• In the log file search for Binding service. Three entries should be displayed if all services were created successfully:

Binding service pipes-cloudant-service to app pipes-<project name> in org <your_org_name>_org / space <your_space_name> as <your_bluemix_id>...
OK
Binding service pipes-dashdb-service to app pipes-<project name> in org <your_org_name>_org / space <your_space_name> as <your_bluemix_id>...
OK
Binding service pipes-dataworks-service to app pipes-<project name> in org <your_org_name>_org / space <your_space_name> as <your_bluemix_id>...
OK

• Service creation failed and application deployment was stopped if a message similar to the following is displayed:

  FAILED
  Could not find service pipes-dataworks-service to bind to pipes-<project name>
  Build step 'Execute shell' marked build as failure
  

Should you encounter this problem, check the service status on the Bluemix support status page:

• Open the and log in.

• Click on the user account icon.

• Select Status.

• Locate the SERVICES section.

• Check the status for Cloudant NoSQL DB, dashDB and DataWorks.
  

• If issues are reported, check the system status messages and announcements on the right hand side.