## 4.1.8.1.12  Frequently Asked Questions
## My MTA deployment failed. What could be done?
Check the MTA Operation Failure [page 736] section.
## What to do when my application start-up/staging failed?
Check the MTA Operation Failure [page 736] section.
## How can I find the logs of an application from a failed/succeeded deployment?
There are several ways to find the application logs:
- OPERATION.LOG - contains the whole deployment log.
- &lt;application-name&gt;.log - there is a separate file for each application. It holds the logs related to the application during staging and starting.
##  Note
Note that the operation logs are kept for 3 days. Make sure that you download them before the retention period expires.
To download the logs, execute the following command:
cf dmol -i &lt;process-id&gt;
## 
```
Sample Code cf dmol -i cbe58aeb-0c40-4a3e-972d-82a499815745
```
## Whom to contact in case of problems with deployment?
When an error occurs during deployment, there is a message which indicates whether the problem is in one of the components of the Cloud Foundry Platform. In such cases, an incident to the corresponding component could be created.
##  Example
'Controller operation failed: 400 Bad Request: Cannot bind application to service'
For more information, you can also check the Troubleshooting [page 735].
## How to check the state of my deployment?
Use the command cf mta-ops and find the id of the operation related to the desired deployment. There will be information about the status of the operation.
## How can I list the MTAs that I have deployed in my space?
Use the cf mtas command and locate the ID of the desired MTA. After locating the correct MTA ID, execute the command cf mta &lt;located-mta-id&gt; to get detailed information about the MTA with the provided ID.
## What can I do with my deployment?
- If the deployment fails, see MTA Operation Failure [page 736].
- If the deployment finishes successfully, you can check the deployment logs.
- If the deployment is still running, you can abort or monitor it. The Abort action is described in more details in the MTA Operation Failure [page 736] section. The Monitor action can be executed with the following command: cf &lt;operation&gt; -i &lt;operation-id&gt; -a monitor. Example: cf deploy -i 12355 -a monitor
## How can I redeploy my MTA when a deployment is already running?
You can abort the currently running deployment, using the command cf &lt;operation&gt; -i &lt;operationid&gt; -a abort (Example: cf deploy -i 12353 -a abort ) or you can execute the command for starting the deployment by providing the option -f as described in the deploy [page 2555] section.
##  Example cf deploy &lt;path-to-mtar&gt;.mtar -f
## What are the size limits of an MTA?
4GB for the whole MTA and 1GB for a single module. For more information, see Prerequisites and Restrictions [page 601].
## What to do in case of service creation failure?
See MTA Operation Failure [page 736].
## How to make my deployment faster?
You can use a parallel deployment as described in section Parallel Deployment [page 721].
## How can I resolve problems with the MTA descriptor modeling?
For more information, see Defining Multitarget Application Deployment Descriptors for Cloud Foundry [page 606].
## What is the deployment order of services, applications and other content?
Services are always deployed in parallel.
The applications and content deployment order is determined based on the deployed-after module parameter. If deployed-after is not used and parallel deployments are not enabled for the MTA, the requires / provides module sections define the order. For more information, see Parallel Module Deployment [page 720].
## How to reuse one backing service in two different MTAs?
If you want one MTA to 'own' the lifecycle of the service and another to use it only as an 'existing service', use the org.cloudfoundry.managed-service and org.cloudfoundry.existing-service resource types respectively.
## How to define service instance and bindings parameters?
For more information, see Service Binding Parameters [page 680] as well as Service Instance Parameters [page 677].