@ateka_18 Here is the Cause and Solution of this issue.    Cause:  Microsoft recently rolled out an Active Directory update for CVE-2020-17049 [1]. This update indicates: 'When the registry key is set to 1, patched domain controllers will issue service tickets and Ticket-Granting Tickets (TGT)s that are not renewable and will refuse to renew existing service tickets and TGTs. Windows clients are not impacted by this since they never renew service tickets or TGTs. Third-party Kerberos clients may fail to renew service tickets or TGTs acquired from unpatched DCs. If all DCs are patched with the registry settings to 1, third-party clients will no longer receive renewable tickets. Now the Solution is:   We have found out that MSFT has also released a fix for the Kerberos authentication issue. To fix the Windows AD, you can engage with the AD team to apply one of the following patches that MSFT has provided to fix the Kerberos authentication issue. Please link on the appropriate link based on the flavor of the Windows Server. Windows Server 2012: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594438 Windows Server 2012 R2: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594439Windows Server 2016: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594441 Windows Server 2019: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594442 Windows Server 1903: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594443 Windows Server 1909: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594443 Windows Server 2004: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594440 Windows Server 20H2: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594440 Once the patch is applied, the application will be able to renew the tickets without theneed to apply any patch for Hue. [1] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-17049  So in short you have to ask you AD team to apply the below patch on Domain Controllers to resolve this  issue since it's a Microsoft Vulnerability.  https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-17049   ... View more

@backlashhardik  The manual process means install agent beforehand on all of the hosts which you are going to add. Make sure you have local repo or internet access.    sudo yum install cloudera-manager-agent cloudera-manager-daemons  If agent is installed then reinstall to avoid any issue once again.  sudo yum reinstall cloudera-manager-agent cloudera-manager-daemons  Then you have to modify the /etc/cloudera-scm-agent/config.ini file and post this to CM server, also if TLS is enabled make necessary changes.  [General] # Hostname of the CM server. server_host=host-xx.xxx.xxx.cloudera.com Then go to the CM and try to add hosts from there. Since agent is already installed this should not take much time and you can start agent then and see if that helps.  ... View more

@crcerror Let me try to address your concern:   Does this mean that even the older versions (6.3.x and older) that until now have still been available for download without a subscription, will no longer be available without a subscription? Yes, effective from January 31, 2020 every Cloudera software's binaries can be only accessed via a valid subscription.  Does that mean that if you have a cluster running 6.3.x without a subscription, you can no longer add new nodes to the cluster? or might this still work if you have already downloaded the parcels using Cloudera Manager? This will remain unchanged, as the paywall is only affecting accessing the binaries. The catch is if you have local repo set you can distribute parcels and expand cluster, but downloading parcels over internet will fail in this case.    What is the status of making all the code (such as Cloudera Manager) open source and available? I've not seen any news about that anymore. As far as I know you can still access source code from https://github.com/cloudera/ page only binaries can't be downloaded. The best way to get more details is to reach out Cloudera Sales Team.    The pricing for CDH is very high, probably a lot of "legacy" users cannot afford it, what is the best option if you now need to move away from CDH, use plain Apache Hadoop? or other database such as Clickhouse or AWS Athena? I would highly encourage you to reach out Cloudera Sales Team as you can get a better picture on pricing then. However you can still use Cloudera Trial software version without any issues.  ... View more

No, there is not any such feature. Basically this is more of a dependent feature of AD means AD server usually decides how many attempts a user did and use to lock the account for same for some time or until AD team unlock them.    Hope this make sense.  ... View more

This seems a problem with installation itself, I would suggest to reinstall the software.    Caused by: java.lang.ClassNotFoundException: scala.Function0 at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:418) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ... 7 more Error: A JNI error has occurred, please check your installation and try again ... View more

Yes, that's fine.  ... View more

@cuian01 What do you mean by maximum login retries? Are you saying you want to control how many times a AD user can attempt to login into CM UI and then locked himself after that?  ... View more

@SangramM The issue seems to be with the bucket name or path where you are trying to copy the data.  look at the exception this is not accepting the target path due to some special character.  Error: java.lang.IllegalArgumentException: Invalid bucket name (eca02696p9u987tcbb55e477t94r3599baaf2469d4a99a19f78t5eebc4) or object name (testing/sc2_scam/src_rcv_ts=2020-11-25 23%3A25%3A23/000000_0) Caused by: java.net.URISyntaxException: Illegal character in path at index 109: gs://eca02696p9u987tcbb55e477t94r3599baaf2469d4a99a19f78t5eebc4/testing/sc2_scam/src_rcv_ts=2020-11-25 23%3A25%3A23/000000_0 So I would suggest you to rectify the path name.  This general thread might help you in terms of syntaxes: https://stackoverflow.com/questions/749709/how-to-deal-with-the-urisyntaxexception ... View more