Bobcares

Failed to synchronize cache for repo appstream | Troubleshooting Tip

by | Mar 4, 2023

How to fix the “Failed to synchronize cache for repo appstream” error? At Bobcares, with our Server Management Services, we can handle your server-related issues.

How to fix the “Failed to synchronize cache for repo appstream” error?

AppStream repository’s content includes more user space programs, runtime languages, and databases to accommodate the range of workloads and use cases. Also, application Streams are specific user space components from the AppStream repository. The distribution is diverse because Application Streams are released on a cadence that is appropriate for each package. The way that many versions of a single package accessible for installation under RHEL 8 improves with the Application Streams.

Moreover, RHEL 8 unifies the previous channels of distribution into one location. Application Streams are offered in the well-known RPM format, as a module-based RPM extension, or as Software Collections. While upgrading CentOS 7 to CentOS 8, we may sometimes see the following error: Failed to synchronize cache for repo ‘appstream’. The error will be like this:

Failed to synchronize cache for repo appstream

The /var/log/dnf.log output showing additional DEBUG information

Failed to synchronize cache for repo appstream

When we see the message, we may think the error is caused by poor network connectivity. But that may not be the case always. There will be a number of causes for this problem. The most typical examples are:

1. incorrectly set time and date.

2. CentOS baseURL.

3. Old dnf cache available or expired.

Solution 1

In CentOS 7 and 8, the timedatectlcommand is a brand-new utility tool. It serves as a replacement for the outdated date command used by Linux distributions with sysvinit daemons. Find the system’s current date and time. Make sure the time zone is set correctly.

Failed to synchronize cache for repo appstream

Now set it to our timezone:

Solution 2

In order to clean Old/expired dnf cache, use the command:

Solution 3

In order to change CentOS baseURL, follow the below steps:

1. Navigate to the /etc/yum.repos.d/ directory.

2. Execute the commands:

Failed to synchronize cache for repo appstream

3. Finally, run  dnf update.

Failed to synchronize cache for repo appstream

[Looking for a solution to another query? We are just a click away.]

Conclusion

The article explains about the error, “Failed to synchronize cache for repo appstream”, along with its causes and the solutions associated with each cause.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF