<div dir="ltr">Hi Anoop,<div><br></div><div>So I think I found the issue. Looks like the server's IP changed. What's the best way to recover from an IP change? </div><div><br></div><div>Thanks!</div><div>Alan</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 28, 2016 at 2:41 AM Anoop C S <<a href="mailto:anoopcs@redhat.com">anoopcs@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 2016-06-28 at 06:01 +0000, Alan Hartless wrote:<br>
> Hi Anoop,<br>
><br>
> 1. I didn't configure anything specific with RDMA so I assume TCP.<br>
> When I run gluster volume status all on the working pod, it has 0 for<br>
> the RDMA Port. The server that won't start Gluster is a Docker image<br>
> running Ubuntu 14.04 with Gluster 3.7 installed from Gluster's apt<br>
> repositories. <br>
><br>
<br>
Fine. So we can take out the involvement of RDMA from the picture.<br>
<br>
> 2. There are no error messages for the bricks. No brick logs at all<br>
> on the server since it won't even start Glusterd due to the RDMA<br>
> error. On the working server, there are no errors recorded for the<br>
> bricks. <br>
><br>
<br>
Can you also please check errors inside glusterd log file? If you can't<br>
find any error messages there, try increasing the log level to DEBUG by<br>
adding "-L DEBUG" option while starting glusterd and check for any<br>
abnormal messages?<br>
<br>
> Thanks,<br>
> Alan<br>
><br>
> On Mon, Jun 27, 2016 at 5:52 AM Anoop C S <<a href="mailto:anoopcs@redhat.com" target="_blank">anoopcs@redhat.com</a>> wrote:<br>
> > On Mon, 2016-06-27 at 15:20 +0530, Anoop C S wrote:<br>
> > > On Sun, 2016-06-26 at 14:48 +0000, Alan Hartless wrote:<br>
> > > ><br>
> > > > I had a glusterd server restart and now glusterfsd refused to<br>
> > > > start.<br>
> > > > When I try to start glusterd with <br>
> > > > /usr/sbin/glusterd -N -p /var/run/glusterd.pid<br>
> > > ><br>
> > > > I get this:<br>
> > > > librdmacm: couldn't read ABI version.<br>
> > > > librdmacm: assuming: 4<br>
> > > > CMA: unable to get RDMA device list<br>
> > > ><br>
> > > Some queries:<br>
> > > 1. With what transport type have you created the volume? On which<br>
> > > platform are your glusterfs servers running and in case you are<br>
> > using<br>
> > > rdma transport, what packages were installed for setting up the<br>
> > IB<br>
> > > stack?<br>
> > ><br>
> > > 2. Can you please share the error messages from brick logs(under<br>
> > > /var/log/gluster/bricks/) and glusterd logs(under<br>
> ><br>
> > Small correction. Brick logs are located at<br>
> > /var/log/glusterfs/bricks.<br>
> ><br>
> > > /var/log/glusterfs/)<br>
> > > for better clarity?<br>
> > ><br>
> > > ><br>
> > > > A google search has been unsuccessful on how to resolve this.<br>
> > Any<br>
> > > > ideas?<br>
> > > ><br>
> > > > Thanks!<br>
> > > > Alan<br>
> > > > _______________________________________________<br>
> > > > Gluster-users mailing list<br>
> > > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> > > > <a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> > > _______________________________________________<br>
> > > Gluster-users mailing list<br>
> > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> > > <a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> ><br>
</blockquote></div>