- Newest
- Most votes
- Most comments
In addition to the Agent's answer, you should run this command first, as it is the most likely to resolve the issue:
sudo update-crypto-policies --set FIPS
Afterwards, proceed with the reinstallation of crypto-policies as suggested by the AI.
The error you're encountering appears to be related to SSL/TLS configuration issues rather than an actual out-of-memory condition, despite the error message. The "SSL: could not create a context: error:0A000180:SSL routines::bad value" portion of the error is the key indicator here.
This type of error typically occurs when there's a problem with the system's cryptographic policies or SSL/TLS libraries after an upgrade. When you upgraded to a newer release version, it's possible that changes to crypto-policies or related SSL libraries are causing compatibility issues with the repository connections.
Here are some steps you can try to resolve this:
- Update crypto-policies: The crypto-policies package manages system-wide cryptographic policies. Try updating it explicitly:
sudo dnf upgrade crypto-policies crypto-policies-scripts
- Check your system's crypto policy: Verify the current policy setting:
update-crypto-policies --show
- Reinstall or update curl and related packages: Since the error mentions curl, try updating curl and its dependencies:
sudo dnf reinstall curl libcurl
- Clear DNF cache: Sometimes cached metadata can cause issues:
sudo dnf clean all
- Check available memory: Although this appears to be an SSL issue, verify your instance actually has sufficient memory available using
free -hto rule out genuine memory constraints.
If the issue persists after trying these steps, you may need to review the release notes for the specific version you upgraded to, as there may have been significant changes to SSL/TLS handling or crypto-policies that require additional configuration adjustments.
Sources
Using Deterministic upgrades through versioned repositories - Amazon Linux 2023
Manage package and operating system updates in AL2023 - Amazon Linux 2023
Only need to change the policy to FIPS: sudo update-crypto-policies --set FIPS
Relevant content
- asked 2 years ago

Changing to FIPS resolved the problem: sudo update-crypto-policies --set FIPS