Hi @alvaro_soares,   If you have maked changes in the configuration bashrc file(~/.bashrc), you need to use the next command: source ~/.bashrc     Regards, Manu.   ... View more

Hi @salve08,   Are you accesing to the correct port? Have you tried https ?   Regards, Manu. ... View more

Hi @mmm286,   It looks like you have some problems:   1) report: Access denied for user root. Superuser privilege is required that indicates your os user "root" is not the superuser of HDFS (root is just the "superuser" of the operating system). Try to do the same as user "hdfs" (which is by default the hdfs superuser), as root do:   su - hdfs hdfs dfsadmin -report Basically, the HDFS superuser is the user, under which account the Namenode is started.   2)Safe mode is ON   In VM there is only one file system. Login as root Try: df -sh (one of the mount points will show ~100%) du -sh / (it will list size of each of the directory) If any directory other than your namenode and datanode directories taking up too much space, you can start cleaning up Also you can run hadoop fs -du -s -h /user/hadoop (to see usage of the directories)   Try to see Namenode log for more information when you start the service.   Regards, Manu. ... View more

Hi, @TomasTF   Have your system the same timezone that your CDH?   Regards, Manu. ... View more

Hi @srt_thomas,   Try to see the configuration Hue log. You can go to "user tab" on right top and "Hue Administration", are there any error?   Regards, Manu. ... View more

Hi @TomasTF,   One question:    - How do you executhe that queries? With wich client?   Have you try to ctrl+R in your cloudera manager (tab impala --> queries) in your browser.   Regards, Manu. ... View more

Hi @grhuang,   Only need 2 things: 1) Change SoftwareClock in all hosts (nodes):     timedatectl set-timezone Europe/Madrid (in my case) 2) Restart Cloudera manager server:      sudo service cloudera-scm-server restart   Regards, Manu. ... View more

Exit code 143 is related to Memory issues. Your default Mapper/reducer memory setting may not be sufficient to run the large data set. Try setting up higher AM, MAP and REDUCER memory when a large yarn job is invoked.   Regards,  Manu. ... View more