Package Deployment fails with "CRC check failed" and "inst_file_start" errors
Article ID: 447930
Updated On:
Products
Issue/Introduction
When attempting to deploy or update probes (such as cdm or robot_update) via the Admin Console, the deployment fails.
The automated_deployment_engine.log on the target robot shows the following errors:
CRC check failed on 'Package:robot_update, File: /opt/nimsoft/probes/service/automated_deployment_engine/ade_package_temp/...java.io.IOException: (1) error, Received status (1) on response (for sendRcv) for cmd = 'inst_file_start'
The deployment status in the console may show "Failed" or "Finished with unknown status."
Environment
DX Unified Infrastructure Management (UIM) Any Version
Component: Robot / Automated Deployment Engine (ADE) - Any Version
OS: Linux (RHEL/CentOS/Ubuntu)
Cause
Disk Full on /opt filesystem.
The Automated Deployment Engine (ADE) downloads and extracts package files into a temporary directory (ade_package_temp). If there is no space to write the file or if the file is truncated during extraction due to a full disk, the CRC (Cyclic Redundancy Check) will fail, and the inst_file_start command will return an error status (1).
Resolution
To resolve this issue, free up space on the target server.
- Verify Disk Space: Log into the affected Linux server and check the disk usage:
df -h /opt
Adjust the path if your Nimsoft directory is installed elsewhere). - Clear Disk Space: Identify and remove unnecessary files. Common areas to check include:
- Old log files in /opt/nimsoft/robot/ or /opt/nimsoft/probes/.
- Large files in /var/log.
- Old temporary files in /tmp or the ADE temp directory.
- Cleanup ADE Temp Folder (Optional): You can manually clear the ADE temporary files to ensure a clean state
rm -rf /opt/nimsoft/probes/service/automated_deployment_engine/ade_package_temp/* - Retry Deployment: Once at least 500MB to 1GB of space is available, retry the deployment of the robot_update or cdm package.
Feedback
