000017212 - Error message 'There is an error synchronizing repo. Please check the repo configuration.' displayed in RSA Security Analytics

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

Article Content

Article Number000017212
Applies ToRSA Security Analytics
RSA Live
IssueError message "There is an error synchronizing repo. Please check the repo configuration." displayed in RSA Security Analytics.
Although connectivity tests in the "Updates" tab in the Security Analytics UI pass successfully, it is observed that when clicking on Administration->Devices, selecting a device and clicking on "Refresh Status" results in an error an error on every device similar to the following: "There is an error synchronizing repo. Please check the repo configuration."

When typing "yum list" from the command line, an error similar to the following is displayed:

[Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'smcupdate.emc.com'"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: sa. Please verify its path and try again

When typing "yum list" from the command line, an error similar to the following is displayed:  [Errno 14] PYCURL ERROR 22 - "the requested URL returned error: 401 Authorization Required'"

In addition to being configured in the UI, the live updates username, password and repo mirror hostname is stored on the SA server in the file /etc/yum.repos.d/sa.repo file. 
When either the live username, password, mirror hostname changes, the sa.repo configuration file must be manually updated to reflect this change.  Changing information in the UI does not update the sa.repo file.

On an initial installation, the sa.repo file will also need to be configured from the command line manually.  Therefore, the repository hostname, username or password is incorrect in the /etc/yum.repos.d/sa.repo configuration file.


This is a known issue and has been permanently resolved in RSA Security Analytics 10.3 SP5.  Alternatively, a workaround to resolve the issue is found in the steps below.

  1. Ensure that smcupdate.emc.com is resolvable from the command line by executing the following command:

         [root@rsareNsa-00-1 yum.repos.d]# getent hosts smcupdate.emc.com    smcupdate.emc.com

  2. Navigate to the appropriate directory with the following command:  cd /etc/yum.repos.d
  3. Make a backup of the sa.repo file with the following command:  cp sa.repo sa.repo.backup<date>  (i.e. cp sa.repo sa.repo.backup2014-07-26)
  4. Issue the command vi sa.repo to edit the sa.repo file using the vi editor.
  5. Locate the line beginning with baseurl, as shown in the example below.

         baseurl = https://admin.company:abcd123@smcupdate.emc.com/nw10/rpmabcd123@smcupdate.emc.com/nw10/rpm

         In this example:
              -- admin.company represents the RSA Live account username
              -- abcd123 represents the RSA Live account password
  6. Confirm that the username and password are correct and that smcupdate.emc.com is listed as the URL for the repository.
  7. Save the file by hitting the Escape (Esc) key, typing :wq! and pressing enter.
  8. Issue the command yum list | more to verify that the repository is functioning correctly.  The command should display a list of RPM packages and no errors should be displayed. 
    As it is a simple query listing against the currently configured yum repository in the sa.repo file, it can be executed at any time without any adverse effects on production environments.

  9. Repeat Step 8 to confirmthat the repository is functioning correctly.

If issues are still being experienced, it may be necessary to restart the jettysrv service by issuing the commands below.  NOTE:  This will result in a brief period during which the Security Analytics UI will be inaccessible.

  1. stop jettysrv
  2. start jettysrv


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.  You may also wish to have RSA Support first verify your RSA Live username, and reset your password before further troubleshooting actions are taken.

NotesThis issue may also be caused by corrupt .rpm files present on the Security Analytics server.  To confirm whether or not this is the case, refer to the knowledgebase article Updates Repository error "There is an error synchronizing repo" in RSA Security Analytics due to corrupt .rpm files.
Legacy Article IDa66782