FAQ
I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

root@li339-83:~/cdh# file cloudera-manager-installer.bin
cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64, version
1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not
stripped
root@li339-83:~/cdh# uname -a
Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT 2013
x86_64 x86_64 x86_64 GNU/Linux
root@li339-83:~/cdh# sh cloudera-manager-installer.bin
cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
execute binary file
root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
root@li339-83:~/cdh#

Search Discussions

  • Philip Langdale at Jun 7, 2013 at 9:18 pm
    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil

    On 7 June 2013 14:14, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT 2013
    x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 7, 2013 at 9:20 pm
    Philip, Thanks for replying. I have done that already (but missed to post
    in my code)

    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26 cloudera-manager-installer.bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran <email...@gmail.com<javascript:>
    wrote:
    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT 2013
    x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 7, 2013 at 9:29 pm
    My OS Details:

    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Philip, Thanks for replying. I have done that already (but missed to post
    in my code)

    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil

    On 7 June 2013 14:14, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Philip Langdale at Jun 7, 2013 at 9:43 pm
    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04 installation. I
    note that you're using this on Linode and are running a Linode specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not giving you
    much to go on. You can always install without using the installer if you
    follow the "Path B" instructions in the installation guide - although I
    can't promise other programs will be able to run, given this problem.

    --phil

    On 7 June 2013 14:29, Lenin Raj Rajasekaran wrote:

    My OS Details:

    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Philip, Thanks for replying. I have done that already (but missed to post
    in my code)

    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26 cloudera-manager-installer.*
    *bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.**bin


    --phil

    On 7 June 2013 14:14, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.**bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.**bin: cloudera-manager-installer.**bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.**bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 8, 2013 at 6:36 am
    Hi Philip,

    According to this forum <https://forum.linode.com/viewtopic.php?t=7557%3E>,
    they say:

    Linode's kernels aren't modified; you can reproduce them using the mainline
    kernel source <http://www.kernel.org/> and the configuration file from
    /proc/config.gz, plus a quick edit to config.h to stick -linodeXX into the
    kernel version.
    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I couldn't
    locate it here<http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Free/latest/Cloudera-Manager-Free-Edition-Installation-Guide/cmfeig_topic_6_1.html>

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(
    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale wrote:

    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04 installation. I
    note that you're using this on Linode and are running a Linode specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not giving you
    much to go on. You can always install without using the installer if you
    follow the "Path B" instructions in the installation guide - although I
    can't promise other programs will be able to run, given this problem.

    --phil


    On 7 June 2013 14:29, Lenin Raj Rajasekaran <email...@gmail.com<javascript:>
    wrote:
    My OS Details:

    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#

    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed to
    post in my code)

    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26 cloudera-manager-installer.
    **bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.**bin


    --phil

    On 7 June 2013 14:14, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.**bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.**bin: cloudera-manager-installer.**bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.**bin
    root@li339-83:~/cdh#
  • bc Wong at Jun 8, 2013 at 6:41 am
    The path B doc is here:
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html

    What's the actual error when you run the installer bin? Seems that it
    exits without doing anything? (Exit code? Strace?) If you have X, it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using the
    mainline kernel source and the configuration file from /proc/config.gz, plus
    a quick edit to config.h to stick -linodeXX into the kernel version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(

    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale wrote:

    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04 installation. I
    note that you're using this on Linode and are running a Linode specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not giving you
    much to go on. You can always install without using the installer if you
    follow the "Path B" instructions in the installation guide - although I
    can't promise other programs will be able to run, given this problem.

    --phil

    On 7 June 2013 14:29, Lenin Raj Rajasekaran wrote:

    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil

    On 7 June 2013 14:14, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here and when I executed the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 8, 2013 at 6:53 am
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from dash
    yesterday). I am running via command line. I tried 3 different ways of
    executing the bin file. Doing ./ throw "No such file or directory error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute" error


    *root@li339-83:~/cdh# ll*
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26 cloudera-manager-installer.bin*
    *root@li339-83:~/cdh# ./cloudera-manager-installer.bin*
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    *root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin*
    *root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin*
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin: cannot
    execute binary file
    *root@li339-83:~/cdh# sh cloudera-manager-installer.bin*
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh#

    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:

    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html

    What's the actual error when you run the installer bin? Seems that it
    exits without doing anything? (Exit code? Strace?) If you have X, it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    <email...@gmail.com <javascript:>> wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using the
    mainline kernel source and the configuration file from /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(

    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale wrote:

    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04 installation.
    I
    note that you're using this on Linode and are running a Linode specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not giving
    you
    much to go on. You can always install without using the installer if
    you
    follow the "Path B" instructions in the installation guide - although I
    can't promise other programs will be able to run, given this problem.

    --phil

    On 7 June 2013 14:29, Lenin Raj Rajasekaran wrote:

    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil

    On 7 June 2013 14:14, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here and when I executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • bc Wong at Jun 8, 2013 at 7:26 am
    That installer bin is not a shell script. So the 3rd way would
    definitely not work. And since you're already root, sudo is not
    meaningful.

    The ENOENT is most likely due to missing runtime. What does `ldd
    cloudera-manager-installer.bin' say?

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:53 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from dash
    yesterday). I am running via command line. I tried 3 different ways of
    executing the bin file. Doing ./ throw "No such file or directory error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute" error


    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh# ./cloudera-manager-installer.bin
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin: cannot
    execute binary file

    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:

    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html

    What's the actual error when you run the installer bin? Seems that it
    exits without doing anything? (Exit code? Strace?) If you have X, it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using the
    mainline kernel source and the configuration file from /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(

    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale wrote:

    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04 installation.
    I
    note that you're using this on Linode and are running a Linode specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not giving
    you
    much to go on. You can always install without using the installer if
    you
    follow the "Path B" instructions in the installation guide - although I
    can't promise other programs will be able to run, given this problem.

    --phil

    On 7 June 2013 14:29, Lenin Raj Rajasekaran wrote:

    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale wrote:

    You need to make the installer executable before trying to run it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    I just downloaded Cloudera Standard from here and when I executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 8, 2013 at 8:02 am
    Hi Wong,

    Here is the output of ldd command:

    root@li339-83:~/cdh# ldd cloudera-manager-installer.bin
    not a dynamic executable
    root@li339-83:~/cdh#
    Should I download the bin file again? is it corrupted? Can you please
    provide a direct download link so I can use wget?
    On Saturday, June 8, 2013 12:55:49 PM UTC+5:30, bc Wong wrote:

    That installer bin is not a shell script. So the 3rd way would
    definitely not work. And since you're already root, sudo is not
    meaningful.

    The ENOENT is most likely due to missing runtime. What does `ldd
    cloudera-manager-installer.bin' say?

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:53 PM, Lenin Raj Rajasekaran
    <email...@gmail.com <javascript:>> wrote:
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from dash
    yesterday). I am running via command line. I tried 3 different ways of
    executing the bin file. Doing ./ throw "No such file or directory error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute" error

    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh# ./cloudera-manager-installer.bin
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin:
    cannot
    execute binary file

    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html
    What's the actual error when you run the installer bin? Seems that it
    exits without doing anything? (Exit code? Strace?) If you have X, it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using the
    mainline kernel source and the configuration file from
    /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I
    couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(

    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale wrote:

    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04
    installation.
    I
    note that you're using this on Linode and are running a Linode
    specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not
    giving
    you
    much to go on. You can always install without using the installer if
    you
    follow the "Path B" instructions in the installation guide -
    although I
    can't promise other programs will be able to run, given this
    problem.
    --phil

    On 7 June 2013 14:29, Lenin Raj Rajasekaran wrote:

    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj
    Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed
    to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale
    wrote:
    You need to make the installer executable before trying to run
    it.
    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    I just downloaded Cloudera Standard from here and when I
    executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable,
    x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 8, 2013 at 9:41 am
    Update:

    I just installed X in my server. And double clicked the bin file. It said
    unknown file type.
    On Saturday, June 8, 2013 1:32:29 PM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Hi Wong,

    Here is the output of ldd command:

    root@li339-83:~/cdh# ldd cloudera-manager-installer.bin
    not a dynamic executable
    root@li339-83:~/cdh#
    Should I download the bin file again? is it corrupted? Can you please
    provide a direct download link so I can use wget?
    On Saturday, June 8, 2013 12:55:49 PM UTC+5:30, bc Wong wrote:

    That installer bin is not a shell script. So the 3rd way would
    definitely not work. And since you're already root, sudo is not
    meaningful.

    The ENOENT is most likely due to missing runtime. What does `ldd
    cloudera-manager-installer.bin' say?

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:53 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from dash
    yesterday). I am running via command line. I tried 3 different ways of
    executing the bin file. Doing ./ throw "No such file or directory error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute" error

    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh# ./cloudera-manager-installer.bin
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin:
    cannot
    execute binary file

    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html
    What's the actual error when you run the installer bin? Seems that it
    exits without doing anything? (Exit code? Strace?) If you have X, it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using the
    mainline kernel source and the configuration file from
    /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel
    version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I
    couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(


    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale
    wrote:
    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04
    installation.
    I
    note that you're using this on Linode and are running a Linode
    specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not
    giving
    you
    much to go on. You can always install without using the installer
    if
    you
    follow the "Path B" instructions in the installation guide -
    although I
    can't promise other programs will be able to run, given this
    problem.
    --phil


    On 7 June 2013 14:29, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj
    Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed
    to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale
    wrote:
    You need to make the installer executable before trying to run
    it.
    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    I just downloaded Cloudera Standard from here and when I
    executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable,
    x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20
    10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin:
    cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • bc Wong at Jun 8, 2013 at 6:45 pm
    Can you run `readelf -a cloudera-manager-installer.bin' and attach the
    output? Does this exist on your system: /lib64/ld-linux-x86-64.so.2
    (provided by libc6)?

    (That ldd error means that your system can't even interpret that elf.)

    Cheers,
    bc

    On Sat, Jun 8, 2013 at 1:02 AM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Here is the output of ldd command:
    root@li339-83:~/cdh# ldd cloudera-manager-installer.bin
    not a dynamic executable
    root@li339-83:~/cdh#

    Should I download the bin file again? is it corrupted? Can you please
    provide a direct download link so I can use wget?

    On Saturday, June 8, 2013 12:55:49 PM UTC+5:30, bc Wong wrote:

    That installer bin is not a shell script. So the 3rd way would
    definitely not work. And since you're already root, sudo is not
    meaningful.

    The ENOENT is most likely due to missing runtime. What does `ldd
    cloudera-manager-installer.bin' say?

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:53 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from dash
    yesterday). I am running via command line. I tried 3 different ways of
    executing the bin file. Doing ./ throw "No such file or directory
    error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute"
    error


    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh# ./cloudera-manager-installer.bin
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin:
    cannot
    execute binary file

    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:


    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html

    What's the actual error when you run the installer bin? Seems that it
    exits without doing anything? (Exit code? Strace?) If you have X, it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using the
    mainline kernel source and the configuration file from
    /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I
    couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(

    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale wrote:

    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04
    installation.
    I
    note that you're using this on Linode and are running a Linode
    specific
    kernel. That may be the reason, or maybe there are other userspace
    differences in their image. Either way, it's not working and not
    giving
    you
    much to go on. You can always install without using the installer if
    you
    follow the "Path B" instructions in the installation guide -
    although I
    can't promise other programs will be able to run, given this
    problem.

    --phil


    On 7 June 2013 14:29, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj
    Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but missed
    to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale
    wrote:
    You need to make the installer executable before trying to run
    it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    I just downloaded Cloudera Standard from here and when I
    executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable,
    x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 8, 2013 at 7:29 pm
    Hi Wong,

    My system has *libc6 *installed.
    Attached the output of readelf command.
    Though I couldn't find the exact file you mentioned, I could locate a
    similar file in /lib/

    root@lid339-83:/lib# ls ld-linux.so.2
    ld-linux.so.2
    root@li339-83:/lib#
    On Sunday, June 9, 2013 12:15:15 AM UTC+5:30, bc Wong wrote:

    Can you run `readelf -a cloudera-manager-installer.bin' and attach the
    output? Does this exist on your system: /lib64/ld-linux-x86-64.so.2
    (provided by libc6)?

    (That ldd error means that your system can't even interpret that elf.)

    Cheers,
    bc

    On Sat, Jun 8, 2013 at 1:02 AM, Lenin Raj Rajasekaran
    <email...@gmail.com <javascript:>> wrote:
    Hi Wong,

    Here is the output of ldd command:
    root@li339-83:~/cdh# ldd cloudera-manager-installer.bin
    not a dynamic executable
    root@li339-83:~/cdh#

    Should I download the bin file again? is it corrupted? Can you please
    provide a direct download link so I can use wget?

    On Saturday, June 8, 2013 12:55:49 PM UTC+5:30, bc Wong wrote:

    That installer bin is not a shell script. So the 3rd way would
    definitely not work. And since you're already root, sudo is not
    meaningful.

    The ENOENT is most likely due to missing runtime. What does `ldd
    cloudera-manager-installer.bin' say?

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:53 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from
    dash
    yesterday). I am running via command line. I tried 3 different ways
    of
    executing the bin file. Doing ./ throw "No such file or directory
    error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute"
    error


    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh# ./cloudera-manager-installer.bin
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin:
    cannot
    execute binary file

    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot
    execute binary file
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:

    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html
    What's the actual error when you run the installer bin? Seems that
    it
    exits without doing anything? (Exit code? Strace?) If you have X,
    it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using
    the
    mainline kernel source and the configuration file from
    /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel
    version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I
    couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(


    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale
    wrote:
    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04
    installation.
    I
    note that you're using this on Linode and are running a Linode
    specific
    kernel. That may be the reason, or maybe there are other
    userspace
    differences in their image. Either way, it's not working and not
    giving
    you
    much to go on. You can always install without using the installer
    if
    you
    follow the "Path B" instructions in the installation guide -
    although I
    can't promise other programs will be able to run, given this
    problem.

    --phil


    On 7 June 2013 14:29, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj
    Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but
    missed
    to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale
    wrote:
    You need to make the installer executable before trying to run
    it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran <
    email...@gmail.com>
    wrote:
    I just downloaded Cloudera Standard from here and when I
    executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable,
    x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20
    10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin:
    cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • bc Wong at Jun 9, 2013 at 4:31 am

    On Sat, Jun 8, 2013 at 12:29 PM, Lenin Raj Rajasekaran wrote:
    Hi Wong,

    My system has libc6 installed.
    Attached the output of readelf command.
    Though I couldn't find the exact file you mentioned, I could locate a
    similar file in /lib/
    root@lid339-83:/lib# ls ld-linux.so.2
    ld-linux.so.2
    root@li339-83:/lib#
    Aye. You have the 32-bit version of libc6 somehow. The CM installer is
    a 64-bit program and needs the amd64 version of libc6.

    See http://packages.ubuntu.com/search?suite=precise&arch=any&mode=exactfilename&searchon=contents&keywords=ld-linux.so.2.
    The amd64 version of libc6 would provide
    `/lib64/ld-linux-x86-64.so.2'. Another confirmation would be to look
    at `dpkg -s libc6 | grep Arch'. Looks like this on my system:

    $ dpkg -s libc6 | grep Arch
    Multi-Arch: same
    Architecture: amd64

    I'm guessing that yours would say i386. (If that's the case, could you
    let me know how you ended up with a 64-bit kernel + 32-bit libc? I'm
    curious.)

    Cheers,
    bc
    On Sunday, June 9, 2013 12:15:15 AM UTC+5:30, bc Wong wrote:

    Can you run `readelf -a cloudera-manager-installer.bin' and attach the
    output? Does this exist on your system: /lib64/ld-linux-x86-64.so.2
    (provided by libc6)?

    (That ldd error means that your system can't even interpret that elf.)

    Cheers,
    bc

    On Sat, Jun 8, 2013 at 1:02 AM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Here is the output of ldd command:
    root@li339-83:~/cdh# ldd cloudera-manager-installer.bin
    not a dynamic executable
    root@li339-83:~/cdh#

    Should I download the bin file again? is it corrupted? Can you please
    provide a direct download link so I can use wget?

    On Saturday, June 8, 2013 12:55:49 PM UTC+5:30, bc Wong wrote:

    That installer bin is not a shell script. So the 3rd way would
    definitely not work. And since you're already root, sudo is not
    meaningful.

    The ENOENT is most likely due to missing runtime. What does `ldd
    cloudera-manager-installer.bin' say?

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:53 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    I don't have X in my server. My default shell is bash (changed from
    dash
    yesterday). I am running via command line. I tried 3 different ways
    of
    executing the bin file. Doing ./ throw "No such file or directory
    error".
    Doing sudo ./ does nothing. Doing sh ./ or sh gives "cannot execute"
    error


    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh# ./cloudera-manager-installer.bin
    -bash: ./cloudera-manager-installer.bin: No such file or directory
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh# sh ./cloudera-manager-installer.bin
    ./cloudera-manager-installer.bin: ./cloudera-manager-installer.bin:
    cannot
    execute binary file

    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin:
    cannot
    execute binary file
    root@li339-83:~/cdh#
    On Saturday, June 8, 2013 12:11:00 PM UTC+5:30, bc Wong wrote:

    The path B doc is here:



    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_install_cm_cdh.html

    What's the actual error when you run the installer bin? Seems that
    it
    exits without doing anything? (Exit code? Strace?) If you have X,
    it's
    supposed to bring up a graphical installation dialog. Otherwise it's
    text based.

    Cheers,
    bc

    On Fri, Jun 7, 2013 at 11:36 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Philip,

    According to this forum, they say:
    Linode's kernels aren't modified; you can reproduce them using
    the
    mainline kernel source and the configuration file from
    /proc/config.gz,
    plus
    a quick edit to config.h to stick -linodeXX into the kernel
    version.

    So I think it is not a problem with the kernel build.

    Can you please share the link to the "Path B" instructions? I
    couldn't
    locate it here

    If nothing seems to work, I have to go back to the plain vanilla
    distributions :(


    On Saturday, June 8, 2013 3:13:26 AM UTC+5:30, Philip Langdale
    wrote:
    Hi Lenin,

    I'm not sure what to say. It works fine on a stock 12.04
    installation.
    I
    note that you're using this on Linode and are running a Linode
    specific
    kernel. That may be the reason, or maybe there are other
    userspace
    differences in their image. Either way, it's not working and not
    giving
    you
    much to go on. You can always install without using the installer
    if
    you
    follow the "Path B" instructions in the installation guide -
    although I
    can't promise other programs will be able to run, given this
    problem.

    --phil


    On 7 June 2013 14:29, Lenin Raj Rajasekaran <email...@gmail.com>
    wrote:
    My OS Details:
    root@li339-83:~/cdh# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:50:37 AM UTC+5:30, Lenin Raj
    Rajasekaran
    wrote:
    Philip, Thanks for replying. I have done that already (but
    missed
    to
    post in my code)
    root@li339-83:~/cdh# ll
    total 504
    drwxr-xr-x 2 root root 4096 Jun 8 02:26 ./
    drwx------ 13 root root 4096 Jun 8 02:25 ../
    -rwxr-xr-x 1 root root 501703 Jun 8 02:26
    cloudera-manager-installer.bin*
    root@li339-83:~/cdh#


    On Saturday, June 8, 2013 2:48:27 AM UTC+5:30, Philip Langdale
    wrote:
    You need to make the installer executable before trying to run
    it.

    # chmod +x cloudera-manager-installer.bin
    # sudo ./cloudera-manager-installer.bin


    --phil


    On 7 June 2013 14:14, Lenin Raj Rajasekaran
    <email...@gmail.com>
    wrote:
    I just downloaded Cloudera Standard from here and when I
    executed
    the
    bin file, I got the following error:
    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable,
    x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for
    GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20
    10:22:57
    EDT
    2013 x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin:
    cloudera-manager-installer.bin:
    cannot execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • Lenin Raj Rajasekaran at Jun 9, 2013 at 6:51 am
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.

    Now, I have installed the package *libc6-amd64*

    root@li339-83:~# apt-get install libc6-amd64
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following NEW packages will be installed:
       libc6-amd64
    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
    Need to get 4,615 kB of archives.
    After this operation, 10.9 MB of additional disk space will be used.
    Get:1 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main libc6-amd64
    i386 2.15-0ubuntu10.4 [4,615 kB]
    Fetched 4,615 kB in 3s (1,201 kB/s)
    Selecting previously unselected package libc6-amd64.
    (Reading database ... 130862 files and directories currently installed.)
    Unpacking libc6-amd64 (from .../libc6-amd64_2.15-0ubuntu10.4_i386.deb) ...
    Setting up libc6-amd64 (2.15-0ubuntu10.4) ...
    Processing triggers for libc-bin ...
    ldconfig deferred processing now taking place
    root@li339-83:/lib64# ls ld-linux-x86-64.so.2
    ld-linux-x86-64.so.2
    root@li339-83:/lib64#

    I could locate the file ld-linux-x86-64.so.2 in /lib64/ now.

    But libc6 still shows i386

    root@li339-83:/lib64# dpkg -s libc6 | grep Arch
    Multi-Arch: same
    Architecture: i386
    root@li339-83:/lib64#

    I am not able to remove libc6 package. It shows the error E: Error,
    pkgProblemResolver::Resolve generated breaks, this may be caused by held
    packages. while trying to remove.

    Is it okay to have both* libc6 and libc6-amd64* installed together?
    Do I need to check for any other 32 bit left overs?

    Thanks,
    Lenin
    On Saturday, June 8, 2013 2:44:13 AM UTC+5:30, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT 2013
    x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#
  • bc Wong at Jun 9, 2013 at 7:27 am

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
  • Lenin Raj Rajasekaran at Jun 9, 2013 at 7:49 am
    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and start
    from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    <email...@gmail.com <javascript:>> wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
  • Dilip Varma at Oct 18, 2013 at 10:00 am
    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean while
    it is running prompts to accept the license key and next etc..how to select
    these prompts using scripts without entering manually..
    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
    start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Darren Lo at Oct 18, 2013 at 2:54 pm
    Hi Dilip,

    You can use the Cloudera Manager REST API to automate your setup process
    once you have CM installed.

    The most relevant API documentation is in Cloudera Manager, if you poke
    around the menus in the upper right corner. You can also find API docs
    online here: http://cloudera.github.io/cm_api/. As you read through them,
    you'll find an API endpoint "/cm/license" that will take care of the
    license for you.

    Note that when using the API to set up your cluster, you are responsible
    for knowing which commands need to be run, such as formatting the namenode,
    starting hdfs, creating /tmp, etc. Also the current API doesn't help you
    install CM agents on your hosts, but that will be added in an upcoming
    release.

    Here's some useful links to help get you started:

    CM Architecture blog
    http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/

    API Examples and Tutorials
    http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/
    http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/

    Thanks,
    Darren


    On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:

    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean
    while it is running prompts to accept the license key and next etc..how to
    select these prompts using scripts without entering manually..

    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
    start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it, send
    an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren

    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Dilip Varma at Oct 22, 2013 at 3:08 pm
    Hi Darren,

    Thanks for your quick response and inputs.

    We want run *cloudera*-*manager*-*installer*.*bin* in non TUI mode. We
    tried with below options but its not working.

    --i-agree-to-all-licenses
    --noprompt
    --noreadme
    --nooptions

    We are getting "Fatal Error" installation failed message with above
    options. Any pointers in this regards will help us in getting out of this
    issue.

    Thanks in advance.


    Regards,
    Dilip.

    Thanks,
    Dilip

    On Fri, Oct 18, 2013 at 8:24 PM, Darren Lo wrote:

    Hi Dilip,

    You can use the Cloudera Manager REST API to automate your setup process
    once you have CM installed.

    The most relevant API documentation is in Cloudera Manager, if you poke
    around the menus in the upper right corner. You can also find API docs
    online here: http://cloudera.github.io/cm_api/. As you read through them,
    you'll find an API endpoint "/cm/license" that will take care of the
    license for you.

    Note that when using the API to set up your cluster, you are responsible
    for knowing which commands need to be run, such as formatting the namenode,
    starting hdfs, creating /tmp, etc. Also the current API doesn't help you
    install CM agents on your hosts, but that will be added in an upcoming
    release.

    Here's some useful links to help get you started:

    CM Architecture blog
    http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/

    API Examples and Tutorials

    http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/

    http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/

    Thanks,
    Darren


    On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:

    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean
    while it is running prompts to accept the license key and next etc..how to
    select these prompts using scripts without entering manually..

    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
    start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it, send
    an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Darren Lo at Oct 22, 2013 at 6:50 pm
    Hi Dilip,

    Sorry for misunderstanding. Did you run it as root? Was there a more
    descriptive error message?

    Thanks,
    Darren

    On Tue, Oct 22, 2013 at 8:08 AM, Dilip Varma wrote:

    Hi Darren,

    Thanks for your quick response and inputs.

    We want run *cloudera*-*manager*-*installer*.*bin* in non TUI mode. We
    tried with below options but its not working.

    --i-agree-to-all-licenses
    --noprompt
    --noreadme
    --nooptions

    We are getting "Fatal Error" installation failed message with above
    options. Any pointers in this regards will help us in getting out of this
    issue.

    Thanks in advance.


    Regards,
    Dilip.

    Thanks,
    Dilip

    On Fri, Oct 18, 2013 at 8:24 PM, Darren Lo wrote:

    Hi Dilip,

    You can use the Cloudera Manager REST API to automate your setup process
    once you have CM installed.

    The most relevant API documentation is in Cloudera Manager, if you poke
    around the menus in the upper right corner. You can also find API docs
    online here: http://cloudera.github.io/cm_api/. As you read through
    them, you'll find an API endpoint "/cm/license" that will take care of the
    license for you.

    Note that when using the API to set up your cluster, you are responsible
    for knowing which commands need to be run, such as formatting the namenode,
    starting hdfs, creating /tmp, etc. Also the current API doesn't help you
    install CM agents on your hosts, but that will be added in an upcoming
    release.

    Here's some useful links to help get you started:

    CM Architecture blog
    http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/

    API Examples and Tutorials

    http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/

    http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/

    Thanks,
    Darren


    On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:

    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean
    while it is running prompts to accept the license key and next etc..how to
    select these prompts using scripts without entering manually..

    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran wrote:

    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
    start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it, send
    an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send an
    email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren

    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Dilip Varma at Oct 23, 2013 at 8:13 am
    Hi Darren,

    It is working fine with these 4 options(--i-agree-to-all-licenses,
    --noprompt,--noreadme,--nooptions).

    can i know what it is doing exactly?

    and i want that bin file should run using my own repo file

    for ex:
    cat /etc/yum.repos.d/cloudera.manager.repo
    [cloudera-manager]
    name=Cloudera Manager
    baseurl=http://<MY NODE PUBLIC DNS>/cm4/redhat/6/x86_64/cm/4/
    gpgkey = http://MY NODE PUBLIC
    DNS/cm4/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
    gpgcheck=1

    without this bin file is there any way to get CM WEB UI,i have seen that
    PATH B will solve this..
    i've followed PATH B but no use,while navigating to browser

    http://<public dns>:7180

    it is throwing CONNECTION TIMED ERROR.

    how to oversome this issue using PATH B and what CM.BIN file is doing while
    running?

    Thanks & Regards,
    Dilip

    Thanks,
    Dilip

    On Wed, Oct 23, 2013 at 12:20 AM, Darren Lo wrote:

    Hi Dilip,

    Sorry for misunderstanding. Did you run it as root? Was there a more
    descriptive error message?

    Thanks,
    Darren

    On Tue, Oct 22, 2013 at 8:08 AM, Dilip Varma wrote:

    Hi Darren,

    Thanks for your quick response and inputs.

    We want run *cloudera*-*manager*-*installer*.*bin* in non TUI mode. We
    tried with below options but its not working.

    --i-agree-to-all-licenses
    --noprompt
    --noreadme
    --nooptions

    We are getting "Fatal Error" installation failed message with above
    options. Any pointers in this regards will help us in getting out of this
    issue.

    Thanks in advance.


    Regards,
    Dilip.

    Thanks,
    Dilip

    On Fri, Oct 18, 2013 at 8:24 PM, Darren Lo wrote:

    Hi Dilip,

    You can use the Cloudera Manager REST API to automate your setup process
    once you have CM installed.

    The most relevant API documentation is in Cloudera Manager, if you poke
    around the menus in the upper right corner. You can also find API docs
    online here: http://cloudera.github.io/cm_api/. As you read through
    them, you'll find an API endpoint "/cm/license" that will take care of the
    license for you.

    Note that when using the API to set up your cluster, you are responsible
    for knowing which commands need to be run, such as formatting the namenode,
    starting hdfs, creating /tmp, etc. Also the current API doesn't help you
    install CM agents on your hosts, but that will be added in an upcoming
    release.

    Here's some useful links to help get you started:

    CM Architecture blog
    http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/

    API Examples and Tutorials

    http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/

    http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/

    Thanks,
    Darren


    On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:

    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean
    while it is running prompts to accept the license key and next etc..how to
    select these prompts using scripts without entering manually..


    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
    start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it,
    send an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send
    an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Dilip Varma at Oct 23, 2013 at 10:17 am
    Hi Darren,

    i'm following PATH B for alternative instead of using CM bin file to get CM
    WEB UI

    when i restarting CM DB it is giving that

          *postgres -D /var/lib/cloudera-scm-server-db/data or*
    * *
    * pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start*
    *
    *
    *Check below for reference:*

    $sudo service cloudera-scm-server-db start
    The files belonging to this database system will be owned by user
    "cloudera-scm".
    This user must also own the server process.

    The database cluster will be initialized with locale en_US.UTF8.
    The default text search configuration will be set to "english".

    fixing permissions on existing directory
    /var/lib/cloudera-scm-server-db/data ... ok
    creating subdirectories ... ok
    selecting default max_connections ... 100
    selecting default shared_buffers ... 32MB
    creating configuration files ... ok
    creating template1 database in /var/lib/cloudera-scm-server-db/data/base/1
    ... ok
    initializing pg_authid ... ok
    setting password ... ok
    initializing dependencies ... ok
    creating system views ... ok
    loading system objects' descriptions ... ok
    creating conversions ... ok
    creating dictionaries ... ok
    setting privileges on built-in objects ... ok
    creating information schema ... ok
    vacuuming database template1 ... ok
    copying template1 to template0 ... ok
    copying template1 to postgres ... ok

    Success. You can now start the database server using:

         postgres -D /var/lib/cloudera-scm-server-db/data
    or
         pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start

    *$sudo pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start*
    *
    *
    *pg_ctl: cannot be run as root*
    *Please log in (using, e.g., "su") as the (unprivileged) user that will*
    *own the server process.*
    *
    *
    where do i need to run this command?



    Thanks,
    Dilip

    On Wed, Oct 23, 2013 at 1:43 PM, Dilip Varma wrote:

    Hi Darren,

    It is working fine with these 4 options(--i-agree-to-all-licenses,
    --noprompt,--noreadme,--nooptions).

    can i know what it is doing exactly?

    and i want that bin file should run using my own repo file

    for ex:
    cat /etc/yum.repos.d/cloudera.manager.repo
    [cloudera-manager]
    name=Cloudera Manager
    baseurl=http://<MY NODE PUBLIC DNS>/cm4/redhat/6/x86_64/cm/4/
    gpgkey = http://MY NODE PUBLIC
    DNS/cm4/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
    gpgcheck=1

    without this bin file is there any way to get CM WEB UI,i have seen that
    PATH B will solve this..
    i've followed PATH B but no use,while navigating to browser

    http://<public dns>:7180

    it is throwing CONNECTION TIMED ERROR.

    how to oversome this issue using PATH B and what CM.BIN file is doing
    while running?

    Thanks & Regards,
    Dilip

    Thanks,
    Dilip

    On Wed, Oct 23, 2013 at 12:20 AM, Darren Lo wrote:

    Hi Dilip,

    Sorry for misunderstanding. Did you run it as root? Was there a more
    descriptive error message?

    Thanks,
    Darren

    On Tue, Oct 22, 2013 at 8:08 AM, Dilip Varma wrote:

    Hi Darren,

    Thanks for your quick response and inputs.

    We want run *cloudera*-*manager*-*installer*.*bin* in non TUI mode. We
    tried with below options but its not working.

    --i-agree-to-all-licenses
    --noprompt
    --noreadme
    --nooptions

    We are getting "Fatal Error" installation failed message with above
    options. Any pointers in this regards will help us in getting out of this
    issue.

    Thanks in advance.


    Regards,
    Dilip.

    Thanks,
    Dilip

    On Fri, Oct 18, 2013 at 8:24 PM, Darren Lo wrote:

    Hi Dilip,

    You can use the Cloudera Manager REST API to automate your setup
    process once you have CM installed.

    The most relevant API documentation is in Cloudera Manager, if you poke
    around the menus in the upper right corner. You can also find API docs
    online here: http://cloudera.github.io/cm_api/. As you read through
    them, you'll find an API endpoint "/cm/license" that will take care of the
    license for you.

    Note that when using the API to set up your cluster, you are
    responsible for knowing which commands need to be run, such as formatting
    the namenode, starting hdfs, creating /tmp, etc. Also the current API
    doesn't help you install CM agents on your hosts, but that will be added in
    an upcoming release.

    Here's some useful links to help get you started:

    CM Architecture blog
    http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/

    API Examples and Tutorials

    http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/

    http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/

    Thanks,
    Darren


    On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:

    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean
    while it is running prompts to accept the license key and next etc..how to
    select these prompts using scripts without entering manually..


    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
    start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it,
    send an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send
    an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Darren Lo at Oct 23, 2013 at 3:28 pm
    Hi Dilip,

    If you want to customize the repo file, you're correct in picking Path B.

    You should ignore the message about running pg_ctl. You should always start
    the postgres used by cm using "service cloudera-scm-server-db start".
    Instead, just follow the steps in Cloudera Manager documentation.

    Your output should have had lines about creating various databases. It is
    very strange that those are missing, and seems like it might indicate a
    problem. I would yum erase all cloudera packages, make sure
    /var/lib/clouders-scm-server-db is empty, and start again.

    If you want to use the embedded postgresql database, you usually just need
    to install java, set up your repo files to point to the right cloudera
    manager package repository, yum install cloudera-manager-server-db, then
    run "sudo service cloudera-manager-server-db start" and then "sudo service
    cloudera-manager-server start".

    Thanks,
    Darren

    On Wed, Oct 23, 2013 at 3:17 AM, Dilip Varma wrote:

    Hi Darren,

    i'm following PATH B for alternative instead of using CM bin file to get
    CM WEB UI

    when i restarting CM DB it is giving that

    *postgres -D /var/lib/cloudera-scm-server-db/data or*
    * *
    * pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start*
    *
    *
    *Check below for reference:*

    $sudo service cloudera-scm-server-db start
    The files belonging to this database system will be owned by user
    "cloudera-scm".
    This user must also own the server process.

    The database cluster will be initialized with locale en_US.UTF8.
    The default text search configuration will be set to "english".

    fixing permissions on existing directory
    /var/lib/cloudera-scm-server-db/data ... ok
    creating subdirectories ... ok
    selecting default max_connections ... 100
    selecting default shared_buffers ... 32MB
    creating configuration files ... ok
    creating template1 database in /var/lib/cloudera-scm-server-db/data/base/1
    ... ok
    initializing pg_authid ... ok
    setting password ... ok
    initializing dependencies ... ok
    creating system views ... ok
    loading system objects' descriptions ... ok
    creating conversions ... ok
    creating dictionaries ... ok
    setting privileges on built-in objects ... ok
    creating information schema ... ok
    vacuuming database template1 ... ok
    copying template1 to template0 ... ok
    copying template1 to postgres ... ok

    Success. You can now start the database server using:

    postgres -D /var/lib/cloudera-scm-server-db/data
    or
    pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start

    *$sudo pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start*
    *
    *
    *pg_ctl: cannot be run as root*
    *Please log in (using, e.g., "su") as the (unprivileged) user that will*
    *own the server process.*
    *
    *
    where do i need to run this command?



    Thanks,
    Dilip

    On Wed, Oct 23, 2013 at 1:43 PM, Dilip Varma wrote:

    Hi Darren,

    It is working fine with these 4 options(--i-agree-to-all-licenses,
    --noprompt,--noreadme,--nooptions).

    can i know what it is doing exactly?

    and i want that bin file should run using my own repo file

    for ex:
    cat /etc/yum.repos.d/cloudera.manager.repo
    [cloudera-manager]
    name=Cloudera Manager
    baseurl=http://<MY NODE PUBLIC DNS>/cm4/redhat/6/x86_64/cm/4/
    gpgkey = http://MY NODE PUBLIC
    DNS/cm4/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
    gpgcheck=1

    without this bin file is there any way to get CM WEB UI,i have seen that
    PATH B will solve this..
    i've followed PATH B but no use,while navigating to browser

    http://<public dns>:7180

    it is throwing CONNECTION TIMED ERROR.

    how to oversome this issue using PATH B and what CM.BIN file is doing
    while running?

    Thanks & Regards,
    Dilip

    Thanks,
    Dilip

    On Wed, Oct 23, 2013 at 12:20 AM, Darren Lo wrote:

    Hi Dilip,

    Sorry for misunderstanding. Did you run it as root? Was there a more
    descriptive error message?

    Thanks,
    Darren

    On Tue, Oct 22, 2013 at 8:08 AM, Dilip Varma wrote:

    Hi Darren,

    Thanks for your quick response and inputs.

    We want run *cloudera*-*manager*-*installer*.*bin* in non TUI mode. We
    tried with below options but its not working.

    --i-agree-to-all-licenses
    --noprompt
    --noreadme
    --nooptions

    We are getting "Fatal Error" installation failed message with above
    options. Any pointers in this regards will help us in getting out of this
    issue.

    Thanks in advance.


    Regards,
    Dilip.

    Thanks,
    Dilip

    On Fri, Oct 18, 2013 at 8:24 PM, Darren Lo wrote:

    Hi Dilip,

    You can use the Cloudera Manager REST API to automate your setup
    process once you have CM installed.

    The most relevant API documentation is in Cloudera Manager, if you
    poke around the menus in the upper right corner. You can also find API docs
    online here: http://cloudera.github.io/cm_api/. As you read through
    them, you'll find an API endpoint "/cm/license" that will take care of the
    license for you.

    Note that when using the API to set up your cluster, you are
    responsible for knowing which commands need to be run, such as formatting
    the namenode, starting hdfs, creating /tmp, etc. Also the current API
    doesn't help you install CM agents on your hosts, but that will be added in
    an upcoming release.

    Here's some useful links to help get you started:

    CM Architecture blog
    http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/

    API Examples and Tutorials

    http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/

    http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/

    Thanks,
    Darren


    On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:

    Hi Team,

    How to run the cloudera binary file using shell or perl script.i mean
    while it is running prompts to accept the license key and next etc..how to
    select these prompts using scripts without entering manually..


    On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran
    wrote:
    Thanks Wong.

    I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS
    and start from scratch.

    Thanks,
    Lenin
    On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:

    On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
    wrote:
    Hi Wong,

    Thanks for finding that out.

    Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
    kernel (to install CDH) by changing the kernel via Linode Manager and
    rebooting the server. After reboot, uname -a showed 64 bit
    system. So I
    thought everything went fine. But looking at this libc6 problem, I think
    there might be other related issues as well.
    <snip>

    Hi Lenin,

    I'd highly recommend that you start from scratch, with a 64 bit
    system. Who knows what other gotchas you'll find.

    Cheers,
    bc
    To unsubscribe from this group and stop receiving emails from it,
    send an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren
    To unsubscribe from this group and stop receiving emails from it, send
    an email to scm-users+unsubscribe@cloudera.org.


    --
    Thanks,
    Darren

    --
    Thanks,
    Darren

    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Lenin Raj Rajasekaran at Jun 9, 2013 at 7:03 am
    Hello,

    I executed the bin file now. It starts executing.

    Accepted the license. It failed with

    NOTICE: oracle-j2sdk1.6 installation failed. See
    /var/log/cloudera-manager-installer/3.install-oracle-j2sdk1.6.log for
    details. Click OK to revert this installation.

    That log file has the following:

    root@li339-83:~# cat
    /var/log/cloudera-manager-installer/3.install-oracle-j2sdk1.6.log
    Reading package lists...
    Building dependency tree...
    Reading state information...
    E: Unable to locate package oracle-j2sdk1.6
    E: Couldn't find any package by regex 'oracle-j2sdk1.6'
    root@li339-83:~#

    I have Oracle JDK already. How to skip this installation?

    On Saturday, June 8, 2013 2:44:13 AM UTC+5:30, Lenin Raj Rajasekaran wrote:

    I just downloaded Cloudera Standard from here<https://ccp.cloudera.com/display/SUPPORT/Downloads>and when I executed the bin file, I got the following error:

    root@li339-83:~/cdh# file cloudera-manager-installer.bin
    cloudera-manager-installer.bin: ELF 64-bit LSB executable, x86-64,
    version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
    2.6.9, not stripped
    root@li339-83:~/cdh# uname -a
    Linux li339-83 3.9.3-x86_64-linode33 #1 SMP Mon May 20 10:22:57 EDT 2013
    x86_64 x86_64 x86_64 GNU/Linux
    root@li339-83:~/cdh# sh cloudera-manager-installer.bin
    cloudera-manager-installer.bin: cloudera-manager-installer.bin: cannot
    execute binary file
    root@li339-83:~/cdh# sudo ./cloudera-manager-installer.bin
    root@li339-83:~/cdh#

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJun 7, '13 at 9:14p
activeOct 23, '13 at 3:28p
posts25
users5
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase