> 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-failed-multipathd-service-not-running-on-destina.md).

# Live Migration Failed, Multipathd Service Not Running on Destination Host

## Problem

Instance live migration fails with below error in *ostackhost.log* of source host.

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

```none
ERROR nova.compute.manager [-] [instance: "instance-id"] Pre live migration failed at "destination-host-uuid": RemoteError: Remote error: ProcessExecutionError Unexpected error while running command.Command: multipathd show statusExit code: 1...TRACE nova.compute.manager [instance: "instance-id"] Stderr: u'ux_socket_connect: Connection refused<br>'
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* multipathd
* pf9-ostackhost

## Cause

* The ***pf9-ostackhos*** t service on the source and the destination host is configured to use the multipath connection for volumes.

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

```none
# less /opt/pf9/etc/nova/conf.d/nova_override.conf..volume_use_multipath = True..
```

{% endtab %}
{% endtabs %}

* Once the live migration is initiated, a pre-live migration check is performed to confirm if the destination host is running the ***multipathd*** service.
* If this pre-live migration check fails, the below command on the destination host will give the error mentioned in the problem section on source host.

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

```none
$ multipathd show status
```

{% endtab %}
{% endtabs %}

* On the destination host, we can observe the error message with the live-migration request ID as below.

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

```none
ERROR os_brick.initiator.linuxscsi [req-xxxxxxxxxxx user@domain service] multipathd is not running: exit code 1: ProcessExecutionError: Unexpected error while running command.
```

{% endtab %}
{% endtabs %}

* Check the status of ***multipathd*** service on the destination host.

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

```none
$ systemctl status multipathd.service
```

{% endtab %}
{% endtabs %}

* This issue is most often observed if the ***multipathd*** service is not running on the destination host.

## Resolution

* Check multipath configuration in */* *etc/multipath.conf* file on destination host.
* If the configuration is correct, start the ***multipathd*** service if not running on the destination host.

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

```none
$ systemctl start multipathd.service
```

{% endtab %}
{% endtabs %}


---

# 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-failed-multipathd-service-not-running-on-destina.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.