The user/pass cloudera doesn't work in mysql, but even if it would worked it won't solve my problem.   The thing is, why suddently the access to cm/hue's mysql stop working? I mean 'cm'@'localhost' failed and I had to use root user. Now with HUE I can't use Hue user with the defined password.   In order to continue using cloudera VM I have created another VM and works well.   Thanks ... View more

Now Hue doen't work... another password problem:   OperationalError: (1045, "Access denied for user 'hue'@'localhost' (using password: YES)")   I don't get it, I didn't change the password after the first Hue login.   The way to get the password is (if I am right):   /var/run/cloudera-scm-agent/process/163-hue-HUE_SERVER/hue.ini /var/run/cloudera-scm-agent/process/163-hue-HUE_SERVER/altscript.sh sec-5-password /var/run/cloudera-scm-agent/process/163-hue-HUE_SERVER/creds.localjceks" "${ALIAS}   creds.localjceks is a binary file, so I don't know what password is set in order to change hue password in linux account (I'm not sure if would fix the problem).   Cloudera Manager can't start Hue server because this error, how can I fix Hue?   Thanks   PD: There is no need for password as I can test trying logging with hue user with mysql... so I tried to comment password line (previous 2º item) and still it is setting the pass. n-hue-HUE_SERVER is created when startint Hue server... so I need to find the original config. ... View more

Yeah, I had the same problem and I found the culprit in this log, thanks.   When trying to start cloudera-scm-server it started correctly (apparently, it says OK in green), but it wasn't started. In the log /var/log/cloudera-scm-server/cloudera-scm-server.log I could see this error:   java.sql.SQLException: Access denied for user 'cm'@'localhost' (using password: YES) I was working with the VM with no problem days before and I didn't change anything. Why it just stopped working? I don't know. But with this post I tried root user instead of cm (changing /etc/cloudera-scm-server/db.properties file) and it worked! 🙂   After changing the db.properties file I had to restart the services doing this: sudo service cloudera-scm-server restart sudo service cloudera-scm-agent restart sudo /home/cloudera/cloudera-manager --force --express   Hope it helps!     ... View more

I think I fixed the problem, I don't know exactly how.   The thing is, I really have a problem with Hive's performance, the querys are running too slow.    Show tables; takes 64-67 seconds the first time I execute the sentence with Hive just started. The next times it takes less than a second. But, trying to show 16k lines from customers takes too much and when running for 3:30h it gives the lock error (it's really a timeout, there are no locks).   I have tried restarting the services according to Showing Big Data Value (previous to exercise 2): HDFS, Hive, Hue and Impala, in the correct order with no luck.   But as last option I tried restarting all Cloudera Quickstart services and now Hive works OK!   Maybe YARN, Zookeeper, Ozzie, or some other service is needed in order to Hive gain performance?   Well, at least now I can finish exercise 2... I hope Hive doesn't bring me more problems.   Regards ... View more

Hello,   First make sure you configure the VM with a minimun of 8GB of RAM and 2 CPU cores.   Second, don't try to start all services. Start only the services you really need. In getting started page (http://quickstart.cloudera/#/tutorial/getting_started) you only need to start 5 services.   If you still have the same problem copy&paste here the health warning in order we can help you.   I had this problem some days ago, and I fixed it by stopping all services and starting only the ones I need to do the exercice. It this doesn't work try restarting the VM (Linux).   Regards ... View more

I really don't understand what's going on. In case I broke some config, I have reset the VM.   Anyone can test this SQL sentence with Hive in Cloudera Quick Start VM 5.12 (VirtualBox format)?   select * from customers;     These are the steps I just have done: Download Cloudera Quick Start VM 5.12 from here (VirtualBox format): https://www.cloudera.com/downloads/quickstart_vms/5-12.html Configure the VM in order to have 2 CPU processes and 12GB of RAM (required to launch Cloudera Express). Launch the VM. Launch Cloudera Express with no problems. In Cloudera Manager I launch with no problem: HDFS, Hive, HUE, Impala and YARN, but they have some warnings. Hive says "1 is less than the recommended minimum of 4." regarding Spark Executor Cores in Hive and HiveServer2. In Linux terminal I launch the sqoop import-all-tables indicated in Tutorial Exercise 1. In Impala I execute invalidate metadata; and select * from customers; with no problems, and returning all the records of the table in less than 1 second. In Hive I execute select * from customers; and the query keeps running with no end (more than 30 min at least).   In Hive's log ("Show Logs" icon in Hue) says:   INFO : Compiling command(queryId=hive_20180215091515_596862e0-3749-4b30-aa1c-4bdd4f7c76a8): select * from customers INFO : Semantic Analysis Completed INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:customers.customer_id, type:int, comment:null), FieldSchema(name:customers.customer_fname, type:string, comment:null), FieldSchema(name:customers.customer_lname, type:string, comment:null), FieldSchema(name:customers.customer_email, type:string, comment:null), FieldSchema(name:customers.customer_password, type:string, comment:null), FieldSchema(name:customers.customer_street, type:string, comment:null), FieldSchema(name:customers.customer_city, type:string, comment:null), FieldSchema(name:customers.customer_state, type:string, comment:null), FieldSchema(name:customers.customer_zipcode, type:string, comment:null)], properties:null) INFO : Completed compiling command(queryId=hive_20180215091515_596862e0-3749-4b30-aa1c-4bdd4f7c76a8); Time taken: 0.05 seconds     So, what's happening? All seems ok but Hive doesn't return any record.     Maybe this info can help to identify the problem:   The other day I executed the query It took 3:30h and gave the next error:   Error while processing statement: FAILED: Error in acquiring locks: Locks on the underlying objects cannot be acquired. retry after some time     Now, when I execute the query "SHOW LOCKS customers;" it returns "Done. 0 results." but it takes 57 seconds. Is this normal? Maybe there is some performance problem with Hive?   I tested also to change the Spark Executor Cores in Hive from 1 to 4 (in order to avoid the warning), to redeploy and restart Hive, Impala and Hue... but it didn't fix the problem.   Can anyone help me with this problem?   At least saying something like "no one use VM in Virtualbox format, use Docker/VMWare/KVM instead" or "I have no problem with Hive using Cloudera Quick Start VM 5.12 with VirtualBox format".   Thanks in advance!   ... View more