|| at Apr 4, 2014 at 2:43 pm
Thanks to everyone that helped me overcome these problems.
I was able to complete installation of C5 with the correct installer.
Based on my experience, here are a few recommendations that can greatly
improve installation experience.
- The version number does not appear anywhere until you finish
installation. It is not in the installer file name, nor in the initial
notice shown. You will only know the actual version number "after"
installation is completed. Even in the initial CM Welcome screen, when
it asks you which edition you want to deploy, the version number is not
displayed. The version number should be displayed more prominently.
- The installer should detect compatible version of the host OS and
issue a warning if not one of the supported versions.
- The installer should detect host name resolution and reverse lookup
problems and warn the user. This would be similar to how it warns you
- The installer should also inform you of where the uninstaller resides,
in case installation fails so you know how to start over.
On Thursday, April 3, 2014 7:30:18 PM UTC-4, Rajat Goel wrote:
Firstly, I wanted to apologize for the frustrating experience. Thanks to
your feedback, we realized that our web link was incorrectly pointing to
the previous Cloudera Manager release. We have addressed the problem and
fixed the link to point to the correct location. We are also taking steps
to make sure this does not happen in the future. Please let us know if you
run into other issues.
On Thu, Apr 3, 2014 at 2:36 PM, asoto <[email protected]
The email I received from Cloudera with Subject "Cloudera Enterprise GA
Today – Thank You" has this link:http://app.go.cloudera.com/e/er?s=1465054361&lid=1108&elq=83ab368dffb4413dbb5f96a28ede6508
which takes me to a download page where I select "Download Cloudera
Express" which in turn, gives me this link:http://app.go.cloudera.com/e/er?s=1465054361&lid=11418&elq=00000000000000000000000000000000
Somebody should check these links in case they resolve to the wrong
version. The result of following all above links is:
Version: Cloudera Enterprise Trial 4.8.2 (#101 built by jenkins on
20140226-1855 git: 8609801079d228f2440a493a3880ab68cad0524b)
I will try tomorrow the new link you provided.
On Thursday, April 3, 2014 5:24:26 PM UTC-4, Darren Lo wrote:
Can you make sure you are downloading the Cloudera Manager installer bin
from the following URL?http://archive.cloudera.com/cm5/installer/latest/cloudera-
It sounds like you might have the Cloudera Manager 4 installer. You can
verify this by looking at the versions of the cloudera manager binaries
installed (if on rhel, yum info "cloudera*") or by looking in Support ->
About in the upper right of the Cloudera Manager web interface. You may
need to exit a wizard before this will appear as an option (click the
Cloudera Manager logo).
On Thu, Apr 3, 2014 at 2:10 PM, asoto wrote:
This has been very frustrating experience.
1. I have now deleted the old parcels from /opt/cloudera/parcel-
2. Deleted the default cluster.
3. Now there are no clusters not parcels.
4. Creating a new cluster
5. The only choice is: CDH-4.6.0-1.cdh4.6.0.p0.26
6. Provide custom repository URL: http://archive.cloudera.com/c
7. Click Add button and nothing happens.
8. Remove the trailing slash from URL: http://archive.cloudera.com/
9. Click Add
10. Get error dialog with message: Unknown Distro suffix: wheezy
What is going on? Is it really this difficult to test is in a freshly
On Thursday, April 3, 2014 4:56:26 PM UTC-4, Omar Alrubaiyan wrote:
Try clicking on the "Check for new Parcels" button on the parcels
page. Also look in the CM logs for any errors regarding parcels.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]