Hi @jludac  You didn't say which release of CDH you're interested in, but assuming you're looking for information describing how to download CDH 6 from Cloudera's private repositories, the best place to start would be the official documentation located here: CDH 6 Download Information   You should only follow those instructions, however, after carefully considering the fact that CDH 6 is well on it's way to reaching its EOS date. CDH 5.x releases have already reached their EoS date. Cloudera's lifecycle support policies are documented here: Support lifecycle policy (open that link and then expand the section labeled "Cloudera Enterprise products" underneath Current End of Support (EoS) Dates).   At that last link (as of this writing) you can read that Cloudera 6.3 is supported until the end of March 2022. For eligible customers, Limited Support for CDH versions 6.2 and 6.3 will be provided during the six-month period beginning on April 1, 2022, and ending on September 30, 2022. So you should understand that in the best case circumstances, any testing you plan to do using CDH will essentially become obsolete later this year.   If you are looking to evaluate a current data platform for use within your company, you can currently do so by downloading and installing the Trial Version of CDP Private Cloud Base Edition of Cloudera Data Platform without a preexisting Cloudera subscription. CDP Private Cloud supersedes CDH as Cloudera's on-premises data platform product and has been generally available since November 2019. If your evaluation needs will extend past the 60-day free trial period governing that downloadable distribution, please reach out to your Cloudera Account Executive to find out how to proceed.     ... View more

Hi @tableau    Please read the relevant Support Announcement here: Cloudera response to CVE-2021-4104 which also has information on what steps to take if the support announcement isn't sufficient to answer your questions.     ... View more

Hi @PT_L  I strongly recommend that you consult the section headed CDP Private Cloud Base Supported Operating Systems on the page titled Operating System Requirements in the section of Cloudera's documentation devoted to CDP Private Cloud.   If you click the hyperlink in that section labeled Cloudera Support Matrix, I think that you'll find that the release of CDP Private Cloud Base that the trial version is based on isn't supported on the release of RHEL you are targeting, and perhaps you have stumbled upon one of the reasons why that is the case.     ... View more

Hi @sagarbot , First and foremost, you should understand that CDH 5.16 reached it's end of support date in December 2020 (open that link and then expand the section labeled "Cloudera Enterprise products" underneath Current End of Support (EoS) Dates). The current Enterprise Data Platform offered by Cloudera is Cloudera Data Platform (CDP), which in it's on-premises "form factor" is offered as CDP Private Cloud. CDP supersedes CDH as it is fairly up to date on all the included components, which is not the case with CDH 5.16. For these reasons, it's going to be increasingly difficult to get answers to your questions about CDH 5.16 going forward, as fewer and fewer members of the community use that version and therefore your organization should be actively looking into upgrading.   That being said, there is a lot going on in the screen shot you provided. I'll focus my response on this bit, based on your Subject line for this post:   [centos@ip-i72-31-2-199 -1$ systemctl status cloudera-scm-server.service . cloudera-scm-server.service - LSB: Cloudera SCM Server Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-server: bad; vendor preset: disabled) Active: active (exited) since Fri 2021-12-31 20:03:52 UTC; 10min ago DOCS: man: systemd-sysv-generator (8) Process: 7268 ExecStop=/etc/rc.d/init.d/cloudera-scm-server stop (code exited, status=1/FAILURE)   If I am interpreting your question correctly, your issue is that the /etc/rc.d/init.d/cloudera-scm-server script is not responding in the desired manner when you supply the stop argument on the command line. If that's the case, you need to consult the logs for that script and deduce what is going on from what is being logged there. It could be any number of things, but I think it will turn out to be a problem addressable with regular Linux (Centos) System Administration skills. I believe that by default, the logs for that script can be found on the Server host at the location /var/log/cloudera-scm-server/cloudera-scm-server.log so that is the first place you should go and look (but it's been a long time since I've seen a CDH-5 based system). You might want to post what you find there in this thread if the problem isn't obvious and perhaps other members of the community who are still running CDH-5 will post something helpful. If the logs aren't present in that directory, you may have to find someone in your organization who knows how the system was installed and configured and ask them.     ... View more

@Fawze that is why I asked @chr_heim what version he was talking about. It's a little imprecise to say "Cloudera is using the 1.x log4j", because different versions of Cloudera's distributions use different versions of the log4j library. If you're interested in CDH 5.x, then sure, the version of the log4j library you most likely have deployed is log4j 1.x (you should confirm this for yourself) and you should confirm for yourself by consulting the appropriate documentation whether or not log4j 1.x is even affected by CVE-2021-44228 and therefore if applying Cloudera's short-term mitigation is necessary. My reading of the advisory that The Apache Security team released earlier this month addressing CVE-2021-44228 is that it affects Apache Log4j, versions 2.0 through 2.14.x. Other versions of CDH use a version of Log4j that is definitely within this affected group.   See Cloudera Response to CVE-2021-44228 for the details.     ... View more

@brconejeros  You didn't provide any detail about which repository you were attempting to download from or the hostname you were using.   If you're attempting to download the binaries for Ambari from Cloudera's repositories you should closely read this announcement: Transition to private repositories for CDH, HDP and HDF   One alternative would be to download and/or install Ambari 2.7.0.x from Apache's site.     ... View more

Christian, You didn't indicate what version of CDH you're running the aforementioned script on, so other members of the community with the appropriate knowledge and inclination to offer assistance won't be able to offer an answer to your questions.      ... View more

@Eric_B Yes. There is a link for non-customers of Cloudera in the blog article linked above. It's at the end of the paragraph beginning "What Cloudera products and versions are affected?"       ... View more

Hi @Army  It appears that you are attempting to run a version of the Cloudera Quickstart VM that is based on CDH 5.4.2. Hopefully you are aware that the 5.4.2 version of CDH was released way back in May 2015 (that was quite a while ago, especially in terms of "internet time") and is probably severely out of date when compared to the hardware, host OS and virtualization platform you are attempting to run it on. In addition, Cloudera is no longer making that version of the Cloudera Quickstart VM available for download because the version of CDH it was based on went out of support last year. For both these reasons, obtaining a quick resolution to your specific issue from the Cloudera Community will be challenging. Unless you have some very compelling reason to run the Quickstart VM, you'd be much better off installing and running a much more up-to-date data platform. The current Enterprise Data Platform available from Cloudera is Cloudera Data Platform (CDP), which in it's on-premises "form factor" is offered as CDP Private Cloud. CDP supersedes CDH as it is fairly up to date on all the included components, which is not the case with CDH 5.4.2. You can download and install the Trial Version of CDP Private Cloud Base Edition of Cloudera Data Platform without an existing valid Cloudera subscription.   All that being said, if you must troubleshoot your particular installation of the Cloudera Quickstart VM, your logical first step would be to examine the log file located on your file system at the location   C:\Users\User\VirtualBox VMs\cloudera-quickstart-vm-5.4.2-0-virtualbox\Logs\VBoxHardening.log   …and take steps based on what it says. You stand a better chance of obtaining assistance if you cut-and-paste the text present in that file in a reply to this thread; that might jog the memory of some other community member with specific expertise on virtual box.     ... View more