PowerProtect: Backup Agent cannot be reached, or the service is not running ABA0009

The initial file system backup fails with:

CRITICAL
ABA0009 
Protection of these assets was unsuccessful because either the Agent host cannot be reached or the Agent service is not running.
Details
my-protection-policy-name: Unable to backup FILE_SYSTEM asset / on host my-client.my-domain.com because of an agent host connection or agent service issue.

The Dell PowerProtect Agent Service Daemon (agentsvc) status shows that the daemon is inactive on the client. Attempting to start the agentsvc stops immediately and does not remain online.

my-client:~# systemctl status agentsvc 
* agentsvc.service - Dell PowerProtect Agent Service Daemon
   Loaded: loaded (/etc/systemd/system/agentsvc.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu YYYY-MM-DD HH:MM:SS CST; 5s ago
  Process: 3331 ExecStop=/opt/dpsapps/agentsvc/register.sh --stop (code=exited, status=0/SUCCESS)
  Process: 3304 ExecStart=/opt/dpsapps/agentsvc/agentService config=/opt/dpsapps/agentsvc/config.yml (code=exited, status=0/SUCCESS)
  Process: 3294 ExecStartPre=/bin/mkdir -p /opt/dpsapps/agentsvc/tmp (code=exited, status=0/SUCCESS)
 Main PID: 3304 (code=exited, status=0/SUCCESS)
Month DD 10:30:35 my-client.my-domain.com systemd[1]: Starting Dell PowerProtect Agent Service Daemon...
Month DD 10:30:35 my-client.my-domain.com systemd[1]: Started Dell PowerProtect Agent Service Daemon.
Month DD 10:30:36 my-client.my-domain.com register.sh[3331]: Successfully stopped agent-service.

The OpAgentSvc-*.log shows a message that the Agent was decommissioned during the discovery HOST_COMFIGURATION step:

...
YYYY-MM-DD HH:MM:SS,266359 CST| DBGHTTPSERVER| PID-15180| TID-139754566948608| INFO] HTTPServer.py-retrieve_sessions()-Line 3502- Record fetched: {'response': {'id': 3387335264, 'type': 'HOST_CONFIGURATION', 'status': 'IDLE', 'errorCode': None, 'errorMessage': None, 'subStatus': None}, 'opaque': None}
YYYY-MM-DD HH:MM:SS,331271 CST| DBGHTTPSERVER| PID-15180| TID-139754566948608| INFO] HTTPServer.py-get_session()-Line 3451- Data returned during get_session: {"id": 3387335264, "type": "HOST_CONFIGURATION", "status": "IN_PROGRESS", "errorCode": null, "errorMessage": null, "subStatus": null}
YYYY-MM-DD HH:MM:SS,091674 CST| DBGHTTPSERVER| PID-15180| TID-139754566948608| INFO] HTTPServer.py-full_decommission_client()-Line 4625- Request to decommission host received
YYYY-MM-DD HH:MM:SS,138603 CST| DBGHTTPSERVER| PID-15180| TID-139754566948608| INFO] HTTPServer.py-full_decommission_client()-Line 4651- Created decommission session with job id 18469f3349644211a9b577fbaf373931, status IDLE
...
YYYY-MM-DD HH:MM:SS,405726 CST| AGENTSVC_OP| PID-15159| TID-139754566948608| INFO] main.py-check_if_decommissioned()-Line 600- Decommission Complete. Shutting down agentsvc....
...

The agent host configuration decommissioned the agentsvc as there was a missing package on the client. The install script with the debug option validates any missing packages on the client.

Here is an example output from an Ubuntu 16.04.x client debug installation:

root@my-client:/opt/dpsapps/fsagent/bin# ./install.sh --server=my-ppdm.my-domain.com --debug 
YYYY-MM-DD HH:MM:SS debian based system
YYYY-MM-DD HH:MM:SS Package 'bc' was not installed. Installation shall not proceed.
YYYY-MM-DD HH:MM:SS Refer to the documentation for installation instructions.

Resolve any package dependencies on the Linux file system. Once the package dependencies are addressed, the client installation and registration can be manually performed.

1. Run the agent installation script: /opt/dpsapps/fsagent/bin/install.sh --server=my-ppdm.my-domain.com --debug 
2. Run the agent registration script: /opt/dpsapps/agentsvc/register.sh --enable
3. Validate backups are working for the protected file system.

Here is an example of the procedure:

root@my-client:~# /opt/dpsapps/fsagent/bin/install.sh --server=my-ppdm.my-domain.com --debug 
YYYY-MM-DD HH:MM:SS debian based system
YYYY-MM-DD HH:MM:SS Linux
YYYY-MM-DD HH:MM:SS The adm-agent was not installed.
dpkg-deb: error: failed to read archive 'powerprotect-agentsvc*.deb': No such file or directory
YYYY-MM-DD HH:MM:SS
YYYY-MM-DD HH:MM:SS The powerprotect-agentsvc was installed.
YYYY-MM-DD HH:MM:SS The installed powerprotect-agentsvc version is the same as or later than the deb package version. Install or upgrade will not be attempted. Proceeding further.
dpkg-deb: error: failed to read archive 'ppdm-fsagent*.deb': No such file or directory
YYYY-MM-DD HH:MM:SS
YYYY-MM-DD HH:MM:SS The ppdm-fsagent was installed.
YYYY-MM-DD HH:MM:SS The ppdm-fsagent upgrade was initiated.
YYYY-MM-DD HH:MM:SS The installed File System agent version is the same as or later than the deb package version. Install or upgrade will not be attempted. Proceeding further.
dpkg-deb: error: failed to read archive 'ppdm-bbbwt*.deb': No such file or directory
YYYY-MM-DD HH:MM:SS The ppdm-bbbwt was not installed.
YYYY-MM-DD HH:MM:SS Initiating registration to the PowerProtect Data Manager my-ppdm.my-domain.com.
================================================================
AgentService is already DECOMMISSIONED.
To put the agent-service back into operations, recommission it with --enable flag
================================================================
YYYY-MM-DD HH:MM:SS PowerProtect Data Manager registration failed.
YYYY-MM-DD HH:MM:SS Run /opt/dpsapps/agentsvc/register.sh manually to complete registration to PowerProtect Data Manager.
root@my-client:~#

root@my-client:~# /opt/dpsapps/agentsvc/register.sh --enable
AgentService is recommissioned.
Enter the PowerProtect Data Manager server FQDN or IP address: my-ppdm.my-domain.com
TMPDIR set to value /opt/dpsapps/agentsvc/tmp
Agent service (pid 21180) started successfully.
Checking for PowerProtect Data Manager server Accessibility.
PowerProtect Data Manager server is Accessible.
root@my-client:~#