Configuration of Media Server Deduplication Pool (MSDP) fail with "system call failed(11)" due to system proxy

Problem

When configuring a new MSDP pool on a media server the configuration is failing and reporting "system call failed(11)"  and sometimes that the server is shutdown.

Error Message

<MSDP_PATH>/log/pdde-config.log

Starting PDDE Mini SPA: spad [  OK  ]
spad (pid  8971) is running...
Wed Jul  7 09:32:36 WEST 2021 Polling spad failed.  Sleeping for 5 seconds; 175 seconds remaining before timeout.
Wed Jul  7 09:32:41 WEST 2021 Polling spad failed.  Sleeping for 5 seconds; 170 seconds remaining before timeout.
<SNIP>
Wed Jul  7 09:35:29 WEST 2021 Polling spad failed.  Sleeping for 5 seconds; 5 seconds remaining before timeout.
Wed Jul  7 09:35:34 WEST 2021 \nERROR: PDDE initial configuration failed.  Unable to initialize/start spad within 180 seconds

<MSDP_PATH>/log/spad/spad.log

July 07 09:32:36 ERR [140285763794688]: -1: Execute: failed to perform CURL session. error is: Received HTTP code 403 from proxy after CONNECT
July 07 09:32:36 ERR [140285763794688]: -1: GetToken: curl_.Execute(): https://nbumaster:1556/netbackup/loginwithcert error.
July 07 09:32:36 ERR [140285763794688]: -1: ValidateHost: failed to get token
July 07 09:32:36 ERR [140285763794688]: -1: validate_host_cert: validate the host nbumedia uuid 9320da77-3c61-4980-9dfd-9dbdbbb1649a cert failed.
July 07 09:32:36 ERR [140285763794688]: 25056: Agent at nbumedia certificate is invalid.
July 07 09:32:36 ERR [140285763794688]: 25099: Could not send binary message: sent -1 instead of 55 bytes. Cause: broken pipe

Cause

In this case there were a system level http/https proxy environment configured on the system which was being used by spad to connect to the master server and this was failing. This can be confirmed with the "env" command on Linux/Unix environment, and with "netsh winhttp show proxy" command in Windows environment. for example:

# /usr/bin/env |grep http
http_proxy=http://10.10.10.10:3128/
https_proxy=http://10.10.10.10:3128/

>netsh winhttp show proxy

Current WinHTTP proxy settings: http_proxy=http://10.10.10.10:3128/
https_proxy=http://10.10.10.10:3128/
Direct access (no proxy server).

Solution

The solution is to remove the system wide proxy configuration from the Operating System before configuring the MSDP pool so communication to the master server's webservice can complete successfully.

On Windows we can reset the proxy by running "netsh winhttp reset proxy".

On linux to remove the environment variable
unset https_proxy
unset http_proxy