> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/live-migration-fails-due-to-rpc-timeout.md).

# Live Migration Fails Due to RPC Timeout

## Problem

Attempts to perform a live migration of an instance fail with an error similar to the below on the source host.

{% tabs %}
{% tab title="None" %}

```none
ERROR nova.compute.manager Pre live migration failed at fea5e264-bfb1-40cd-b1f0-d247845071af...TRACE nova.compute.manager MessagingTimeout: Timed out waiting for a reply to message ID f1e35e10f7c445e3810a115dc3204a24
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Volume-Backed Storage

## Cause

Attempting a live migration of an instance with multiple attached volumes may fail pre-migration checks due to an RPC timeout.

## Resolution

1. Increase the default RPC timeout of 60 seconds using an override in */opt/pf9/etc/nova/conf.d/nova\_override.conf*, as shown here.

{% tabs %}
{% tab title="None" %}

```none
[DEFAULT]rpc_response_timeout = 120
```

{% endtab %}
{% endtabs %}

2. Restart the ***pf9-ostackhost*** service.

{% tabs %}
{% tab title="None" %}

```none
# systemctl restart pf9-ostackhost
```

{% endtab %}
{% endtabs %}

3. Retry the migration operation and further increase the RPC timeout if necessary.

## Additional Information

For more information on Nova configuration options, please refer to the following OpenStack documentation.

[Nova (Pike) Configuration Options](https://docs.openstack.org/nova/pike/configuration/config.html)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/solution/live-migration-fails-due-to-rpc-timeout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.