I'm trying to log into to Cloudera Manager in cloudera-quickstart-vm-5.8.0-0-vmware with the specified log in details ( Username: cloudera, Password: cloudera) but getting the error: Incorrect username or password.
Does the user name and the password had changed?
Created 11-01-2016 03:25 PM
Thank you for reaching out on this.
I looked at the documentation for the quickstart VMs, and it states the username and password for CM in quickstart are "cloudera", as you said.
Intrigued, I decided to fire up the VM on my end, and sure enough, those credentials don't work. I instead tried using the default CM login specified in the instructions for a standard path B install, and viola, it worked!
try using the following login for CM in quickstart:
Let me know if that works, and in the mean-time, I'll look into getting that documentation updated. Thank you for bringing this to my attention. 🙂
Created 11-01-2016 06:21 PM
I succeeded to log in with username and password admin.
But now I have another issue. As I saw, on some online videos, when I'm login into Cloudera Manager in the quickstart vm, all the components (such as HDFS) are already installed.
But when I'm login into cloudera manager I need to install all the components by myself ("Specify hosts for your CDH cluster installation").
Shouldn't it be already installed in the Cloudera Quickstart VM?
Thank you for your help!
Created on 11-03-2016 11:10 AM - last edited on 11-03-2016 01:06 PM by cjervis
Glad that login worked. As far as the services go, they should indeed already be installed. My thought is it could be an issue with the particular VM you received. Either it was received from a different source, or it didn't download completely. Could you perhaps provide the link you originally got the VM from?
Here’s what I recommend. Try re-downloading* the VM, verify it completely downloaded, and try loading it, still using the "admin" user and pass login. I downloaded the quickstart VM from the link below*, and I've verified that it works. (all services installed)
Let me know if this works.
*some links for your convenience
Community Knowledge article with quickstart install tips (outdated CDH version, but steps are good)
Created on 11-03-2016 02:58 PM - edited 11-03-2016 02:59 PM
I downloaded it from:
and choose VMWare as a platfrom
Created 11-07-2016 02:59 PM
I re-downloaded th VM from this link - http://www.cloudera.com/downloads/quickstart_vms/5-8.html
After unzipping it (with 7-Zip), this is the content of the folder:
Is there a missing file?
After I logged into Cloudera Manager in the VM (with "admin"), I was again asked to install everything
Created 11-07-2016 03:48 PM
All of the files are there. Have you used the launch script for this VM?
These guys right here.
If so, did you you use the shortcut for express, or the enterprise trial?
Created 11-07-2016 04:16 PM
but then I was asked to run in the terminal -
sudo /home/cloudera/cloudera-manager --force
(and more precisely -
sudo /home/cloudera/cloudera-manager --express --force)
Created 11-08-2016 12:05 PM
Okay, from this point, it would seem that the script could be having trouble setting up and starting the services. Could you try re-running the script with the method you described (sudo /home/cloudera/cloudera-manager --express --force) and post the output from it? We'll comb through it for any possible errors. Meanwhile, I'm working on my end to replicate this.
Created 11-08-2016 03:09 PM
I re-run the script and got this output:
[cloudera@quickstart ~]$ sudo /home/cloudera/cloudera-manager --express --force [QuickStart] Shutting down CDH services via init scripts... kafka-server: unrecognized service JMX enabled by default Using config: /etc/zookeeper/conf/zoo.cfg [QuickStart] Disabling CDH services on boot... error reading information on service kafka-server: No such file or directory [QuickStart] Starting Cloudera Manager server... [QuickStart] Waiting for Cloudera Manager API... [QuickStart] Starting Cloudera Manager agent... [QuickStart] Configuring deployment... [QuickStart] Deploying client configuration... [QuickStart] Starting Cloudera Management Service... [QuickStart] Enabling Cloudera Manager daemons on boot... ________________________________________________________________________________ Success! You can now log into Cloudera Manager from the QuickStart VM's browser: http://quickstart.cloudera:7180 Username: cloudera Password: cloudera [cloudera@quickstart ~]$
Created 11-09-2016 04:05 PM
Are the errors regarding kafka-server have something to do with that the cluster isn't installed?
What can I do to fix this?
Created 11-11-2016 01:07 AM
Created 11-13-2016 06:19 PM
On the desktop of VM I have also the following items:
Migrate to Parcels
Should I use one of them?
Created 11-14-2016 09:59 AM
You should'nt have to use the Kerberos or Parcels links.
I'm currectly working on some additional troubleshooting steps. Thank you for your patience.
Created 11-14-2016 10:08 AM
Created 11-16-2016 06:11 AM
I'm trying to install the cluster by myself.
Could you help me with the configurations?
Created 11-16-2016 08:22 AM
I'm still researching the issue, but in the meantime, I can definitely help you with the cluster setup. The selections on that first screen look fine. Feel free to post screen shots of anything else you have questions for.
Created on 11-17-2016 09:16 AM - edited 11-17-2016 09:21 AM
So, after the Cluster Installation, I got this screen:
What does the warning about the Parcels mean?
Should I change the configuration of the cluster installation to "Use Packages" instead of "Use Parcels"?
Created 11-17-2016 11:35 AM
Interesting. It seems like your VM already had the packages installed for the services, even though Cloudera Manager didn't recognize them.
First, try running the "Migrate to Parcels" script on the desktop. That should stop the services, uninstall them, and re-deploy the client configuration. Just ran the script myself, and the output should Idealy look like this.
Feel free to share a screenshot of your console output for this
If that doesn't work, try reinstalling CM with packages instead of parcels. To do this, I would recommend deleting the current VM and re-extracting the zip you download, just so you can start fresh.
Let me know if it throws any warnings this time around or if you have any questions along the way. (screenshots are welcome, as always) Thank you for being so patient while we figure this out.
Also, here's some fun reading to get a better understanding of Parcels, if you're so inclined. 🙂
Created 11-17-2016 04:18 PM
I deleted the VM (again),
re-extracted the zip (again),
in the terminal in the VM I run the script - sudo /home/cloudera/cloudera-manager --express --force (again),
and this time I could log into Cloudera Manager with the credentials 'cloudera' and the cluster was already installed!
Created 03-19-2023 01:05 AM
I just want to say thanks a lot, is 2023 and it still works