Skip to main content
Juanes
Juanes
Gold ⭐️
August 22, 2024
Solved

Failed to install cloudera-manager-agent package

Hello Community,

Back again with different version same issue ...

Juanes_0-1724326990759.png

added the proxy settings, properly, this is reaching out the Runtime repos but not the CM repo...

don't know how to set this to make the installer to work, this is exhausting...

where is this taking the info from??? 
Checking https://[userpass]@archive.cloudera.com/p/cm7/7.11.3.0/repodata/repomd.xml

this URL is not existing!

Juanes_1-1724327195341.png

and then is creating  cloudera.repo file empty

Juanes_2-1724327413515.png

why is so dificult to make this installer to work? 

and yes, there is connectivity froem the serrvers to CLOUDERA:

Juanes_3-1724327581405.png

anyone knows how to install this CM 7.11.3 and CDP 7.1.9?

 

 

    Juanes
    JuanesAnswer
    Gold ⭐️
    August 26, 2024

    Hi All,

    Will clarify the WORKARROUND in case it helps anyone...

    The wizard installer is composed of 2 phases defined in the "Select Repository" screen:

    [Phase1] The Cloudera Manager processes (jdk if needed, cloudera-scm-agent, cloudera daemons)

    [Phase2] The Runtime (the roles like impala, kudu, Hive...)

    Main issue was that the install attempt for the Phase1 did not took into accout the Poxy added for the Runtime repo, failing all the time, even setting the proxy in /etc/bashrc for letting eny user to use it.

    Here are two solutions:

    1º to manuall install the services required by the [Phase1] using the /etc/yum.repos.d/cloudera-manager.repo (used yum in my case)

    openjdk8-1.8.0_372_cloudera-1.x86_64, cloudera-manager-agent.x86_64 in all servers. then retry the wizard (it will detect the packages are already installed and jump to the Runtime part)

    2º setting the proxy in /etc/yum.conf

    proxy=http://user:pass@proxy-IP:8080

    and disable all other repos (I had to do this to avoid yum to fail) NOTE: maybe the installer fails because the Cloudera-manager-agent.x86_64 has many dependencies and some of then might be in the OS repo (This is why I installed it manually)

     

     

    View in thread

    5 replies

    Juanes
    JuanesAuthor
    Gold ⭐️
    August 23, 2024

    some trace logs...

    BEGIN which wget
    /usr/bin/wget
    END (0)
    BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest/meta-data/public-hostname && /bin/echo
    END (4)
    ###CLOUDERA_SCM### REPO_INSTALL
    Checking http:---------------------:---------------------@archive.cloudera.com/p/cm7/7.11.3/redhat8/yum/repodata/repomd.xml
    Checking http://---------------------:---------------------@archive.cloudera.com/p/cm7/7.11.3/repodata/repomd.xml
    Using
    installing repository file /tmp/scm_prepare_node.GXl2U46v/repos/rhel8/cloudera-manager.repo
    repository file /tmp/scm_prepare_node.GXl2U46v/repos/rhel8/cloudera-manager.repo installed
    installing rpm keys
    BEGIN gpg --import /tmp/scm_prepare_node.GXl2U46v/customGPG
    gpg: keybox '/tmp/scm_prepare_node.GXl2U46v/gnupg.r31nEei4Sq/pubring.kbx' created
    gpg: /tmp/scm_prepare_node.GXl2U46v/gnupg.r31nEei4Sq/trustdb.gpg: trustdb created
    gpg: key 327574EE02A818DD: public key "Cloudera Apt Repository" imported
    gpg: key F90C0D8FE8F86ACD: public key "Yum Maintainer <webmaster@cloudera.com>" imported
    gpg: key E03FC402BB5B82D3: public key "ClouderaManager <security@cloudera.com>" imported
    gpg: key 2279662784415700: public key "Cloudera <security@cloudera.com>" imported
    gpg: key B9733A7A07513CAD: public key "Jenkins (HDP Builds) <jenkin@hortonworks.com>" imported
    gpg: Total number processed: 5
    gpg: imported: 5
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    BEGIN sudo rpm --import /tmp/scm_prepare_node.GXl2U46v/---------------------.pub
    END (0)
    ###CLOUDERA_SCM### REFRESH_METADATA
    BEGIN sudo yum --disablerepo=* --enablerepo=cloudera* clean all
    Updating Subscription Management repositories.
    Unable to read consumer identity

    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

    36 files removed
    END (0)
    BEGIN sudo rm -Rf /var/cache/yum/*
    END (0)
    BEGIN sudo yum --disablerepo=* --enablerepo=cloudera* makecache
    Updating Subscription Management repositories.
    Unable to read consumer identity

    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

    Error: Cannot find a valid baseurl for repo: cloudera-manager
    END (1)
    ###CLOUDERA_SCM### PACKAGE_INSTALL cloudera-manager-agent
    BEGIN sudo yum list installed cloudera-manager-agent
    Updating Subscription Management repositories.
    Unable to read consumer identity

    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

    Error: No matching Packages to list
    END (1)
    BEGIN sudo yum info cloudera-manager-agent
    Updating Subscription Management repositories.
    Unable to read consumer identity

    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

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

    Juanes_0-1724396043265.png

     

    Translate
      Juanes
      JuanesAuthor
      Gold ⭐️
      August 23, 2024

      added the proxy in Parcel Repository & Network Settings

      Juanes_1-1724402559607.png

      but this config is not used at all, not reaching the repo....

       
       

      Juanes_0-1724402462237.png

       

       

      Translate
        vats
        Gold ⭐️
        vats
        Gold ⭐️
        August 23, 2024

        @Juanes 

        The error message suggests that the system is not registered to Red Hat Subscription Management and recommends using subscription-manager to register. Additionally, it states that there is an issue with finding a valid baseurl for the cloudera-manager repository.

        To resolve this issue, you can follow these steps:

        1. Register the system with Red Hat Subscription Management using the subscription-manager tool. Run the following command as root or with sudo privileges:
        subscription-manager register
         

        Follow the prompts and provide the necessary information to register the system.

        2.Once the system is registered, you need to enable the required repository. Run the following command:

        subscription-manager repos --enable=<repository-name>
         

        Replace <repository-name> with the specific repository name you want to enable, such as 'rhel-7-server-rpms' or 'rhel-7-server-optional-rpms'. You may also need to enable additional repositories depending on your requirements.

        3.After enabling the repository, try running the command again. If you still encounter the same error related to the cloudera-manager repository, you may need to check the repository configuration file for any issues. The configuration file is usually located in the '/etc/yum.repos.d/' directory. Check if the 'baseurl' parameter is correctly set.

        Translate
          Juanes
          JuanesAuthor
          Gold ⭐️
          August 23, 2024

          Hello, is this subscription manager mandatory for installing CDP¿? I did several deployments and this is the first time I read this.

          I'm able to access and install using YUM from the repos:

          Juanes_0-1724406580626.png

          but the installer not... neither to get a clearer clue about what's happening...

          it seems it's doing a curl  to the repomd.xml
          Curl error (28): Timeout was reached for https://-----------@archive.cloudera.com/p/cm7/7.11.3/redhat8/yum/repodata/repomd.xml

          but the proxy was added to the PROXY FIELDS in teh installer and seems not working...

          Translate
            Juanes
            JuanesAuthorAnswer
            Gold ⭐️
            August 26, 2024

            Hi All,

            Will clarify the WORKARROUND in case it helps anyone...

            The wizard installer is composed of 2 phases defined in the "Select Repository" screen:

            [Phase1] The Cloudera Manager processes (jdk if needed, cloudera-scm-agent, cloudera daemons)

            [Phase2] The Runtime (the roles like impala, kudu, Hive...)

            Main issue was that the install attempt for the Phase1 did not took into accout the Poxy added for the Runtime repo, failing all the time, even setting the proxy in /etc/bashrc for letting eny user to use it.

            Here are two solutions:

            1º to manuall install the services required by the [Phase1] using the /etc/yum.repos.d/cloudera-manager.repo (used yum in my case)

            openjdk8-1.8.0_372_cloudera-1.x86_64, cloudera-manager-agent.x86_64 in all servers. then retry the wizard (it will detect the packages are already installed and jump to the Runtime part)

            2º setting the proxy in /etc/yum.conf

            proxy=http://user:pass@proxy-IP:8080

            and disable all other repos (I had to do this to avoid yum to fail) NOTE: maybe the installer fails because the Cloudera-manager-agent.x86_64 has many dependencies and some of then might be in the OS repo (This is why I installed it manually)

             

             

            Translate
              Terms & ConditionsAccessibility statement