Troubleshooting the msdpcmdrun issues

The following table lists the msdpcmdrun issues and how to troubleshoot those.

Table: The msdpcmdrun issues

Issue	Resolution
The following error message appears: "The operating system user must be part of the deduplication administrator group to run msdpcmdrun command."	The user attempting to run the msdpcmdrun command is not part of the deduplication administrator group. The administrator must add the user to the pdadmin group. See Configuring a non-root user to run MSDP commands through msdpcmdrun .
The following error message appears: "msdpcmdrun failed to connect to the admin service."	The msdpcmdrun is not able to communicate to the PureDisk Privileged Access Service (PDPAS) service. It may occur due to following reasons: The PDPAS service is not running. A new user is added to the pdadmin group but cannot access the PDPAS service. To resolve this issue: Start the PDPAS service if it is not running. /usr/openv/pdde/pdconfigure/pdde pdpas start If the PDPAS service is already running, restart it. /usr/openv/pdde/pdconfigure/pdde pdpas stop ps -ef \| grep pdpas /usr/openv/pdde/pdconfigure/pdde pdpas start
The PDPAS service fails to stop using bp.kill_all command.	Sometimes, when attempting to stop the PDPAS service, the bp.kill_all command may fail, leaving the service running. To resolve this issue: Stop the PDPAS service using the following command: /usr/openv/pdde/pdconfigure/pdde pdpas stop If the process persists, locate the PDPAS process ID (PID) and kill it manually. Identify the PID of the running PDPAS service: ps -ef \| grep pdpas Force kill the process: kill -9 <PDPAS_PID> Verify that the process is no longer running: ps -ef \| grep pdpas
After the PDPAS service is stopped, it starts running again.	A cron job runs every 5 minutes to monitor PDPAS. If it is not running, the PDPAS service is started automatically. If you want to stop the auto-start of the PDPAS service, you can disable the cron utility or remove the cron file, which monitors the PDPAS service. To disable the cron utility, use operating system-specific command to stop the cron service. For example, on RHEL 8, use following command: systemctl status crond.service To remove the cron file, run the following command: rm /etc/cron.d/pdpas_monitor.cron
One or both of the following error messages appear at the start of the output of the msdpcmdrun command: "Failed to receive a response from the admin service." "Error: -1: recvmsg failed: 88"	The msdpcmdrun can successfully communicate with the PDPAS service, but occasionally, race conditions in the operating system may cause error messages to appear at the start of the command output. To resolve this issue, restart the PDPAS service. /usr/openv/pdde/pdconfigure/pdde pdpas stop ps -ef \| grep pdpas /usr/openv/pdde/pdconfigure/pdde pdpas start

Issue

Resolution

The following error message appears:

"The operating system user must be part of the deduplication administrator group to run msdpcmdrun command."

The user attempting to run the msdpcmdrun command is not part of the deduplication administrator group.

The administrator must add the user to the pdadmin group.

See Configuring a non-root user to run MSDP commands through msdpcmdrun .

The following error message appears:

"msdpcmdrun failed to connect to the admin service."

The msdpcmdrun is not able to communicate to the PureDisk Privileged Access Service (PDPAS) service. It may occur due to following reasons:

The PDPAS service is not running.
A new user is added to the pdadmin group but cannot access the PDPAS service.

To resolve this issue:

Start the PDPAS service if it is not running.
/usr/openv/pdde/pdconfigure/pdde pdpas start

If the PDPAS service is already running, restart it.

/usr/openv/pdde/pdconfigure/pdde pdpas stop
ps -ef | grep pdpas
/usr/openv/pdde/pdconfigure/pdde pdpas start

The PDPAS service fails to stop using bp.kill_all command.

Sometimes, when attempting to stop the PDPAS service, the bp.kill_all command may fail, leaving the service running.

To resolve this issue:

Stop the PDPAS service using the following command:
/usr/openv/pdde/pdconfigure/pdde pdpas stop
If the process persists, locate the PDPAS process ID (PID) and kill it manually.
- Identify the PID of the running PDPAS service:
  ps -ef | grep pdpas
- Force kill the process:
  kill -9 <PDPAS_PID>
- Verify that the process is no longer running:
  ps -ef | grep pdpas

After the PDPAS service is stopped, it starts running again.

A cron job runs every 5 minutes to monitor PDPAS. If it is not running, the PDPAS service is started automatically.

If you want to stop the auto-start of the PDPAS service, you can disable the cron utility or remove the cron file, which monitors the PDPAS service.

To disable the cron utility, use operating system-specific command to stop the cron service. For example, on RHEL 8, use following command:
systemctl status crond.service
To remove the cron file, run the following command:
rm /etc/cron.d/pdpas_monitor.cron

One or both of the following error messages appear at the start of the output of the msdpcmdrun command:

"Failed to receive a response from the admin service."
"Error: -1: recvmsg failed: 88"

The msdpcmdrun can successfully communicate with the PDPAS service, but occasionally, race conditions in the operating system may cause error messages to appear at the start of the command output.

To resolve this issue, restart the PDPAS service.

/usr/openv/pdde/pdconfigure/pdde pdpas stop
ps -ef | grep pdpas
/usr/openv/pdde/pdconfigure/pdde pdpas start

Note:

If you encounter any unexpected errors while running msdpcmdrun, restart the PDPAS service.

Troubleshooting the msdpcmdrun issues

Feedback

Feedback