FAQ
Hi,

I installed the latest version of Cloudera Manager (4.5) on my Ubuntu 12.04.
While I try to install my other host, i got stuck by "Failed to create
temporary directory." on my all client.

I try to get the log by "retry" on one host and get the server log as below.
I've checked my root password is correct i even use private key but in vain.
I also check the temp dir on my host and it also exist.

Any advice ? Thanks!

=======
2013-02-27 02:50:37,335 INFO
[1299979108@scm-web-42:node.NodeConfiguratorService@218] Retrying
configurator with id 1
2013-02-27 02:50:37,338 INFO
[1299979108@scm-web-42:node.NodeConfiguratorService@199] Submitted
configurator for 10.1.193.54 with id 2
2013-02-27 02:50:37,339 INFO
[NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512] 10.1.193.54:
Transitioning from INIT (PT0.001S) to CONNECT
2013-02-27 02:50:37,341 INFO
[NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client identity
string: SSH-2.0-SSHJ_0_8
2013-02-27 02:50:37,346 INFO
[NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server identity
string: SSH-2.0-dropbear_2011.54
2013-02-27 02:50:37,346 INFO
[NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
SSH_MSG_KEXINIT
2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357] Received
SSH_MSG_KEXINIT
2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
SSH_MSG_KEXDH_INIT
2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370] Received
kex followup data
2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
SSH_MSG_KEXDH_REPLY
2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203] Sending
SSH_MSG_NEWKEYS
2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385] Received
SSH_MSG_NEWKEYS
2013-02-27 02:50:37,471 INFO
[NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took 0.125
seconds
2013-02-27 02:50:37,471 INFO
[NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512] 10.1.193.54:
Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
2013-02-27 02:50:37,508 INFO
[NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
service to ssh-userauth
2013-02-27 02:50:37,508 INFO
[NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying `password`
auth...
2013-02-27 02:50:37,508 INFO
[NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting password for
[AccountResource] root@10.1.193.54
2013-02-27 02:50:37,513 INFO
[NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
successful
2013-02-27 02:50:37,513 INFO
[NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
service to ssh-connection
2013-02-27 02:50:37,513 INFO
[NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512] 10.1.193.54:
Transitioning from AUTHENTICATE (PT0.042S) to MAKE_TEMP_DIR
2013-02-27 02:50:37,514 INFO
[NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
`session` channel (#0)
2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
Initialized - < session channel: id=0, recipient=0,
localWin=[winSize=2097152], remoteWin=[winSize=65536] >
2013-02-27 02:50:37,514 INFO
[NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
request for `pty-req`
2013-02-27 02:50:37,515 INFO
[NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing mktemp -d
/tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
2013-02-27 02:50:37,516 INFO
[NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to exec
`mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
2013-02-27 02:50:37,516 INFO
[NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
request for `exec`
2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got EOF
2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got chan
request for `exit-status`
2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got close
2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425] Sending EOF
2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287] Sending
close
2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
Forgetting `session` channel (#0)
2013-02-27 02:50:37,521 INFO
[NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533] 10.1.193.54:
Setting MAKE_TEMP_DIR as failed and done state
=======

Search Discussions

  • bc Wong at Feb 27, 2013 at 6:42 pm
    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc
    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen wrote:

    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my Ubuntu
    12.04.
    While I try to install my other host, i got stuck by "Failed to create
    temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log as
    below.
    I've checked my root password is correct i even use private key but in
    vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@218] Retrying configurator with id 1
    2013-02-27 02:50:37,338 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@199] Submitted configurator for 10.1.193.54
    with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512] 10.1.193.54:
    Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server identity
    string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took
    0.125 seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512] 10.1.193.54:
    Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying `password`
    auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting password
    for [AccountResource] root@10.1.193.54
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
    successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512] 10.1.193.54:
    Transitioning from AUTHENTICATE (PT0.042S) to MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing mktemp
    -d /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to
    exec `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425] Sending
    EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287] Sending
    close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533] 10.1.193.54:
    Setting MAKE_TEMP_DIR as failed and done state
    =======
  • ZZ at Mar 1, 2013 at 6:58 am
    Hi BC,

    I tested on my server, both `echo $?` command return '0'.
    (I test the command by 'root')

    On Thu, Feb 28, 2013 at 2:42 AM, bc Wong wrote:

    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc

    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen wrote:

    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my Ubuntu
    12.04.
    While I try to install my other host, i got stuck by "Failed to create
    temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log as
    below.
    I've checked my root password is correct i even use private key but in
    vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@218] Retrying configurator with id 1
    2013-02-27 02:50:37,338 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@199] Submitted configurator for
    10.1.193.54 with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server identity
    string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203]
    Sending SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took
    0.125 seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying `password`
    auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting password
    for [AccountResource] root@10.1.193.54
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
    successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from AUTHENTICATE (PT0.042S) to MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing mktemp
    -d /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to
    exec `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got
    chan request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got
    close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425] Sending
    EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287] Sending
    close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533]
    10.1.193.54: Setting MAKE_TEMP_DIR as failed and done state
    =======

    --
    Zz
  • bc Wong at Mar 1, 2013 at 8:10 am
    I'm interested in the verbatim stdout of the commands, not just the return
    code. Verbatim as in the created directory name, new lines, or any possible
    warnings. Could you try that again?

    Cheers,
    bc
    On Thu, Feb 28, 2013 at 10:58 PM, ZZ wrote:

    Hi BC,

    I tested on my server, both `echo $?` command return '0'.
    (I test the command by 'root')

    On Thu, Feb 28, 2013 at 2:42 AM, bc Wong wrote:

    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc

    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen wrote:

    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my Ubuntu
    12.04.
    While I try to install my other host, i got stuck by "Failed to create
    temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log as
    below.
    I've checked my root password is correct i even use private key but in
    vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@218] Retrying configurator with id 1
    2013-02-27 02:50:37,338 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@199] Submitted configurator for
    10.1.193.54 with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client
    identity string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server
    identity string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203]
    Sending SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took
    0.125 seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying `password`
    auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting password
    for [AccountResource] root@10.1.193.54
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
    successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from AUTHENTICATE (PT0.042S) to MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing mktemp
    -d /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to
    exec `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got
    chan request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got
    close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425]
    Sending EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287]
    Sending close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533]
    10.1.193.54: Setting MAKE_TEMP_DIR as failed and done state
    =======

    --
    Zz
  • ZZ at Mar 1, 2013 at 8:14 am
    Sure! I retry those command as below,

    ======
    root@CDH-Manager:~# sudo mktemp -d /tmp/foo.XXXXXXXX
    /tmp/foo.jlxjEoWJ
    root@CDH-Manager:~# echo $?

    root@CDH-Manager:~# sudo su -
    root@CDH-Manager:~# mktemp -d /tmp/bar.XXXXXXXX
    /tmp/bar.xxfV2wk2
    root@CDH-Manager:~# echo $?

    ======

    On Fri, Mar 1, 2013 at 4:10 PM, bc Wong wrote:

    I'm interested in the verbatim stdout of the commands, not just the return
    code. Verbatim as in the created directory name, new lines, or any possible
    warnings. Could you try that again?

    Cheers,
    bc

    On Thu, Feb 28, 2013 at 10:58 PM, ZZ wrote:

    Hi BC,

    I tested on my server, both `echo $?` command return '0'.
    (I test the command by 'root')

    On Thu, Feb 28, 2013 at 2:42 AM, bc Wong wrote:

    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc

    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen wrote:

    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my Ubuntu
    12.04.
    While I try to install my other host, i got stuck by "Failed to create
    temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log as
    below.
    I've checked my root password is correct i even use private key but in
    vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@218] Retrying configurator with id 1
    2013-02-27 02:50:37,338 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@199] Submitted configurator for
    10.1.193.54 with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client
    identity string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server
    identity string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203]
    Sending SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took
    0.125 seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting
    active service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying
    `password` auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting
    password for [AccountResource] root@10.1.193.54
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
    successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting
    active service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from AUTHENTICATE (PT0.042S) to
    MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing
    mktemp -d /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to
    exec `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got
    EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got
    chan request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got
    close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425]
    Sending EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287]
    Sending close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533]
    10.1.193.54: Setting MAKE_TEMP_DIR as failed and done state
    =======

    --
    Zz

    --
    Zz
  • Philip Langdale at Mar 1, 2013 at 6:21 pm
    ZZ,

    I notice in the log that you're using dropbear as your ssh server. This is
    not the normal thing to use on a desktop or server Ubuntu machine.
    It also leads me to wonder whether you're using busybox as well, which
    would provide an mktemp that's different from the usual one in coreutils
    that we expect.

    I'd ask, to keep things consistent, if you could switch to openssh server
    and coreutils (if you're using busybox) and retry?

    Thanks,

    --phil

    On 1 March 2013 16:14, ZZ wrote:

    Sure! I retry those command as below,

    ======
    root@CDH-Manager:~# sudo mktemp -d /tmp/foo.XXXXXXXX
    /tmp/foo.jlxjEoWJ
    root@CDH-Manager:~# echo $?

    root@CDH-Manager:~# sudo su -
    root@CDH-Manager:~# mktemp -d /tmp/bar.XXXXXXXX
    /tmp/bar.xxfV2wk2
    root@CDH-Manager:~# echo $?

    ======

    On Fri, Mar 1, 2013 at 4:10 PM, bc Wong wrote:

    I'm interested in the verbatim stdout of the commands, not just the
    return code. Verbatim as in the created directory name, new lines, or any
    possible warnings. Could you try that again?

    Cheers,
    bc

    On Thu, Feb 28, 2013 at 10:58 PM, ZZ wrote:

    Hi BC,

    I tested on my server, both `echo $?` command return '0'.
    (I test the command by 'root')

    On Thu, Feb 28, 2013 at 2:42 AM, bc Wong wrote:

    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc

    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen wrote:

    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my Ubuntu
    12.04.
    While I try to install my other host, i got stuck by "Failed to
    create temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log as
    below.
    I've checked my root password is correct i even use private key but in
    vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@218] Retrying configurator with id 1
    2013-02-27 02:50:37,338 INFO [1299979108@scm-web-42
    :node.NodeConfiguratorService@199] Submitted configurator for
    10.1.193.54 with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client
    identity string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server
    identity string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203]
    Sending SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took
    0.125 seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting
    active service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying
    `password` auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting
    password for [AccountResource] root@10.1.193.54
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password`
    auth successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting
    active service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from AUTHENTICATE (PT0.042S) to
    MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending
    channel request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing
    mktemp -d /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request
    to exec `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending
    channel request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got
    EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got
    chan request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got
    close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425]
    Sending EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287]
    Sending close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533]
    10.1.193.54: Setting MAKE_TEMP_DIR as failed and done state
    =======

    --
    Zz

    --
    Zz
  • Kevin Moulart at Jan 2, 2014 at 10:58 am
    Hi,

    I have exactly the same logs here after upgrading to CM 4.8, I can't
    upgrade the hosts :

    tail -n 100 /var/log/cloudera-scm-server/cloudera-scm-server.log
    2014-01-02 11:48:05,663 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@263] Creating request
    with id 1
    2014-01-02 11:48:05,664 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@190] Adding
    pubkey-based configurator for node03.bigdata
    2014-01-02 11:48:05,665 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@204] Submitted
    configurator for node03.bigdata with id 0
    2014-01-02 11:48:05,665 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@512]
    node03.bigdata: Transitioning from INIT (PT0.001S) to CONNECT
    2014-01-02 11:48:05,665 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@190] Adding
    pubkey-based configurator for node02.bigdata
    2014-01-02 11:48:05,666 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@204] Submitted
    configurator for node02.bigdata with id 1
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@512]
    node02.bigdata: Transitioning from INIT (PT0.001S) to CONNECT
    2014-01-02 11:48:05,666 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@190] Adding
    pubkey-based configurator for node01.bigdata
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2014-01-02 11:48:05,666 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@204] Submitted
    configurator for node01.bigdata with id 2
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@512]
    node01.bigdata: Transitioning from INIT (PT0S) to CONNECT
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2014-01-02 11:48:05,667 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@161] Server identity
    string: SSH-2.0-OpenSSH_5.3
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-0:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@161] Server identity
    string: SSH-2.0-OpenSSH_5.3
    2014-01-02 11:48:05,672 INFO [reader:transport.KeyExchanger@357] Received
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-1:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,673 INFO [reader:transport.KeyExchanger@357] Received
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,674 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@161] Server identity
    string: SSH-2.0-OpenSSH_5.3
    2014-01-02 11:48:05,674 INFO
    [NodeConfiguratorThread-1-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,674 INFO [reader:transport.KeyExchanger@357] Received
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,697 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2014-01-02 11:48:05,697 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2014-01-02 11:48:05,698 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2014-01-02 11:48:05,702 INFO [reader:transport.KeyExchanger@370] Received
    kex followup data
    2014-01-02 11:48:05,702 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2014-01-02 11:48:05,702 INFO [reader:transport.KeyExchanger@370] Received
    kex followup data
    2014-01-02 11:48:05,702 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2014-01-02 11:48:05,704 INFO [reader:transport.KeyExchanger@370] Received
    kex followup data
    2014-01-02 11:48:05,704 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@385] Received
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@385] Received
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,728 INFO
    [NodeConfiguratorThread-1-2:node.CmfSSHClient@686] Key exchange took 0.054
    seconds
    2014-01-02 11:48:05,728 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@512]
    node01.bigdata: Transitioning from CONNECT (PT0.062S) to AUTHENTICATE
    2014-01-02 11:48:05,728 INFO
    [NodeConfiguratorThread-1-0:node.CmfSSHClient@686] Key exchange took 0.056
    seconds
    2014-01-02 11:48:05,729 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@512]
    node03.bigdata: Transitioning from CONNECT (PT0.064S) to AUTHENTICATE
    2014-01-02 11:48:05,729 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,729 INFO [reader:transport.KeyExchanger@385] Received
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,729 INFO
    [NodeConfiguratorThread-1-1:node.CmfSSHClient@686] Key exchange took 0.057
    seconds
    2014-01-02 11:48:05,730 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@512]
    node02.bigdata: Transitioning from CONNECT (PT0.064S) to AUTHENTICATE
    2014-01-02 11:48:05,768 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2014-01-02 11:48:05,768 INFO
    [NodeConfiguratorThread-1-0:userauth.UserAuthImpl@85] Trying `publickey`
    auth...
    2014-01-02 11:48:05,769 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2014-01-02 11:48:05,770 INFO
    [NodeConfiguratorThread-1-1:userauth.UserAuthImpl@85] Trying `publickey`
    auth...
    2014-01-02 11:48:05,770 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2014-01-02 11:48:05,770 INFO
    [NodeConfiguratorThread-1-2:userauth.UserAuthImpl@85] Trying `publickey`
    auth...
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:userauth.UserAuthImpl@102] `publickey` auth
    successful
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@512]
    node02.bigdata: Transitioning from AUTHENTICATE (PT0.055S) to MAKE_TEMP_DIR
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2014-01-02 11:48:05,786 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=0] >
    2014-01-02 11:48:05,786 INFO
    [NodeConfiguratorThread-1-1:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2014-01-02 11:48:05,788 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfigurator@598] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on node02.bigdata
    2014-01-02 11:48:05,788 INFO
    [NodeConfiguratorThread-1-1:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2014-01-02 11:48:05,788 INFO
    [NodeConfiguratorThread-1-1:direct.SessionChannel@372] Sending channel
    request for `exec`
    2014-01-02 11:48:05,789 INFO [reader:direct.SessionChannel@326] Received
    window adjustment for 2097152 bytes
    2014-01-02 11:48:05,791 INFO
    [NodeConfiguratorThread-1-2:userauth.UserAuthImpl@102] `publickey` auth
    successful
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@512]
    node01.bigdata: Transitioning from AUTHENTICATE (PT0.064S) to MAKE_TEMP_DIR
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:userauth.UserAuthImpl@102] `publickey` auth
    successful
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@512]
    node03.bigdata: Transitioning from AUTHENTICATE (PT0.063S) to MAKE_TEMP_DIR
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2014-01-02 11:48:05,793 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=0] >
    2014-01-02 11:48:05,794 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=0] >
    2014-01-02 11:48:05,794 INFO
    [NodeConfiguratorThread-1-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2014-01-02 11:48:05,794 INFO
    [NodeConfiguratorThread-1-0:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2014-01-02 11:48:05,794 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfigurator@598] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on node01.bigdata
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfigurator@598] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on node03.bigdata
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-0:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-2:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-0:direct.SessionChannel@372] Sending channel
    request for `exec`
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2014-01-02 11:48:05,796 INFO [reader:direct.SessionChannel@326] Received
    window adjustment for 2097152 bytes
    2014-01-02 11:48:05,796 INFO [reader:direct.SessionChannel@326] Received
    window adjustment for 2097152 bytes
    2014-01-02 11:48:05,816 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2014-01-02 11:48:05,816 INFO [reader:direct.SessionChannel@408] Got EOF
    2014-01-02 11:48:05,817 INFO [reader:direct.SessionChannel@223] Got close
    2014-01-02 11:48:05,817 INFO [reader:direct.SessionChannel@425] Sending EOF
    2014-01-02 11:48:05,817 INFO [reader:direct.SessionChannel@287] Sending
    close
    2014-01-02 11:48:05,817 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2014-01-02 11:48:05,818 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@533]
    node02.bigdata: Setting MAKE_TEMP_DIR as failed and done state
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@408] Got EOF
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@223] Got close
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@425] Sending EOF
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@287] Sending
    close
    2014-01-02 11:48:05,829 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2014-01-02 11:48:05,830 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@533]
    node03.bigdata: Setting MAKE_TEMP_DIR as failed and done state
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@408] Got EOF
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@223] Got close
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@425] Sending EOF
    2014-01-02 11:48:05,852 INFO [reader:direct.SessionChannel@287] Sending
    close
    2014-01-02 11:48:05,852 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2014-01-02 11:48:05,852 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@533]
    node01.bigdata: Setting MAKE_TEMP_DIR as failed and done state


    Did you manage to find a solution to the problem ?

    Le vendredi 1 mars 2013 19:21:16 UTC+1, Philip Langdale a écrit :
    ZZ,

    I notice in the log that you're using dropbear as your ssh server. This is
    not the normal thing to use on a desktop or server Ubuntu machine.
    It also leads me to wonder whether you're using busybox as well, which
    would provide an mktemp that's different from the usual one in coreutils
    that we expect.

    I'd ask, to keep things consistent, if you could switch to openssh server
    and coreutils (if you're using busybox) and retry?

    Thanks,

    --phil

    On 1 March 2013 16:14, ZZ <chy...@gmail.com <javascript:>> wrote:

    Sure! I retry those command as below,

    ======
    root@CDH-Manager:~# sudo mktemp -d /tmp/foo.XXXXXXXX
    /tmp/foo.jlxjEoWJ
    root@CDH-Manager:~# echo $?

    root@CDH-Manager:~# sudo su -
    root@CDH-Manager:~# mktemp -d /tmp/bar.XXXXXXXX
    /tmp/bar.xxfV2wk2
    root@CDH-Manager:~# echo $?

    ======


    On Fri, Mar 1, 2013 at 4:10 PM, bc Wong <bcwa...@cloudera.com<javascript:>
    wrote:
    I'm interested in the verbatim stdout of the commands, not just the
    return code. Verbatim as in the created directory name, new lines, or any
    possible warnings. Could you try that again?

    Cheers,
    bc


    On Thu, Feb 28, 2013 at 10:58 PM, ZZ <chy...@gmail.com <javascript:>>wrote:
    Hi BC,

    I tested on my server, both `echo $?` command return '0'.
    (I test the command by 'root')


    On Thu, Feb 28, 2013 at 2:42 AM, bc Wong <bcwa...@cloudera.com<javascript:>
    wrote:
    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc


    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen <chy...@gmail.com<javascript:>
    wrote:
    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my Ubuntu
    12.04.
    While I try to install my other host, i got stuck by "Failed to
    create temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log as
    below.
    I've checked my root password is correct i even use private key but
    in vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO
    [1299979108@scm-web-42:node.NodeConfiguratorService@218] Retrying
    configurator with id 1
    2013-02-27 02:50:37,338 INFO
    [1299979108@scm-web-42:node.NodeConfiguratorService@199] Submitted
    configurator for 10.1.193.54 with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server identity
    string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203]
    Sending SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took 0.125
    seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying `password`
    auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting password for
    [AccountResource] ro...@10.1.193.54 <javascript:>
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
    successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from AUTHENTICATE (PT0.042S) to
    MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got
    EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got
    chan request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got
    close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425]
    Sending EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287]
    Sending close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533]
    10.1.193.54: Setting MAKE_TEMP_DIR as failed and done state
    =======

    --
    Zz

    --
    Zz
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Kevin Moulart at Jan 3, 2014 at 8:52 am
    Nevermind, I upgraded each node manually using the cloudera-manager.repo
    and yum, and although the automated upgrade process still doesn't works,
    the cluster now works as expected with CM 4.8.

    Le jeudi 2 janvier 2014 11:58:34 UTC+1, Kevin Moulart a écrit :
    Hi,

    I have exactly the same logs here after upgrading to CM 4.8, I can't
    upgrade the hosts :

    tail -n 100 /var/log/cloudera-scm-server/cloudera-scm-server.log
    2014-01-02 11:48:05,663 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@263] Creating request
    with id 1
    2014-01-02 11:48:05,664 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@190] Adding
    pubkey-based configurator for node03.bigdata
    2014-01-02 11:48:05,665 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@204] Submitted
    configurator for node03.bigdata with id 0
    2014-01-02 11:48:05,665 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@512]
    node03.bigdata: Transitioning from INIT (PT0.001S) to CONNECT
    2014-01-02 11:48:05,665 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@190] Adding
    pubkey-based configurator for node02.bigdata
    2014-01-02 11:48:05,666 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@204] Submitted
    configurator for node02.bigdata with id 1
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@512]
    node02.bigdata: Transitioning from INIT (PT0.001S) to CONNECT
    2014-01-02 11:48:05,666 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@190] Adding
    pubkey-based configurator for node01.bigdata
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2014-01-02 11:48:05,666 INFO
    [1671934774@scm-web-14:node.NodeConfiguratorService@204] Submitted
    configurator for node01.bigdata with id 2
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@512]
    node01.bigdata: Transitioning from INIT (PT0S) to CONNECT
    2014-01-02 11:48:05,666 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2014-01-02 11:48:05,667 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@161] Server identity
    string: SSH-2.0-OpenSSH_5.3
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-0:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@161] Server identity
    string: SSH-2.0-OpenSSH_5.3
    2014-01-02 11:48:05,672 INFO [reader:transport.KeyExchanger@357] Received
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,672 INFO
    [NodeConfiguratorThread-1-1:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,673 INFO [reader:transport.KeyExchanger@357] Received
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,674 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@161] Server identity
    string: SSH-2.0-OpenSSH_5.3
    2014-01-02 11:48:05,674 INFO
    [NodeConfiguratorThread-1-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,674 INFO [reader:transport.KeyExchanger@357] Received
    SSH_MSG_KEXINIT
    2014-01-02 11:48:05,697 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2014-01-02 11:48:05,697 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2014-01-02 11:48:05,698 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2014-01-02 11:48:05,702 INFO [reader:transport.KeyExchanger@370] Received
    kex followup data
    2014-01-02 11:48:05,702 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2014-01-02 11:48:05,702 INFO [reader:transport.KeyExchanger@370] Received
    kex followup data
    2014-01-02 11:48:05,702 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2014-01-02 11:48:05,704 INFO [reader:transport.KeyExchanger@370] Received
    kex followup data
    2014-01-02 11:48:05,704 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@385] Received
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,727 INFO [reader:transport.KeyExchanger@385] Received
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,728 INFO
    [NodeConfiguratorThread-1-2:node.CmfSSHClient@686] Key exchange took 0.054
    seconds
    2014-01-02 11:48:05,728 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@512]
    node01.bigdata: Transitioning from CONNECT (PT0.062S) to AUTHENTICATE
    2014-01-02 11:48:05,728 INFO
    [NodeConfiguratorThread-1-0:node.CmfSSHClient@686] Key exchange took 0.056
    seconds
    2014-01-02 11:48:05,729 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@512]
    node03.bigdata: Transitioning from CONNECT (PT0.064S) to AUTHENTICATE
    2014-01-02 11:48:05,729 INFO [reader:transport.KeyExchanger@203] Sending
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,729 INFO [reader:transport.KeyExchanger@385] Received
    SSH_MSG_NEWKEYS
    2014-01-02 11:48:05,729 INFO
    [NodeConfiguratorThread-1-1:node.CmfSSHClient@686] Key exchange took 0.057
    seconds
    2014-01-02 11:48:05,730 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@512]
    node02.bigdata: Transitioning from CONNECT (PT0.064S) to AUTHENTICATE
    2014-01-02 11:48:05,768 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2014-01-02 11:48:05,768 INFO
    [NodeConfiguratorThread-1-0:userauth.UserAuthImpl@85] Trying `publickey`
    auth...
    2014-01-02 11:48:05,769 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2014-01-02 11:48:05,770 INFO
    [NodeConfiguratorThread-1-1:userauth.UserAuthImpl@85] Trying `publickey`
    auth...
    2014-01-02 11:48:05,770 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2014-01-02 11:48:05,770 INFO
    [NodeConfiguratorThread-1-2:userauth.UserAuthImpl@85] Trying `publickey`
    auth...
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:userauth.UserAuthImpl@102] `publickey` auth
    successful
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@512]
    node02.bigdata: Transitioning from AUTHENTICATE (PT0.055S) to MAKE_TEMP_DIR
    2014-01-02 11:48:05,785 INFO
    [NodeConfiguratorThread-1-1:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2014-01-02 11:48:05,786 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=0] >
    2014-01-02 11:48:05,786 INFO
    [NodeConfiguratorThread-1-1:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2014-01-02 11:48:05,788 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfigurator@598] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on node02.bigdata
    2014-01-02 11:48:05,788 INFO
    [NodeConfiguratorThread-1-1:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2014-01-02 11:48:05,788 INFO
    [NodeConfiguratorThread-1-1:direct.SessionChannel@372] Sending channel
    request for `exec`
    2014-01-02 11:48:05,789 INFO [reader:direct.SessionChannel@326] Received
    window adjustment for 2097152 bytes
    2014-01-02 11:48:05,791 INFO
    [NodeConfiguratorThread-1-2:userauth.UserAuthImpl@102] `publickey` auth
    successful
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@512]
    node01.bigdata: Transitioning from AUTHENTICATE (PT0.064S) to MAKE_TEMP_DIR
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:userauth.UserAuthImpl@102] `publickey` auth
    successful
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@512]
    node03.bigdata: Transitioning from AUTHENTICATE (PT0.063S) to MAKE_TEMP_DIR
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-0:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2014-01-02 11:48:05,792 INFO
    [NodeConfiguratorThread-1-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2014-01-02 11:48:05,793 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=0] >
    2014-01-02 11:48:05,794 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=0] >
    2014-01-02 11:48:05,794 INFO
    [NodeConfiguratorThread-1-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2014-01-02 11:48:05,794 INFO
    [NodeConfiguratorThread-1-0:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2014-01-02 11:48:05,794 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfigurator@598] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on node01.bigdata
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfigurator@598] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on node03.bigdata
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-0:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-2:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-0:direct.SessionChannel@372] Sending channel
    request for `exec`
    2014-01-02 11:48:05,795 INFO
    [NodeConfiguratorThread-1-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2014-01-02 11:48:05,796 INFO [reader:direct.SessionChannel@326] Received
    window adjustment for 2097152 bytes
    2014-01-02 11:48:05,796 INFO [reader:direct.SessionChannel@326] Received
    window adjustment for 2097152 bytes
    2014-01-02 11:48:05,816 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2014-01-02 11:48:05,816 INFO [reader:direct.SessionChannel@408] Got EOF
    2014-01-02 11:48:05,817 INFO [reader:direct.SessionChannel@223] Got close
    2014-01-02 11:48:05,817 INFO [reader:direct.SessionChannel@425] Sending
    EOF
    2014-01-02 11:48:05,817 INFO [reader:direct.SessionChannel@287] Sending
    close
    2014-01-02 11:48:05,817 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2014-01-02 11:48:05,818 INFO
    [NodeConfiguratorThread-1-1:node.NodeConfiguratorProgress@533]
    node02.bigdata: Setting MAKE_TEMP_DIR as failed and done state
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@408] Got EOF
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@223] Got close
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@425] Sending
    EOF
    2014-01-02 11:48:05,829 INFO [reader:direct.SessionChannel@287] Sending
    close
    2014-01-02 11:48:05,829 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2014-01-02 11:48:05,830 INFO
    [NodeConfiguratorThread-1-0:node.NodeConfiguratorProgress@533]
    node03.bigdata: Setting MAKE_TEMP_DIR as failed and done state
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@314] Got chan
    request for `exit-status`
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@408] Got EOF
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@223] Got close
    2014-01-02 11:48:05,851 INFO [reader:direct.SessionChannel@425] Sending
    EOF
    2014-01-02 11:48:05,852 INFO [reader:direct.SessionChannel@287] Sending
    close
    2014-01-02 11:48:05,852 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2014-01-02 11:48:05,852 INFO
    [NodeConfiguratorThread-1-2:node.NodeConfiguratorProgress@533]
    node01.bigdata: Setting MAKE_TEMP_DIR as failed and done state


    Did you manage to find a solution to the problem ?

    Le vendredi 1 mars 2013 19:21:16 UTC+1, Philip Langdale a écrit :
    ZZ,

    I notice in the log that you're using dropbear as your ssh server. This
    is not the normal thing to use on a desktop or server Ubuntu machine.
    It also leads me to wonder whether you're using busybox as well, which
    would provide an mktemp that's different from the usual one in coreutils
    that we expect.

    I'd ask, to keep things consistent, if you could switch to openssh server
    and coreutils (if you're using busybox) and retry?

    Thanks,

    --phil

    On 1 March 2013 16:14, ZZ wrote:

    Sure! I retry those command as below,

    ======
    root@CDH-Manager:~# sudo mktemp -d /tmp/foo.XXXXXXXX
    /tmp/foo.jlxjEoWJ
    root@CDH-Manager:~# echo $?

    root@CDH-Manager:~# sudo su -
    root@CDH-Manager:~# mktemp -d /tmp/bar.XXXXXXXX
    /tmp/bar.xxfV2wk2
    root@CDH-Manager:~# echo $?

    ======

    On Fri, Mar 1, 2013 at 4:10 PM, bc Wong wrote:

    I'm interested in the verbatim stdout of the commands, not just the
    return code. Verbatim as in the created directory name, new lines, or any
    possible warnings. Could you try that again?

    Cheers,
    bc

    On Thu, Feb 28, 2013 at 10:58 PM, ZZ wrote:

    Hi BC,

    I tested on my server, both `echo $?` command return '0'.
    (I test the command by 'root')

    On Thu, Feb 28, 2013 at 2:42 AM, bc Wong wrote:

    Can you go to any one of the nodes, try the following and tell me the
    results? I'm interested in the stdout as well as the return code.

    $ sudo mktemp -d /tmp/foo.XXXXXXXX
    $ echo $?
    $ sudo su -
    # mktemp -d /tmp/bar.XXXXXXXX
    # echo $?

    Thanks,
    bc

    On Wed, Feb 27, 2013 at 2:53 AM, Zz Chen wrote:

    Hi,

    I installed the latest version of Cloudera Manager (4.5) on my
    Ubuntu 12.04.
    While I try to install my other host, i got stuck by "Failed to
    create temporary directory." on my all client.

    I try to get the log by "retry" on one host and get the server log
    as below.
    I've checked my root password is correct i even use private key but
    in vain.
    I also check the temp dir on my host and it also exist.

    Any advice ? Thanks!

    =======
    2013-02-27 02:50:37,335 INFO
    [1299979108@scm-web-42:node.NodeConfiguratorService@218] Retrying
    configurator with id 1
    2013-02-27 02:50:37,338 INFO
    [1299979108@scm-web-42:node.NodeConfiguratorService@199] Submitted
    configurator for 10.1.193.54 with id 2
    2013-02-27 02:50:37,339 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from INIT (PT0.001S) to CONNECT
    2013-02-27 02:50:37,341 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@152] Client identity
    string: SSH-2.0-SSHJ_0_8
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@161] Server identity
    string: SSH-2.0-dropbear_2011.54
    2013-02-27 02:50:37,346 INFO
    [NodeConfiguratorThread-3-2:transport.KeyExchanger@195] Sending
    SSH_MSG_KEXINIT
    2013-02-27 02:50:37,347 INFO [reader:transport.KeyExchanger@357]
    Received SSH_MSG_KEXINIT
    2013-02-27 02:50:37,408 INFO [reader:kex.DHG14@110] Sending
    SSH_MSG_KEXDH_INIT
    2013-02-27 02:50:37,436 INFO [reader:transport.KeyExchanger@370]
    Received kex followup data
    2013-02-27 02:50:37,436 INFO [reader:kex.DHG14@120] Received
    SSH_MSG_KEXDH_REPLY
    2013-02-27 02:50:37,469 INFO [reader:transport.KeyExchanger@203]
    Sending SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,470 INFO [reader:transport.KeyExchanger@385]
    Received SSH_MSG_NEWKEYS
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.CmfSSHClient@686] Key exchange took 0.125
    seconds
    2013-02-27 02:50:37,471 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from CONNECT (PT0.133S) to AUTHENTICATE
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-userauth
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@85] Trying `password`
    auth...
    2013-02-27 02:50:37,508 INFO
    [NodeConfiguratorThread-3-2:method.AuthPassword@40] Requesting password for
    [AccountResource] ro...@10.1.193.54
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:userauth.UserAuthImpl@102] `password` auth
    successful
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:transport.TransportImpl@302] Setting active
    service to ssh-connection
    2013-02-27 02:50:37,513 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@512]
    10.1.193.54: Transitioning from AUTHENTICATE (PT0.042S) to
    MAKE_TEMP_DIR
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:connection.ConnectionImpl@68] Attaching
    `session` channel (#0)
    2013-02-27 02:50:37,514 INFO [reader:direct.SessionChannel@125]
    Initialized - < session channel: id=0, recipient=0,
    localWin=[winSize=2097152], remoteWin=[winSize=65536] >
    2013-02-27 02:50:37,514 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `pty-req`
    2013-02-27 02:50:37,515 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfigurator@575] Executing mktemp -d
    /tmp/scm_prepare_node.XXXXXXXX on 10.1.193.54
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@120] Will request to exec
    `mktemp -d /tmp/scm_prepare_node.XXXXXXXX`
    2013-02-27 02:50:37,516 INFO
    [NodeConfiguratorThread-3-2:direct.SessionChannel@372] Sending channel
    request for `exec`
    2013-02-27 02:50:37,519 INFO [reader:direct.SessionChannel@408] Got
    EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@314] Got
    chan request for `exit-status`
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@223] Got
    close
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@425]
    Sending EOF
    2013-02-27 02:50:37,520 INFO [reader:direct.SessionChannel@287]
    Sending close
    2013-02-27 02:50:37,521 INFO [reader:connection.ConnectionImpl@84]
    Forgetting `session` channel (#0)
    2013-02-27 02:50:37,521 INFO
    [NodeConfiguratorThread-3-2:node.NodeConfiguratorProgress@533]
    10.1.193.54: Setting MAKE_TEMP_DIR as failed and done state
    =======

    --
    Zz

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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedFeb 27, '13 at 10:53a
activeJan 3, '14 at 8:52a
posts8
users4
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase