000017480 - Updates Repository error 'There is an error synchronizing repo' in RSA Security Analytics due to corrupt .rpm files

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000017480
Applies ToRSA Security Analytics
RSA Security Analytics Server
IssueUpdates Repository error "There is an error synchronizing repo" in RSA Security Analytics due to corrupt .rpm files.

After navigating to Administration -> System -> Updates in the Security Analytics UI and clicking on the Updates Repository tab, the following error message is displayed:  "There is an error synchronizing repo. Please check the repo configuration"


CauseIf a .rpm file in the Security Analytics Server repository is corrupt or is an incomplete download, then this error may occur.
Resolution

In order to confirm and resolve the issue, connect to the Security Analytics server via SSH as the root user and follow the steps below.


 


1.  Find which .rpm files(s) may be having an issue by running the following command:  reposync -l -u -q -p /var/netwitness/srv/www/rsa/updates/RemoteRPMs


Any URLs shown in the output should only refer to the "smcupdate.emc.com" site, and are .rpm file(s) to investigate for an issue.
Any reference to a URL for another site like, "centos.org" indicates a wrong repository site is configured within a file in the SA appliance /etc/yum.repos.d directory.  Refer to the SA Upgrade Instructions document for your Security Analytics version for details on where to move any CentOS-*.repo files, referring to the section on "Configure and Update a Device Using the SA Server Update Repository Manually".


For example the output from the command could appear similar to the following:



https://{username}:{password}@smcupdate.emc.com/nw10/rpm/pam_krb5-2.3.11-9.el6.x86_64.rpm
https://{username}:{password}@smcupdate.emc.com/nw10/rpm/pam_ldap-185-11.el6.x86_64.rpm



If no output is returned, refer to the knowledgebase article Error message "There is an error synchronizing repo. Please check the repo configuration." displayed in RSA Security Analytics to confirm if the issue is caused by an error in the /etc/yum.repos.d/sa.repo file.


 


2. With problem .rpm file(s) found, try to fix by re-downloading any problem .rpm file(s) into the Security Analytics Server RemoteRPMs repository by running the following command:  reposync -l -q -p /var/netwitness/srv/www/rsa/updates/RemoteRPMs


NOTE:  The reposync may take a long time to run if it finds any large problem .rpm file(s), which it will try to download.


 


3. If the re-download attempt still fails, then delete or move the problem file(s) from the Repository directory, as shown below.



For repo id = nwupdate, see directory /var/netwitness/srv/www/rsa/updates/RemoteRPMs
For repo id = sa, see directory /var/netwitness/srv/www/rsa/updates/RemoteRPMs/sa



To determine which repo id is enabled, issue the following command:  yum repolist


For example, the re-download could fail with an error similar to the following:



[sa: 371 of 522 ] Downloading pam_krb5-2.3.11-9.el6.x86_64.rpm
Could not retrieve package pam_krb5-2.3.11-9.el6.x86_64. Error was failure: pam_krb5-2.3.11-9.el6.x86_64.rpm from sa: [Errno 256] No more mirrors to try.
[sa: 372 of 522 ] Downloading pam_ldap-185-11.el6.x86_64.rpm
Could not retrieve package pam_ldap-185-11.el6.x86_64. Error was failure: pam_ldap-185-11.el6.x86_64.rpm from sa: [Errno 256] No more mirrors to try.



 


4. Return to the Security Analytics UI and navigate to Administration -> System -> Updates and click on the  Updates Repository tab.
Ignore the error "There is an error synchronizing repo" and click OK.
Click Synchronize Now.
Confirm Yes.


 


5. Wait for the Synchronize to complete.  It can take a long time if there are any other large .rpm file(s) to download.
Check in about 30 minutes in the Security Analytics UI (Administration -> System -> Updates, Updates Repository tab) that the issue is now resolved.


 


If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article ID for further assistance.

Legacy Article IDa67746

Attachments

    Outcomes