Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1257

January 22nd, 2016 05:00

Command failed: Could not add TB

Hello,

I try to deploy 3 node cluster of ScaleIO, upload and install packages phases goes well, but on configure phase I receive error and don't have a clue how to fix this:

Command failed: Could not add TB 10.10.50.138 on 10.10.50.136,10.10.50.135 due to: Communication error

{

  "mdmIPs": [

    "10.10.50.136",

    "10.10.50.135"

  ],

  "mdmPassword": "xxxxx",

  "tb": {

    "node": {

      "ostype": "linux",

      "nodeName": null,

      "nodeIPs": [

        "10.10.50.138"

      ],

      "domain": null,

      "userName": "root",

      "password": "xxxxx",

      "liaPassword": "xxxxx"

    },

    "nodeInfo": {

      "diskDevices": [

        {

          "diskName": "/dev/xvdb"

        },

        {

          "diskName": "/dev/xvda"

        },

        {

          "diskName": "/dev/sr0"

        },

        {

          "diskName": "/dev/xvda1"

        }

      ],

      "installedComponents": [],

      "osType": "linux",

      "linuxFlavour": "rhel7",

      "pythonInstalled": true,

      "timestamp": "2016-01-22T12:39:21.330Z"

    },

    "tbIPs": [

      "10.10.50.138"

    ]

  },

  "commandState": "failed",

  "startTime": "2016-01-22T12:53:11.069Z",

  "message": "Command failed: Could not add TB 10.10.50.138 on 10.10.50.136,10.10.50.135 due to: Communication error",

  "result": null,

  "followingCommand": "SwitchToClusterModeCommand[working on= (MDM) [10.10.50.136, 10.10.50.135]]",

  "allowedState": "configure",

  "archived": false,

  "commandName": ".AddTbCommand"

}

Maybe anyone have idea how to solve this? In all 3 nodes firewall is disabled.

Best regards,

Martins

January 22nd, 2016 07:00

There is a KB article which is a decent match for the issue faced.  Please review the attached article and confirm if its relevant to you.

1 Attachment

1 Rookie

 • 

16 Posts

January 22nd, 2016 07:00

Thanks, it works!

January 23rd, 2016 23:00

When specifying SDS device path on a Linux node in CSV file, the user should use the path according to what's written in '/proc/partitions' (and not according to 'fdisk -l')

example:

fdisk output: /dev/mapper/samah-lv1, /dev/sdb

/proc/partitions value : dm-3, sdb

value to write in CSV file: /dev/dm-3, /dev/sdb

Thanks,

Tomer

Sent from my Cyanogen phone

No Events found!

Top