Capsule sync fails with CRC check failed

Environment

• Red Hat Satellite 6

Issue

• Capsule sync in failing with:

    RPM1004: Error retrieving metadata: A connection error occurred
    PLP0000: CRC check failed 0x2a731d0e != 0x8dfd3e1aL
  

Resolution

On the Capsule take the following actions:

1. Move original file to backup

    # cp /etc/pulp/server/plugins.conf.d/yum_importer.json /etc/pulp/server/plugins.conf.d/yum_importer.json.bkp
   

2. Modify the file so it includes the option "validate": true

    # cat /etc/pulp/server/plugins.conf.d/yum_importer.json | python -m json.tool
    {
        "gpg_sign_metadata": false,
        "max_speed": null,
        "proxy_host": null,
        "proxy_password": null,
        "proxy_port": null,
        "proxy_username": null,
        "validate": true
    }
   

3. Restart pulp services, easiest to just restart all Satellite services

    # foreman-maintain service restart
   

4. Perform a Complete Capsule sync from Satellite

   • WebUI -> Infrastructure -> Capsules -> select the Capsule -> Synchronize -> Complete Sync

5. Verify if the Capsule sync completed without errors

6. Restore the file on the Capsule

    # cp /etc/pulp/server/plugins.conf.d/yum_importer.json.bkp /etc/pulp/server/plugins.conf.d/yum_importer.json
   

7. Restart the services again

    # foreman-maintain service restart
   

8. Ensure that the network bandwidth is good enough to download the packages/metadata.

Note that validate=true has a performance impact, since pulp needs to recheck the existence of every file on the filesystem.

For more KB articles/solutions related to Red Hat Satellite 6.x Capsule Sync Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Capsule Sync Issues

Root Cause

Can be caused by hitting full disk space on the Capsule.

Diagnostic Steps

Capsule sync task has the following error:

RPM1004: Error retrieving metadata: A connection error occurred
PLP0000: CRC check failed 0x2a731d0e != 0x8dfd3e1aL
RPM1004: Error retrieving metadata: A connection error occurred

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.