FAQ
Hello:

I am trying to evaluate Cloudera 5 Enterprise. After many troubles I
managed to install CM, and finally I see some downloaded parcels. However,
the versions of the parcels seem like are from version 4. Here they are:

CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
IMPALA 1.2.4-1.p0.110 Activated


I expected versions to be 5, not 4. Is this correct?

In the configuration settings I noticed this Remote Parcel Repository URLs:

http://archive.cloudera.com/cdh4/parcels/latest/


Which refers to version 4, so I changed to:

http://archive.cloudera.com/cdh5/parcels/latest/


But this had no effect, so still my parcels are stuck in version 4.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

Search Discussions

  • Omar Alrubaiyan at Apr 3, 2014 at 8:56 pm
    Hi,

    Try clicking on the "Check for new Parcels" button on the parcels page.
    Also look in the CM logs for any errors regarding parcels.

    On Thu, Apr 3, 2014 at 1:32 PM, asoto wrote:

    Hello:

    I am trying to evaluate Cloudera 5 Enterprise. After many troubles I
    managed to install CM, and finally I see some downloaded parcels. However,
    the versions of the parcels seem like are from version 4. Here they are:

    CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
    SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
    IMPALA 1.2.4-1.p0.110 Activated


    I expected versions to be 5, not 4. Is this correct?

    In the configuration settings I noticed this Remote Parcel Repository URLs:

    http://archive.cloudera.com/cdh4/parcels/latest/


    Which refers to version 4, so I changed to:

    http://archive.cloudera.com/cdh5/parcels/latest/


    But this had no effect, so still my parcels are stuck in version 4.

    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].
  • Asoto at Apr 3, 2014 at 9:10 pm
    This has been very frustrating experience.

        1. I have now deleted the old parcels from /opt/cloudera/parcel-repo.
        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/cdh5/parcels/latest/
        7. Click Add button and nothing happens.
        8. Remove the trailing slash from URL:
        http://archive.cloudera.com/cdh5/parcels/latest
        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
    created VM?

    On Thursday, April 3, 2014 4:56:26 PM UTC-4, Omar Alrubaiyan wrote:

    Hi,

    Try clicking on the "Check for new Parcels" button on the parcels page.
    Also look in the CM logs for any errors regarding parcels.


    On Thu, Apr 3, 2014 at 1:32 PM, asoto <[email protected] <javascript:>>wrote:
    Hello:

    I am trying to evaluate Cloudera 5 Enterprise. After many troubles I
    managed to install CM, and finally I see some downloaded parcels. However,
    the versions of the parcels seem like are from version 4. Here they are:

    CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
    SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
    IMPALA 1.2.4-1.p0.110 Activated


    I expected versions to be 5, not 4. Is this correct?

    In the configuration settings I noticed this Remote Parcel Repository
    URLs:

    http://archive.cloudera.com/cdh4/parcels/latest/


    Which refers to version 4, so I changed to:

    http://archive.cloudera.com/cdh5/parcels/latest/<http://www.google.com/url?q=http%3A%2F%2Farchive.cloudera.com%2Fcdh5%2Fparcels%2Flatest%2F&sa=D&sntz=1&usg=AFQjCNEG1xlTFSSiJSkTUlZhoqZPfl2HmA>


    But this had no effect, so still my parcels are stuck in version 4.

    To unsubscribe from this group and stop receiving emails from it, send
    an email to [email protected] <javascript:>.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Darren Lo at Apr 3, 2014 at 9:24 pm
    Hi Asoto,

    Can you make sure you are downloading the Cloudera Manager installer bin
    from the following URL?
    http://archive.cloudera.com/cm5/installer/latest/cloudera-manager-installer.bin

    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).

    Thanks,
    Darren

    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-repo.
    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/
    cdh5/parcels/latest/
    7. Click Add button and nothing happens.
    8. Remove the trailing slash from URL: http://archive.cloudera.com/
    cdh5/parcels/latest
    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
    created VM?

    On Thursday, April 3, 2014 4:56:26 PM UTC-4, Omar Alrubaiyan wrote:

    Hi,

    Try clicking on the "Check for new Parcels" button on the parcels page.
    Also look in the CM logs for any errors regarding parcels.

    On Thu, Apr 3, 2014 at 1:32 PM, asoto wrote:

    Hello:

    I am trying to evaluate Cloudera 5 Enterprise. After many troubles I
    managed to install CM, and finally I see some downloaded parcels. However,
    the versions of the parcels seem like are from version 4. Here they are:

    CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
    SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
    IMPALA 1.2.4-1.p0.110 Activated


    I expected versions to be 5, not 4. Is this correct?

    In the configuration settings I noticed this Remote Parcel Repository
    URLs:

    http://archive.cloudera.com/cdh4/parcels/latest/


    Which refers to version 4, so I changed to:

    http://archive.cloudera.com/cdh5/parcels/latest/<http://www.google.com/url?q=http%3A%2F%2Farchive.cloudera.com%2Fcdh5%2Fparcels%2Flatest%2F&sa=D&sntz=1&usg=AFQjCNEG1xlTFSSiJSkTUlZhoqZPfl2HmA>


    But this had no effect, so still my parcels are stuck in version 4.

    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].
  • Asoto at Apr 3, 2014 at 9:36 pm
    Darren:

    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.

    Thanks
    On Thursday, April 3, 2014 5:24:26 PM UTC-4, Darren Lo wrote:

    Hi Asoto,

    Can you make sure you are downloading the Cloudera Manager installer bin
    from the following URL?

    http://archive.cloudera.com/cm5/installer/latest/cloudera-manager-installer.bin

    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).

    Thanks,
    Darren


    On Thu, Apr 3, 2014 at 2:10 PM, asoto <[email protected] <javascript:>>wrote:
    This has been very frustrating experience.

    1. I have now deleted the old parcels from /opt/cloudera/parcel-repo.
    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/
    cdh5/parcels/latest/
    7. Click Add button and nothing happens.
    8. Remove the trailing slash from URL: http://archive.cloudera.com/
    cdh5/parcels/latest
    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
    created VM?

    On Thursday, April 3, 2014 4:56:26 PM UTC-4, Omar Alrubaiyan wrote:

    Hi,

    Try clicking on the "Check for new Parcels" button on the parcels page.
    Also look in the CM logs for any errors regarding parcels.

    On Thu, Apr 3, 2014 at 1:32 PM, asoto wrote:

    Hello:

    I am trying to evaluate Cloudera 5 Enterprise. After many troubles I
    managed to install CM, and finally I see some downloaded parcels. However,
    the versions of the parcels seem like are from version 4. Here they are:

    CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
    SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
    IMPALA 1.2.4-1.p0.110 Activated


    I expected versions to be 5, not 4. Is this correct?

    In the configuration settings I noticed this Remote Parcel Repository
    URLs:

    http://archive.cloudera.com/cdh4/parcels/latest/


    Which refers to version 4, so I changed to:

    http://archive.cloudera.com/cdh5/parcels/latest/<http://www.google.com/url?q=http%3A%2F%2Farchive.cloudera.com%2Fcdh5%2Fparcels%2Flatest%2F&sa=D&sntz=1&usg=AFQjCNEG1xlTFSSiJSkTUlZhoqZPfl2HmA>


    But this had no effect, so still my parcels are stuck in version 4.

    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] <javascript:>.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Rajat Goel at Apr 3, 2014 at 11:30 pm
    Hi Asoto,

    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.

    Thanks,
    -Rajat.

    On Thu, Apr 3, 2014 at 2:36 PM, asoto wrote:

    Darren:

    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.

    Thanks
    On Thursday, April 3, 2014 5:24:26 PM UTC-4, Darren Lo wrote:

    Hi Asoto,

    Can you make sure you are downloading the Cloudera Manager installer bin
    from the following URL?
    http://archive.cloudera.com/cm5/installer/latest/cloudera-
    manager-installer.bin

    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).

    Thanks,
    Darren

    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-
    repo.
    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
    dh5/parcels/latest/
    7. Click Add button and nothing happens.
    8. Remove the trailing slash from URL: http://archive.cloudera.com/c
    dh5/parcels/latest
    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
    created VM?

    On Thursday, April 3, 2014 4:56:26 PM UTC-4, Omar Alrubaiyan wrote:

    Hi,

    Try clicking on the "Check for new Parcels" button on the parcels page.
    Also look in the CM logs for any errors regarding parcels.

    On Thu, Apr 3, 2014 at 1:32 PM, asoto wrote:

    Hello:

    I am trying to evaluate Cloudera 5 Enterprise. After many troubles I
    managed to install CM, and finally I see some downloaded parcels. However,
    the versions of the parcels seem like are from version 4. Here they are:

    CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
    SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
    IMPALA 1.2.4-1.p0.110 Activated


    I expected versions to be 5, not 4. Is this correct?

    In the configuration settings I noticed this Remote Parcel Repository
    URLs:

    http://archive.cloudera.com/cdh4/parcels/latest/


    Which refers to version 4, so I changed to:

    http://archive.cloudera.com/cdh5/parcels/latest/<http://www.google.com/url?q=http%3A%2F%2Farchive.cloudera.com%2Fcdh5%2Fparcels%2Flatest%2F&sa=D&sntz=1&usg=AFQjCNEG1xlTFSSiJSkTUlZhoqZPfl2HmA>


    But this had no effect, so still my parcels are stuck in version 4.

    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].
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Asoto 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
        about SELinux.
        - The installer should also inform you of where the uninstaller resides,
        in case installation fails so you know how to start over.

    Thanks again.
    On Thursday, April 3, 2014 7:30:18 PM UTC-4, Rajat Goel wrote:

    Hi Asoto,

    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.

    Thanks,
    -Rajat.


    On Thu, Apr 3, 2014 at 2:36 PM, asoto <[email protected] <javascript:>>wrote:
    Darren:

    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.

    Thanks
    On Thursday, April 3, 2014 5:24:26 PM UTC-4, Darren Lo wrote:

    Hi Asoto,

    Can you make sure you are downloading the Cloudera Manager installer bin
    from the following URL?
    http://archive.cloudera.com/cm5/installer/latest/cloudera-
    manager-installer.bin

    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).

    Thanks,
    Darren

    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-
    repo.
    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
    dh5/parcels/latest/
    7. Click Add button and nothing happens.
    8. Remove the trailing slash from URL: http://archive.cloudera.com/
    cdh5/parcels/latest<http://archive.cloudera.com/cdh5/parcels/latest/>
    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
    created VM?

    On Thursday, April 3, 2014 4:56:26 PM UTC-4, Omar Alrubaiyan wrote:

    Hi,

    Try clicking on the "Check for new Parcels" button on the parcels
    page. Also look in the CM logs for any errors regarding parcels.

    On Thu, Apr 3, 2014 at 1:32 PM, asoto wrote:

    Hello:

    I am trying to evaluate Cloudera 5 Enterprise. After many troubles
    I managed to install CM, and finally I see some downloaded parcels.
    However, the versions of the parcels seem like are from version 4. Here
    they are:

    CDH 4.6.0-1.cdh4.6.0.p0.26 Activated
    SOLR 1.2.0-1.cdh4.5.0.p0.4 Activated
    IMPALA 1.2.4-1.p0.110 Activated


    I expected versions to be 5, not 4. Is this correct?

    In the configuration settings I noticed this Remote Parcel Repository
    URLs:

    http://archive.cloudera.com/cdh4/parcels/latest/


    Which refers to version 4, so I changed to:

    http://archive.cloudera.com/cdh5/parcels/latest/<http://www.google.com/url?q=http%3A%2F%2Farchive.cloudera.com%2Fcdh5%2Fparcels%2Flatest%2F&sa=D&sntz=1&usg=AFQjCNEG1xlTFSSiJSkTUlZhoqZPfl2HmA>


    But this had no effect, so still my parcels are stuck in version 4.

    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] <javascript:>.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Todd Grayson at Apr 4, 2014 at 6:22 pm
    Asoto,

    I have filed a Jira against Cloudera Manager installer with these
    points. Thank you very much for your work on this.

    Todd
    On 4/4/14 8:43 AM, asoto wrote:

    * 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 about SELinux.
    * The installer should also inform you of where the uninstaller
    resides, in case installation fails so you know how to start over.

    --
    Todd Grayson
    Cloudera Support
    Customer Operations Engineering
    [email protected]

    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedApr 3, '14 at 8:32p
activeApr 4, '14 at 6:22p
posts8
users5
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2023 Grokbase