Knowledgebase

Check for "yum-config-manager" error reported on systems using DNF always fails when locale is not "en_US" Print

  • 0

Symptoms

When changes are needed to be made to the repositories on the server, cPanel uses the yum-config-manager application to make these changes. On AlmaLinux/CloudLinux 8+ servers, if the repository does not exist, then the new DNF backend causes an error to be logged. For example:

# yum-config-manager --disable test
Error: No matching repo to modify: test.

This is not an error that needs action on, and thus is typically ignored by the cPanel Software.  However, if the server's locale is not set to English (en_US.UTF-8), the output of this command is treated as an error and thus will fail.

 

Description

When running this application, cPanel specifically checks for the output string "No matching repo to modify" to determine if this was the error experienced.  If a different locale is being used on the server, then the output string would no longer match.

We've opened an internal case for our development team to investigate this further. For reference, the case number is CPANEL-48436. Follow this article to receive an email notification when a solution is published in the product. 

 

Workaround

Any action that requires this the usage of yum-config-manager will need to be done via the command-line, and with the current session's locale set to en_US.UTF-8.  In your shell, run the following:

export LANG="en_US.UTF-8"

Any commands run after this in your current session will use the English locale. Do note, this is not a permanent change and will need to be applied each session if required; this will also not impact any other operation on the server.


Was this answer helpful?
Back

Send Message