This document explains how to stop and disable the multipathd service on an OpsRamp Classic Gateway. Use this procedure only when you must ensure that the gateway host does not run the multipathd service and does not automatically start it during system boot or through its associated socket unit.

About multipathd

multipathd is a system daemon that manages multiple I/O paths between a server and shared storage. The service performs the following functions:

  • Monitors the availability and health of storage paths
  • Automatically switches to a healthy path when a failure occurs
  • Balances I/O traffic across available paths to prevent overload

When multipathd is disabled, the operating system no longer performs automatic multipath management. This can affect storage behavior on systems that rely on multipath I/O.

Scope and impact

  • Applies to: OpsRamp Classic Gateway nodes only
  • Impact: Disabling multipathd can affect storage configurations that depend on multipath I/O

Before you proceed, ensure that disabling this service is approved for your environment and does not impact required storage functionality for the gateway host.

Procedure

To disable the multipathd service on an OpsRamp Classic Gateway, follow these steps:

  1. Log in to the Classic Gateway using the ruser account.
ssh ruser@<gateway-hostname-or-ip>

Replace <gateway-hostname-or-ip> with the appropriate gateway address.

  1. Stop the running multipathd service.
    sudo systemctl stop multipathd

(Optional) Verify the service status.

systemctl status multipathd

Expected result: The service status shows inactive (dead). 3. Disable the service to prevent it from starting automatically after a system reboot.

sudo systemctl disable multipathd

Confirm that the service is disabled.

systemctl is-enabled multipathd

Expected output:

disabled
  1. Stop and disable the socket unit.
    The multipathd service includes a socket unit (multipathd.socket) that can automatically start the service. You must stop and disable this socket to prevent the service from being reactivated.

Stop the socket

sudo systemctl stop multipathd.socket

Disable the socket

sudo systemctl disable multipathd.socket

Verify the socket status.

systemctl is-enabled multipathd.socket

Expected output:

disabled

Validation

Verify that both the service and the socket are inactive and disabled.

disabled

systemctl status multipathd systemctl status multipathd.socket Expected result: Both units must show a status of inactive and disabled.

If validation fails If either unit remains active or enabled:

  • Re-run the applicable stop and disable commands.
  • Check whether any system automation or dependent services restart multipathd.

Re-enable multipathd (if required)

If you need to restore the default behavior, re-enable and start the service.

sudo systemctl enable multipathd.socket
sudo systemctl enable multipathd
sudo systemctl start multipathd

Verify the status.

systemctl status multipathd
systemctl status multipathd.socket