On Mon, Sep 15, 2014 at 7:57 AM, Sahina Bose <sabose@redhat.com> wrote:

On 09/15/2014 10:28 AM, Kanagaraj wrote:

On 09/15/2014 02:24 AM, Nathan Stratton wrote:

glusterd is running on all hosts and all peers are connected.

Corresponding error messages in vdsm.log should help here.

Do you see any command failure messages in vdsm.log or supervdsm.log?

The error seems to be due to the JSON protocol used while installing host.

Can you put the host to Maintenance, and edit the host - uncheck the Use JSON protocol, and activate host again?

Thanks, that works! However I still don't see my gluster bricks. supervdsm.log is showing:

supervdsm.log:MainProcess|Thread-17518::DEBUG::2014-09-16 09:23:48,442::utils::738::root::(execCmd) /usr/sbin/gluster --mode=script peer status --xml (cwd None)

supervdsm.log:MainProcess|Thread-17518::DEBUG::2014-09-16 09:23:48,453::utils::738::root::(execCmd) /usr/sbin/gluster system:: uuid get (cwd None)

supervdsm.log:MainProcess|Thread-17518::DEBUG::2014-09-16 09:23:48,833::utils::738::root::(execCmd) /usr/sbin/gluster system:: uuid get (cwd None)

supervdsm.log:MainProcess|Thread-17518::DEBUG::2014-09-16 09:23:51,491::utils::738::root::(execCmd) /usr/sbin/gluster --mode=script volume info --xml (cwd None)

Piotr, do you know what we are missing here?

-Nathan

thanks
sahina