FAQ
Hi,

I have 2 queries.

1)
I was able to install the Cloudera Manager successfully.
When I try to add a host, I get the error message as below.

==========================================================
/tmp/scm_prepare_node.iBS24382
using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
opening logging file descriptor
Starting installation script... Acquiring installation lock...
*BEGIN flock 4 *
Usage flock [--shared | --timeout=seconds] filename command {arg arg...}
*END (2) *
could not acquire installation lock, giving up
Reverting changes...
rollback started
Removing package repositories... Cleaning the package manager cache...
unknown packager , exiting
closing logging file descriptor
==========================================================

Can somebody help me resolve this?

2)
This is when I give the IP of a different system where the Manager is not
installed.
But when I provide the IP of the same system where the Manager is
installed, it installs successfully.
But I am not able to see this is the list of managed hosts. Why is this?


Regards,
Mahesh

Search Discussions

  • Philip Zeyliger at Feb 21, 2013 at 5:12 pm
    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a" or
    "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.log; that'll give us a hint.

    Thanks,

    -- Philip

    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru wrote:

    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==========================================================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager cache...
    unknown packager , exiting
    closing logging file descriptor
    ==========================================================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager is not
    installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is this?


    Regards,
    Mahesh

  • Mahesh Bengaluru at Feb 22, 2013 at 3:41 am
    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version:
    core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh
    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a" or
    "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <mahesh.be...@gmail.com<javascript:>
    wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==========================================================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager cache...
    unknown packager , exiting
    closing logging file descriptor
    ==========================================================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager is not
    installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is this?


    Regards,
    Mahesh

  • Philip Zeyliger at Feb 22, 2013 at 4:09 am
    Hi Mahesh,

    Fascinating! You seem to have a very different version of flock than the
    ones we're used to. Could you run "rpm -qf $(which flock)" to figure out
    what package it's coming from? Perhaps there are multiple flocks on your
    system? We've tested with SLES11SP2 quite extensively, and have never seen
    this differing version of /usr/bin/flock before. Are you on SLES11 SP2?

    The workaround is to either install CM manually (we call this "path B" in
    our docs) or to extract a certain jar and replace the script, which I'm
    hesitant to go into too much.

    Here's what I see on my test SLES machine:

    jenkins-sles11-1:~ # flock --version
    flock (util-linux 2.19.1)
    jenkins-sles11-1:~ # flock --help
    flock (util-linux 2.19.1)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version
    jenkins-sles11-1:~ # rpm -qf $(which flock)
    util-linux-2.19.1-6.29.3
    jenkins-sles11-1:/etc # cat issue

    Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r (\l).


    Thanks!

    -- Philip


    On Thu, Feb 21, 2013 at 7:41 PM, Mahesh Bengaluru wrote:

    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version:
    core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh
    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a" or
    "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.**log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <mahesh.be...@gmail.com
    wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==============================**============================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager cache...
    unknown packager , exiting
    closing logging file descriptor
    ==============================**============================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager is
    not installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is this?


    Regards,
    Mahesh

  • Mahesh Bengaluru at Feb 22, 2013 at 6:27 am
    Hi Philip,

    rpm -qf $(which flock)
    returned me

    util-linux-2.16-6.8.2

    I will try installing CM manually & let you know how it goes.

    Regards,
    Mahesh

    On Friday, February 22, 2013 9:39:02 AM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    Fascinating! You seem to have a very different version of flock than the
    ones we're used to. Could you run "rpm -qf $(which flock)" to figure out
    what package it's coming from? Perhaps there are multiple flocks on your
    system? We've tested with SLES11SP2 quite extensively, and have never seen
    this differing version of /usr/bin/flock before. Are you on SLES11 SP2?

    The workaround is to either install CM manually (we call this "path B" in
    our docs) or to extract a certain jar and replace the script, which I'm
    hesitant to go into too much.

    Here's what I see on my test SLES machine:

    jenkins-sles11-1:~ # flock --version
    flock (util-linux 2.19.1)
    jenkins-sles11-1:~ # flock --help
    flock (util-linux 2.19.1)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version
    jenkins-sles11-1:~ # rpm -qf $(which flock)
    util-linux-2.19.1-6.29.3
    jenkins-sles11-1:/etc # cat issue

    Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r (\l).


    Thanks!

    -- Philip



    On Thu, Feb 21, 2013 at 7:41 PM, Mahesh Bengaluru <mahesh.be...@gmail.com<javascript:>
    wrote:
    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version:
    core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh

    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger
    wrote:
    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a" or
    "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.**log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==============================**============================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg
    arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager cache...
    unknown packager , exiting
    closing logging file descriptor
    ==============================**============================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager is
    not installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is this?


    Regards,
    Mahesh

  • Philip Zeyliger at Feb 22, 2013 at 5:06 pm
    Hi Mahesh,

    Oddly, I spun up an instance of SLES11SP1 in EC2, and though I'm seeing the
    same version of flock that you're seeing, it has a different (correct)
    usage string. I'm wondering whether it's possible that there are multiple
    flock's on the path somehow.

    ip-172-25-2-4:~ # flock --help
    flock (util-linux-ng 2.16)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version

    Good luck with the manual install--let us know if we can help.

    On Thu, Feb 21, 2013 at 10:27 PM, Mahesh Bengaluru wrote:

    Hi Philip,

    rpm -qf $(which flock)
    returned me

    util-linux-2.16-6.8.2

    I will try installing CM manually & let you know how it goes.

    Regards,
    Mahesh

    On Friday, February 22, 2013 9:39:02 AM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    Fascinating! You seem to have a very different version of flock than the
    ones we're used to. Could you run "rpm -qf $(which flock)" to figure out
    what package it's coming from? Perhaps there are multiple flocks on your
    system? We've tested with SLES11SP2 quite extensively, and have never seen
    this differing version of /usr/bin/flock before. Are you on SLES11 SP2?

    The workaround is to either install CM manually (we call this "path B" in
    our docs) or to extract a certain jar and replace the script, which I'm
    hesitant to go into too much.

    Here's what I see on my test SLES machine:

    jenkins-sles11-1:~ # flock --version
    flock (util-linux 2.19.1)
    jenkins-sles11-1:~ # flock --help
    flock (util-linux 2.19.1)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version
    jenkins-sles11-1:~ # rpm -qf $(which flock)
    util-linux-2.19.1-6.29.3
    jenkins-sles11-1:/etc # cat issue

    Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r (\l).


    Thanks!

    -- Philip



    On Thu, Feb 21, 2013 at 7:41 PM, Mahesh Bengaluru <mahesh.be...@gmail.com
    wrote:
    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version: core-2.0-noarch:core-3.2-**
    noarch:core-4.0-noarch:core-2.**0-x86_64:core-3.2-x86_64:core-**
    4.0-x86_64:desktop-4.0-amd64:**desktop-4.0-noarch:graphics-2.**
    0-amd64:graphics-2.0-noarch:**graphics-3.2-amd64:graphics-3.**
    2-noarch:graphics-4.0-amd64:**graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh

    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger
    wrote:
    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a" or
    "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.****log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==============================****============================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg
    arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager cache...
    unknown packager , exiting
    closing logging file descriptor
    ==============================****============================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager is
    not installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is
    this?


    Regards,
    Mahesh

  • Philip Langdale at Feb 22, 2013 at 6:31 pm
    Phil,

    You're not seeing it. You're seeing util-linux-ng 2.16 and Mahesh is
    seeing util-linux 2.19.1 (not ng).

    Mahesh, are you running SP1 or SP2? We don't support base SLES11.

    --phil

    On 22 February 2013 09:00, Philip Zeyliger wrote:

    Hi Mahesh,

    Oddly, I spun up an instance of SLES11SP1 in EC2, and though I'm seeing
    the same version of flock that you're seeing, it has a different (correct)
    usage string. I'm wondering whether it's possible that there are multiple
    flock's on the path somehow.

    ip-172-25-2-4:~ # flock --help
    flock (util-linux-ng 2.16)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version

    Good luck with the manual install--let us know if we can help.


    On Thu, Feb 21, 2013 at 10:27 PM, Mahesh Bengaluru <
    mahesh.bengalurava@gmail.com> wrote:
    Hi Philip,

    rpm -qf $(which flock)
    returned me

    util-linux-2.16-6.8.2

    I will try installing CM manually & let you know how it goes.

    Regards,
    Mahesh

    On Friday, February 22, 2013 9:39:02 AM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    Fascinating! You seem to have a very different version of flock than
    the ones we're used to. Could you run "rpm -qf $(which flock)" to figure
    out what package it's coming from? Perhaps there are multiple flocks on
    your system? We've tested with SLES11SP2 quite extensively, and have never
    seen this differing version of /usr/bin/flock before. Are you on SLES11
    SP2?

    The workaround is to either install CM manually (we call this "path B"
    in our docs) or to extract a certain jar and replace the script, which I'm
    hesitant to go into too much.

    Here's what I see on my test SLES machine:

    jenkins-sles11-1:~ # flock --version
    flock (util-linux 2.19.1)
    jenkins-sles11-1:~ # flock --help
    flock (util-linux 2.19.1)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version
    jenkins-sles11-1:~ # rpm -qf $(which flock)
    util-linux-2.19.1-6.29.3
    jenkins-sles11-1:/etc # cat issue

    Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r
    (\l).


    Thanks!

    -- Philip



    On Thu, Feb 21, 2013 at 7:41 PM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version: core-2.0-noarch:core-3.2-**
    noarch:core-4.0-noarch:core-2.**0-x86_64:core-3.2-x86_64:core-**
    4.0-x86_64:desktop-4.0-amd64:**desktop-4.0-noarch:graphics-2.**
    0-amd64:graphics-2.0-noarch:**graphics-3.2-amd64:graphics-3.**
    2-noarch:graphics-4.0-amd64:**graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh

    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger
    wrote:
    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a"
    or "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.****log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==============================****============================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg
    arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager
    cache...
    unknown packager , exiting
    closing logging file descriptor
    ==============================****============================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager is
    not installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is
    this?


    Regards,
    Mahesh

  • Philip Langdale at Feb 22, 2013 at 7:02 pm
    Sorry, slight clarification.

    Mahesh reported util-linux-ng 2.16
    and Phil reported util-linux 2.19.1

    So I had it the wrong way round

    --phil

    On 22 February 2013 10:31, Philip Langdale wrote:

    Phil,

    You're not seeing it. You're seeing util-linux-ng 2.16 and Mahesh is
    seeing util-linux 2.19.1 (not ng).

    Mahesh, are you running SP1 or SP2? We don't support base SLES11.

    --phil

    On 22 February 2013 09:00, Philip Zeyliger wrote:

    Hi Mahesh,

    Oddly, I spun up an instance of SLES11SP1 in EC2, and though I'm seeing
    the same version of flock that you're seeing, it has a different (correct)
    usage string. I'm wondering whether it's possible that there are multiple
    flock's on the path somehow.

    ip-172-25-2-4:~ # flock --help
    flock (util-linux-ng 2.16)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version

    Good luck with the manual install--let us know if we can help.


    On Thu, Feb 21, 2013 at 10:27 PM, Mahesh Bengaluru <
    mahesh.bengalurava@gmail.com> wrote:
    Hi Philip,

    rpm -qf $(which flock)
    returned me

    util-linux-2.16-6.8.2

    I will try installing CM manually & let you know how it goes.

    Regards,
    Mahesh

    On Friday, February 22, 2013 9:39:02 AM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    Fascinating! You seem to have a very different version of flock than
    the ones we're used to. Could you run "rpm -qf $(which flock)" to figure
    out what package it's coming from? Perhaps there are multiple flocks on
    your system? We've tested with SLES11SP2 quite extensively, and have never
    seen this differing version of /usr/bin/flock before. Are you on SLES11
    SP2?

    The workaround is to either install CM manually (we call this "path B"
    in our docs) or to extract a certain jar and replace the script, which I'm
    hesitant to go into too much.

    Here's what I see on my test SLES machine:

    jenkins-sles11-1:~ # flock --version
    flock (util-linux 2.19.1)
    jenkins-sles11-1:~ # flock --help
    flock (util-linux 2.19.1)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version
    jenkins-sles11-1:~ # rpm -qf $(which flock)
    util-linux-2.19.1-6.29.3
    jenkins-sles11-1:/etc # cat issue

    Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r
    (\l).


    Thanks!

    -- Philip



    On Thu, Feb 21, 2013 at 7:41 PM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version: core-2.0-noarch:core-3.2-**
    noarch:core-4.0-noarch:core-2.**0-x86_64:core-3.2-x86_64:core-**
    4.0-x86_64:desktop-4.0-amd64:**desktop-4.0-noarch:graphics-2.**
    0-amd64:graphics-2.0-noarch:**graphics-3.2-amd64:graphics-3.**
    2-noarch:graphics-4.0-amd64:**graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh

    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger
    wrote:
    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a"
    or "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.****log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==============================****============================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg
    arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager
    cache...
    unknown packager , exiting
    closing logging file descriptor
    ==============================****============================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager
    is not installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is
    this?


    Regards,
    Mahesh

  • Mahesh Bengaluru at Feb 23, 2013 at 3:48 am
    Hello Philip*s* :)

    Sorry, My mistake.
    The problem was that the system where CM was installed was Suse Linux 11
    SP1, where as the nodes/hosts I was adding where on Suse Linux 10.
    Seems like that caused the problem.
    I reinstalled 11 SP1 on all the system & I was able to add the hosts.
    The installation was successful ???!!!

    It said successful, but then got the message:
    =============
    Inspector ran on all 0 hosts. The inspector failed to run on all hosts. 0
    hosts are running CDH3 and 0 hosts are running CDH4. Could not determine
    component versions. All checked Cloudera Management Daemons versions are
    consistent with the server.

    All checked Cloudera Management Agents versions are consistent with the
    server.

    ===========

    I googled & came across this:

    https://groups.google.com/a/cloudera.org/forum/?fromgroups#!topic/scm-users/ZTcVjHOBRJA

    answered by you.

    Tried the solution, but it dint work.

    The content of my cloudera-scm-agent.out is:

    =========================

    /usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha
    module is deprecated; use the hashlib module instead

    import sha

    /usr/lib64/cmf/agent/src/cmf/monitor/host/network_interfaces.py:11:
    DeprecationWarning: the sets module is deprecated

    from sets import Set

    [23/Feb/2013 07:57:54 +0000] 29986 MainThread agent ERROR Could not
    determine hostname or ip address; proceeding.

    Traceback (most recent call last):

    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1204, in parse_arguments

    ip_address = socket.gethostbyname(fqdn)

    gaierror: [Errno -2] Name or service not known

    usage: agent.py [-h] [--agent_dir AGENT_DIR]

    [--agent_httpd_port AGENT_HTTPD_PORT] --package_dir

    PACKAGE_DIR [--supervisord_path SUPERVISORD_PATH]

    [--supervisord_httpd_port SUPERVISORD_HTTPD_PORT]

    [--standalone STANDALONE] [--master MASTER]

    [--environment ENVIRONMENT] [--host_id HOST_ID]

    [--disable_supervisord_events] [--disable_eager_heartbeats]

    --hostname HOSTNAME --ip_address IP_ADDRESS [--use_tls]

    [--client_key_file CLIENT_KEY_FILE]

    [--client_cert_file CLIENT_CERT_FILE]

    [--verify_cert_file VERIFY_CERT_FILE]

    [--client_keypw_file CLIENT_KEYPW_FILE] [--logfile LOGFILE]

    [--optional_token] [--clear_agent_dir]

    agent.py: error: argument --hostname is required

    [23/Feb/2013 07:57:54 +0000] 29986 MainThread agent INFO Stopping agent...

    =============================

    I tried doing this:
    virtualenv /usr/lib/cmf/agent/build/env



    But got the message :

    virtualenv /usr/lib/cmf/agent/build/env
    If 'virtualenv' is not a typo you can run the following command to lookup
    the package that contains the binary:
    command-not-found virtualenv
    -bash: virtualenv: command not found



    Can you pls tell me what to do. If I am looking silly, its because I am
    very new to Linux :)



    Thanks & Regards,

    Mahesh




    On Saturday, February 23, 2013 12:26:30 AM UTC+5:30, Philip Langdale wrote:

    Sorry, slight clarification.

    Mahesh reported util-linux-ng 2.16
    and Phil reported util-linux 2.19.1

    So I had it the wrong way round

    --phil


    On 22 February 2013 10:31, Philip Langdale <phi...@cloudera.com<javascript:>
    wrote:
    Phil,

    You're not seeing it. You're seeing util-linux-ng 2.16 and Mahesh is
    seeing util-linux 2.19.1 (not ng).

    Mahesh, are you running SP1 or SP2? We don't support base SLES11.

    --phil


    On 22 February 2013 09:00, Philip Zeyliger <phi...@cloudera.com<javascript:>
    wrote:
    Hi Mahesh,

    Oddly, I spun up an instance of SLES11SP1 in EC2, and though I'm seeing
    the same version of flock that you're seeing, it has a different (correct)
    usage string. I'm wondering whether it's possible that there are multiple
    flock's on the path somehow.

    ip-172-25-2-4:~ # flock --help
    flock (util-linux-ng 2.16)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version

    Good luck with the manual install--let us know if we can help.


    On Thu, Feb 21, 2013 at 10:27 PM, Mahesh Bengaluru <
    mahesh.be...@gmail.com <javascript:>> wrote:
    Hi Philip,

    rpm -qf $(which flock)
    returned me

    util-linux-2.16-6.8.2

    I will try installing CM manually & let you know how it goes.

    Regards,
    Mahesh

    On Friday, February 22, 2013 9:39:02 AM UTC+5:30, Philip Zeyliger wrote:

    Hi Mahesh,

    Fascinating! You seem to have a very different version of flock
    than the ones we're used to. Could you run "rpm -qf $(which flock)" to
    figure out what package it's coming from? Perhaps there are multiple
    flocks on your system? We've tested with SLES11SP2 quite extensively, and
    have never seen this differing version of /usr/bin/flock before. Are you
    on SLES11 SP2?

    The workaround is to either install CM manually (we call this "path B"
    in our docs) or to extract a certain jar and replace the script, which I'm
    hesitant to go into too much.

    Here's what I see on my test SLES machine:

    jenkins-sles11-1:~ # flock --version
    flock (util-linux 2.19.1)
    jenkins-sles11-1:~ # flock --help
    flock (util-linux 2.19.1)
    Usage: flock [-sxun][-w #] fd#
    flock [-sxon][-w #] file [-c] command...
    flock [-sxon][-w #] directory [-c] command...
    -s --shared Get a shared lock
    -x --exclusive Get an exclusive lock
    -u --unlock Remove a lock
    -n --nonblock Fail rather than wait
    -w --timeout Wait for a limited amount of time
    -o --close Close file descriptor before running command
    -c --command Run a single command string through the shell
    -h --help Display this text
    -V --version Display version
    jenkins-sles11-1:~ # rpm -qf $(which flock)
    util-linux-2.19.1-6.29.3
    jenkins-sles11-1:/etc # cat issue

    Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r
    (\l).


    Thanks!

    -- Philip



    On Thu, Feb 21, 2013 at 7:41 PM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi Philip,

    The details are as follows:

    *lsb_release -a*
    LSB Version: core-2.0-noarch:core-3.2-**
    noarch:core-4.0-noarch:core-2.**0-x86_64:core-3.2-x86_64:core-**
    4.0-x86_64:desktop-4.0-amd64:**desktop-4.0-noarch:graphics-2.**
    0-amd64:graphics-2.0-noarch:**graphics-3.2-amd64:graphics-3.**
    2-noarch:graphics-4.0-amd64:**graphics-4.0-noarch
    Distributor ID: SUSE LINUX
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    Release: 11
    Codename: n/a
    *flock --version*
    flock (util-linux-ng 2.16)

    Thanks & Regards,
    Mahesh

    On Thursday, February 21, 2013 10:35:07 PM UTC+5:30, Philip Zeyliger
    wrote:
    Hi Mahesh,

    What OS are you using? (e.g., what's the output of "lsb_release -a"
    or "cat /etc/issue"; also "flock --version"). The usage output of flock
    suggests that you're using an OS which has a different version of flock
    than the one's we're used to.

    As for your second question, check the output of
    /var/log/cloudera-scm-agent/*.****log; that'll give us a hint.

    Thanks,

    -- Philip


    On Thu, Feb 21, 2013 at 4:28 AM, Mahesh Bengaluru <
    mahesh.be...@gmail.com> wrote:
    Hi,

    I have 2 queries.

    1)
    I was able to install the Cloudera Manager successfully.
    When I try to add a host, I get the error message as below.

    ==============================****============================
    /tmp/scm_prepare_node.iBS24382
    using SSH_CLIENT to get the SCM hostname: 10.18.xx.yy 16178 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    Usage flock [--shared | --timeout=seconds] filename command {arg
    arg...}
    *END (2) *
    could not acquire installation lock, giving up
    Reverting changes...
    rollback started
    Removing package repositories... Cleaning the package manager
    cache...
    unknown packager , exiting
    closing logging file descriptor
    ==============================****============================

    Can somebody help me resolve this?

    2)
    This is when I give the IP of a different system where the Manager
    is not installed.
    But when I provide the IP of the same system where the Manager is
    installed, it installs successfully.
    But I am not able to see this is the list of managed hosts. Why is
    this?


    Regards,
    Mahesh

  • Mahesh Bengaluru at Feb 23, 2013 at 4:43 am
    To add to the earlier post.
    I came across this discussion:
    http://grokbase.com/t/cloudera/scm-users/12cc4m3020/inspector-ran-on-all-0-hosts

    I checked if the agents can telnet the server on 7182 & 7180. They can.
    But still getting the same inspector ran on 0 hosts message.

    Thanks & Regards,
    Mahesh

    On Saturday, February 23, 2013 9:18:29 AM UTC+5:30, Mahesh Bengaluru wrote:

    Hello Philip*s* :)

    Sorry, My mistake.
    The problem was that the system where CM was installed was Suse Linux 11
    SP1, where as the nodes/hosts I was adding where on Suse Linux 10.
    Seems like that caused the problem.
    I reinstalled 11 SP1 on all the system & I was able to add the hosts.
    The installation was successful ???!!!

    It said successful, but then got the message:
    =============
    Inspector ran on all 0 hosts. The inspector failed to run on all
    hosts. 0 hosts are running CDH3 and 0 hosts are running CDH4. Could not
    determine component versions. All checked Cloudera Management Daemons
    versions are consistent with the server.

    All checked Cloudera Management Agents versions are consistent with the
    server.

    ===========

    I googled & came across this:


    https://groups.google.com/a/cloudera.org/forum/?fromgroups#!topic/scm-users/ZTcVjHOBRJA

    answered by you.

    Tried the solution, but it dint work.

    The content of my cloudera-scm-agent.out is:

    =========================

    /usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha
    module is deprecated; use the hashlib module instead

    import sha

    /usr/lib64/cmf/agent/src/cmf/monitor/host/network_interfaces.py:11:
    DeprecationWarning: the sets module is deprecated

    from sets import Set

    [23/Feb/2013 07:57:54 +0000] 29986 MainThread agent ERROR Could not
    determine hostname or ip address; proceeding.

    Traceback (most recent call last):

    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1204, in parse_arguments

    ip_address = socket.gethostbyname(fqdn)

    gaierror: [Errno -2] Name or service not known

    usage: agent.py [-h] [--agent_dir AGENT_DIR]

    [--agent_httpd_port AGENT_HTTPD_PORT] --package_dir

    PACKAGE_DIR [--supervisord_path SUPERVISORD_PATH]

    [--supervisord_httpd_port SUPERVISORD_HTTPD_PORT]

    [--standalone STANDALONE] [--master MASTER]

    [--environment ENVIRONMENT] [--host_id HOST_ID]

    [--disable_supervisord_events] [--disable_eager_heartbeats]

    --hostname HOSTNAME --ip_address IP_ADDRESS [--use_tls]

    [--client_key_file CLIENT_KEY_FILE]

    [--client_cert_file CLIENT_CERT_FILE]

    [--verify_cert_file VERIFY_CERT_FILE]

    [--client_keypw_file CLIENT_KEYPW_FILE] [--logfile LOGFILE]

    [--optional_token] [--clear_agent_dir]

    agent.py: error: argument --hostname is required

    [23/Feb/2013 07:57:54 +0000] 29986 MainThread agent INFO Stopping agent...

    =============================

    I tried doing this:
    virtualenv /usr/lib/cmf/agent/build/env



    But got the message :

    virtualenv /usr/lib/cmf/agent/build/env
    If 'virtualenv' is not a typo you can run the following command to lookup
    the package that contains the binary:
    command-not-found virtualenv
    -bash: virtualenv: command not found



    Can you pls tell me what to do. If I am looking silly, its because I am
    very new to Linux :)



    Thanks & Regards,

    Mahesh

  • Philip Zeyliger at Feb 23, 2013 at 8:07 pm
    Yes, we only support SLES11SP1 and newer.

    This:

    ip_address = socket.gethostbyname(fqdn)
    gaierror: [Errno -2] Name or service not known

    Means that DNS is not working. Run this command until you get it to
    output something reasonable:

    $ python -c 'import socket; print socket.getfqdn(),
    socket.gethostbyname(socket.getfqdn())'
    p0428.mtv.cloudera.com 172.29.122.20




    On Fri, Feb 22, 2013 at 8:43 PM, Mahesh Bengaluru wrote:

    To add to the earlier post.
    I came across this discussion:

    http://grokbase.com/t/cloudera/scm-users/12cc4m3020/inspector-ran-on-all-0-hosts

    I checked if the agents can telnet the server on 7182 & 7180. They can.
    But still getting the same inspector ran on 0 hosts message.

    Thanks & Regards,
    Mahesh


    On Saturday, February 23, 2013 9:18:29 AM UTC+5:30, Mahesh Bengaluru
    wrote:
    Hello Philip*s* :)

    Sorry, My mistake.
    The problem was that the system where CM was installed was Suse Linux 11
    SP1, where as the nodes/hosts I was adding where on Suse Linux 10.
    Seems like that caused the problem.
    I reinstalled 11 SP1 on all the system & I was able to add the hosts.
    The installation was successful ???!!!

    It said successful, but then got the message:
    =============
    Inspector ran on all 0 hosts. The inspector failed to run on all
    hosts. 0 hosts are running CDH3 and 0 hosts are running CDH4. Could
    not determine component versions. All checked Cloudera Management
    Daemons versions are consistent with the server.

    All checked Cloudera Management Agents versions are consistent with the
    server.

    ===========

    I googled & came across this:

    https://groups.google.com/a/**cloudera.org/forum/?**
    fromgroups#!topic/scm-users/**ZTcVjHOBRJA<https://groups.google.com/a/cloudera.org/forum/?fromgroups#!topic/scm-users/ZTcVjHOBRJA>

    answered by you.

    Tried the solution, but it dint work.

    The content of my cloudera-scm-agent.out is:

    =========================

    /usr/lib64/cmf/agent/src/cmf/**agent.py:24: DeprecationWarning: the sha
    module is deprecated; use the hashlib module instead

    import sha

    /usr/lib64/cmf/agent/src/cmf/**monitor/host/network_**interfaces.py:11:
    DeprecationWarning: the sets module is deprecated

    from sets import Set

    [23/Feb/2013 07:57:54 +0000] 29986 MainThread agent ERROR Could not
    determine hostname or ip address; proceeding.

    Traceback (most recent call last):

    File "/usr/lib64/cmf/agent/src/cmf/**agent.py", line 1204, in
    parse_arguments

    ip_address = socket.gethostbyname(fqdn)

    gaierror: [Errno -2] Name or service not known

    usage: agent.py [-h] [--agent_dir AGENT_DIR]

    [--agent_httpd_port AGENT_HTTPD_PORT] --package_dir

    PACKAGE_DIR [--supervisord_path SUPERVISORD_PATH]

    [--supervisord_httpd_port SUPERVISORD_HTTPD_PORT]

    [--standalone STANDALONE] [--master MASTER]

    [--environment ENVIRONMENT] [--host_id HOST_ID]

    [--disable_supervisord_events] [--disable_eager_heartbeats]

    --hostname HOSTNAME --ip_address IP_ADDRESS [--use_tls]

    [--client_key_file CLIENT_KEY_FILE]

    [--client_cert_file CLIENT_CERT_FILE]

    [--verify_cert_file VERIFY_CERT_FILE]

    [--client_keypw_file CLIENT_KEYPW_FILE] [--logfile LOGFILE]

    [--optional_token] [--clear_agent_dir]

    agent.py: error: argument --hostname is required

    [23/Feb/2013 07:57:54 +0000] 29986 MainThread agent INFO Stopping agent...

    =============================

    I tried doing this:
    virtualenv /usr/lib/cmf/agent/build/env



    But got the message :

    virtualenv /usr/lib/cmf/agent/build/env
    If 'virtualenv' is not a typo you can run the following command to lookup
    the package that contains the binary:
    command-not-found virtualenv
    -bash: virtualenv: command not found



    Can you pls tell me what to do. If I am looking silly, its because I am
    very new to Linux :)



    Thanks & Regards,

    Mahesh

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedFeb 21, '13 at 12:28p
activeFeb 23, '13 at 8:07p
posts11
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase