The original error has nothing to do with connecting to Hue. It was an error interactions between Impala and the other daemons it needs to complete the query. Just use the link in the email or on the guidance page to connect to Hue. The public IP should work just fine. If it doesn't, you are experiencing a separate issue and would need to provide more information.     ... View more

Thanks for letting us know - glad you got it working! Is there are an article or blog post with more background on the bug you chould share? ... View more

I've had another VMWare Fusion user confirm that the latest (5.4.0-0) release works well for them, and they actually informed me that those lines we recently added to the .vmx file have been in use for a long time in Cloudera's courses without incident, so I don't think it's worth messing with those settings after all.   My only other suggestion would be to see if there is any kind of error message you can get from Fusion about why the VM is failing to start. It would see from the following article that you can enable some diagnostic information collection - perhaps the resulting files will contain a more useful error message?   http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003894 ... View more

I'm going to look into this, but while I do, here's something you can try if you'd like. These lines were added to the .vmx configuration file recently, and that's the only recent change that I can think of that might affect Fusion specifically. You could try removing them from the file and tryin again. (They're only added as a convenience to hide some annoying reminders and prompts).   tools.remindinstall="FALSE" tools.upgrade.policy="manual" Let me know if that does or doesn't work for you if you can try it out, otherwise I'll post back as soon as I can with more information. ... View more

Can you confirm in Cloudera Manager that the HDFS service is running and healthy? If the service is marked in any color other than green, there should be a little warning icon that you can click on to get any information about what may be wrong.   If the service is healthy, can you tell me what happens when you run "hadoop fs -ls /user/examples/sqoop_import_order_items.avsc" from the command line on a machine in your cluster? ... View more

I'm afraid I'm not very familiar with R and running it against Hadoop. My first thought is that perhaps the program that creates the files and the program that looks for the files are running as different users? /user/cloudera is the default working directory for the cloudera user, but other users will default to other directories. e.g. if 'root' asks for a file called '0', unless there's an absolute path with it, it means /user/root/0. Is it possible these files exist under a different user's home directory? ... View more

To answer Morgan's question, port 8020 is the HDFS NameNode, port 8021 is the JobTracker in MR1, which is where you would have submitted jobs in CDH 4. It can still be used in CDH 5, but as it is not the default, you'll need to switch around some configuration and services (and understand that the rest of the tutorial may not work exactly as expected because of the switch - I'd suggest perhaps starting with a fresh copy of the tutorial to be sure everything in the tutorial will work and not conflict with what you've been doing in R). ... View more

After reviewing the blog post, I noticed that it is written for the CDH 4.1.1 VM. I'm afraid there have been a number of changes since then that might be complicating things. The primary change, and the one that I think is complicating Sqoop for you, is the in CDH 4 we recommend MR1 for production, whereas in CDH 5 YARN has stabilized and we now recommend MR2 for production because of the superior resource management.   I believe the following line is responsible for setting up your environment such that Sqoop is trying to use MR1 when it is not running: ln -s /etc/default/hadoop-0.20-mapreduce /etc/profile.d/hadoop.sh You could either try getting rid of that symlink and anything else that's telling the system to use MR1, or you could stop YARN / MR2 and use MR1 instead. I'll try post some instructions for doing the latter shortly...   ... View more

>> In the very first tutorial on cloudera, it reads "You should first log in to the Master Node of your cluster using SSH - you can get the credentials using the instructions on Your Cloudera Cluster. "   It's a little confusing whether you're running these commands on your host machine, or on the VM. If you're reading the tutorial hosted on a website somewhere, it's written with you running this on a fully-distributed cluster in mind and SSH'ing in to the machine. There's a modified copy hosted on the VM itself (just go to localhost in the web browser in the VM, or on your host as port-forwarding should work for VirtualBox) that (in my copy at least) just tells you to click on the terminal icon on the VM's desktop and enter commands there. Which version of the VM are you using and where do you see that text? It should be possible to SSH into the VM, and even run these commands from your host machine but doing so requires a lot of network configuration to be set up correctly - it won't be set up that way by default and it can be complicated to get it working consistently on different hosts - which is why I recommend just using the terminal on the VM's desktop.   The root cause of your connection refused error problem appears to be that Sqoop is trying to use MR1. The VM is set up to use MR2 / YARN by default, so that is probably why MR1 is not running and you can't connect. Cloudera supports running both MR1 and MR2, but you can't have a machine configured as a client to both at the same time. When I run this on my copy of the VM (and in all recent versions) Sqoop is definitely using MR2 / YARN. Have you change any other configurations before running Sqoop? Is it possible you've got Sqoop installed on your host machine and it's configured differently than Sqoop in the VM? ... View more

I hear you - I prefer .tar.gz myself but we found that with most formats (.tar.gz included) the ability to extract large archives (>2GB) was very inconsistent between different tools and it caused a lot of confusion among users about what the problem actually was. ... View more

You beat me to it! I was just downloading the file to confirm the integrity of the file. I downloaded cloudera-quickstart-vm-4.7.0-0-vmware.7z, the SHA-1 checksum matched, and I was able to extract it. If you're not doing so already, I recommend using a download manager for large files (I use DownThemAll! for Firefox) - it will deal with network failures more gracefully than the one built-in to most browsers and you're less likely to have a corrupted or interrupted download. ... View more

Thanks again for reporting the issue and sharing your workaround with other users. Just wanted to let you know that as of noon PT yesterday, now deployments should not have this problem. You should be able to access MySQL via the public IP from any of the instances now, and the tutorial now gives you a working command for the Sqoop import and Hive metadata. ... View more

Thanks for letting us know about this - this is an error in a recent update to the tutorial. Those commands should be using the hostname, rather than the IP address. So I'd suggest trying 'f6129-cldramaster-01' for the NameNode instead of 216.121.116.82. We'll change the future MySQL setup to allow access via IP address as well, but it seems you found a work-around for that. The reason for the second failure is that the command is trying to use the public interface instead of the private interface.   GoGrid machines typically have 2 network interfaces - one that is publicly accessible, and one that is private (but has higher performance). 216.* points to one of the public IP addresses, but some of the services that are not intended to be accessed directly only listen on the private interface (Hue and CM listen on the public interfaces as well). So again, using the hostname there should work, or the IP address of the internal interface (eth1). We'll get the tutorial content and MySQL config updated shortly... Please post back if you run into additional issues with the current tutorial and I'll try provide workarounds... ... View more

FWIW, this should basically be the procedure to install and run from packages in the current QuickStart VM: REPO= http://archive-primary.cloudera.com/accumulo-c5/redhat/6/x86_64/cdh/cloudera-accumulo.repo (cd /etc/yum.repos.d && sudo wget ${REPO}) # install yum repository sudo yum install accumulo-* sudo service accumulo-master init # follow prompts for role in (cd /etc/init.d && ls accumulo\*); do sudo service ${role} start done ... View more

Hmm... The same server that hosts CM should also host Hue (on 8888, as you're trying) and a web server on port 80 with a "Guidance Page" with a link straight to Hue. Are you trying to connect to 8888 on the same IP as the one you can connect to Cloudera Manager on? If so, I'd be curious to know if when you look at the Hue service in CM and click on the Instances tab, if it shows the Hue server running on the host you're expecting. ... View more

Cloudera Manager is responsible for managing and monitoring Hue (among other things, of course). If you can log into Cloudera Manager the first screen you will see includes a list of all services. Hue's status will be shown with a red, yellow or green dot. You can click on the service, go to the processes tab, and see logs from stdout, stderr, and the actual "role log" (this is most likely the be what you want to see). What does it show as the status of Hue and do you see any errors in that log? ... View more