Support Questions

Find answers, ask questions, and share your expertise

Failed to install cloudera-manager-agent package

avatar
New Contributor

I am trying to install cloudera-manager offline and the above problem occurs when I install cloudera-manager-agent package.

微信图片_20220926155347.jpgInstalling cloudera-manager-agent packs...

BEGIN yum --disablerepo=* --enablerepo=cloudera* list installed cloudera-manager-agent
Loaded plugins:fastestmirror, langpacks
Installed packages
cloudera-manager-agent.x86_64 6.3.1-1466458.el7 installed
END (0)
BEGIN echo oracle-j2sdk1.8 cloudera-manager-agent cloudera-manager-daemons | grep cloudera-manager-agent
END (0)
oracle-j2sdk1.8 cloudera-manager-agent cloudera-manager-daemons
BEGIN yum --disablerepo=* --enablerepo=cloudera* info cloudera-manager-agent
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: cloudera-manager
END (1)
cloudera-manager-agent must have Version=6.3.1 and Build=1466458, exiting
closing logging file descriptor

 

My english is not very good so i am using google translate to ask the question please bear with me.

1 REPLY 1

avatar
Super Collaborator

@Laplace it seems like the cloudera manager repo you are using on that server is not correct, please check the repo and correct it, it could be the URLs present are incorrect.

repo path: /etc/yum.repos.d/