Hello,   If the Hue Kerberos Ticket Renewer does not start, check your KDC configuration and the ticket renewal property, maxrenewlife, for the hue/<hostname> and krbtgt principals to ensure they are renewable. If not, running the following commands on the KDC will enable renewable tickets for these principals:   kadmin.local: modprinc -maxrenewlife 90day krbtgt/MY.REALM kadmin.local: modprinc -maxrenewlife 90day +allow_renewable hue/my-hostname@MY.REALM Thanks! Laith ... View more

Hello,   I would check the Cloudera Manager Server log which may have a more helpful information of this failure (in /var/log/cloudera-scm-server/) from the time when the start command failed.    Thanks Laith ... View more

Hello DDreaner94,   Thanks for confirning that the docunmation works for you, and I agree with @mbigelow,  CDH itself isn't really doing the checking so much as relying on system time. The NTP check and Chrony check are doing by the Agent since there are some time sensitive components in the stack.   Please let us know if you have any other concers..   Have a nice day! Laith  ... View more

Hello DemonBY,   This IP is a translation for  archive.cloudera.com, would you please post the output of this command:   $ sudo ps ex | grep 151.101.36.167   Thanks! Laith ... View more

Hello there,   For internal networking, you can control the host names that is associated with the other servers IP addresses in /etc/hosts file.   Thanks Laith  ... View more

Hello Vihoop,   Thanks for your question.   /etc/hosts is not the only place to set/configure the hostnames of hosts. A valid public DNS record could be another resolver for your hosts in case you have defined your hosts' hostname with a public DNS provider (A or CNAME records). However, Linux systems usually resolve the hostname as per the order of the resolver in /etc/nsswitch.conf file.   There is a lot of standard DNS commands that exam your hostname resolution, like: dig, host, nslookup, whois, and many else..   Respectfully Laith ... View more

Hello Victor,   Thanks for your response!   As I can see, the problem is not within your AWS configurations, as you should be able to connect through the security group rules that you configured.   However, as you have a null output by running netstat one the server itself, that means your CM is not running or is not configured properly. You'd need to check the status of the service itself inside the server.   First, investigate if the server is running or not:   service cloudera-scm-server status   If it is not running, try to restart the service again, and wait for a minute or two so the service completely started:   service cloudera-scm-server restart   And while you attempt to login, its good idea to monitor the server log to see what is going on on the cluster level:   tail /var/log/cloudera-scm-server/cloudera-scm-server.log -f    Let me know if you need any help!   Thanks! Laith     ... View more

Hello,   Thanks for your question.   You’d need to identify if it is an AWS or CM issue. So first, run this command on the Cluster level (locally), to verify that you have port 7180 listens:     netstat -pltn | grep 7180   To check if it’s an AWS issue, check connectivity over the port 7180 from your end (remotely):     nc -v $YOUR_PUBLIC_HOST_NAME 7180   If it doesn’t pass, then check the security group rules of your AWS environment and make sure that you have allowed port 7180/tcp in AWS inbound security group rules. In fact, you'd need to allow all the related ports of CDH in the inbound rules (7180, 7182, 7183, and 7432).   Another point to consider, is your server (instance) firewall. Make sure it allows the access over the related port/s.   Else, I'd check the CM server log while you are trying to connect for more information.   These are a basic steps to start investigating, if you have any concerns or questions, please feel free to update this post!   Thanks! Laith Al Obaidy ... View more

Hello again, Vinay As it shown from the output of the executed commands, your system is not registered with RHN, so you won’t be able to download/update your system packages using the default repository.   If you haven’t started your RHEL evaluation yet, then do it here https://access.redhat.com/products/red-hat-enterprise-linux/evaluation   Also, make sure that your system has registered and subscribed, using these commands:   # subscription-manager register # subscription-manager subscribe   Then you can install your missing packages/dependencies.   If the problem still exist, I would suggest to check your subscription issue with Red Hat.   On the other hand, as a suggestion, you could try CentOS instead of RHEL, so you avoid the subscription issue, as CentOS is a free distribution of Linux.     Let me know if you need any help!   Thanks, Laith ... View more

Hello VinayRamu,   Sounds like your system is getting some sort of issue with your Red Hat Network (RHN) subscription/registration. Please check that you have an active entitlement assigned to your system/server.   To confirm, would you please issue the command below and post back the output here.   yum info cyrus-sasl-gssapi  &&  yum install cyrus-sasl-gssapi   Thanks!  Laith ... View more

Hello Igor,   To create a partition in Linux, you’d need to ‘fdisk’ it first. In your example, (sdb) is the disk, so you’d need to to create the partition (sdb1): fdisk /dev/sdb After that, you’d need to format the new partition into an ext4:   mkfs.ext4 /dev/sdb1 Make sure you are mount it correctly in /etc/fstab, just like I stated in my first response, ‘mount -a’ command is a good way to examine your fstab entries. In regards to the HDFS block size, the block division in HFDS is just logically built over the physical blocks of the ext4 filesystem; HDFS blocks are large compared to disk blocks, and the reason for this is to minimize the cost of seeks. If the block is large enough, the time it takes to transfer the data from the disk can be significantly longer than the time to seek to the start of the block. If there are any additional questions, please let me know. Thanks, Laith ... View more

Hello Igor!   You can start building your cluster using any of Cloudera CDH supported file systems; ext3, ext4 and XFS.  Avoid using  LVM partitioning method (which is the default partitioning method in CentOS6 and 7, but use the manual disk partitioning instead). And yes, the recommended option for mounting in /etc/fstab is just like you stated.   /dev/sdb1 /data1 ext4 defaults,noatime 0 For more information please take a look into this article.   https://www.cloudera.com/documentation/enterprise/5-6-x/topics/install_cdh_file_system.html   Thanks   Laith   ... View more