On Fri, 17 May 2019 at 06:01, David Cunningham
wrote:
> Hello,
>
> We're adding an arbiter node to an existing volume and having an issue.
> Can anyone help? The root cause error appears to be
> "----0001: failed to resolve (Transport
> endpoint is not connected)", as
Hello,
It does show everything as Connected and 0 for the existing bricks, gfs1
and gfs2. The new brick gfs3 isn't listed, presumably because of the
failure as per my original email. Would anyone have any further suggestions
on how to prevent the "Transport endpoint is not connected" error when
