<div dir="ltr"><div dir="ltr"><div dir="ltr">I am also seeing a bunch of these errors in the logs. Do they really need to be Info logs?</div><div dir="ltr"><br></div><div><snip></div><div><br></div><div dir="ltr"><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.597029] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 382 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.597640] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 385 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.598114] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 344 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.598737] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 343 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.599172] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 384 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.599789] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 386 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.600237] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 387 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.579405] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 324 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.563771] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 187 (errno:11:Resource temporarily unavailable); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.560416] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 161 (errno:0:Success); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.564826] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 194 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.561503] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 306 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.567985] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 164 (errno:0:Success); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.566924] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 198 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.562567] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 346 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:18.580451] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 363 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:23.165797] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 346 (errno:11:Resource temporarily unavailable); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:23.166019] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 207 (errno:0:Success); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:23.166905] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 197 (errno:0:Success); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:23.167541] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 273 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:23.167904] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 275 (errno:61:No data available); returning ENODATA</font></div><div dir="ltr"><font face="monospace, monospace" size="1">[2018-11-14 06:01:23.168502] I [socket.c:693:__socket_rwv] 0-tcp.patchy-vol01-server: EOF on socket 277 (errno:61:No data available); returning ENODATA</font></div><div><font face="monospace, monospace" size="1"><br></font></div><div><font face="monospace, monospace" size="1"></snip></font></div><div><font face="monospace, monospace" size="1"><br></font></div><div><font face="monospace, monospace" size="1"><br></font></div><div><div><font face="arial, helvetica, sans-serif">[nbalacha@dhcp35-62 bricks]$ grep "EOF on socket" d-backends-vol01-brick* |wc -l</font></div><div><font face="arial, helvetica, sans-serif">1580</font></div></div><div><br></div><div><br></div><div><br></div><div>Regards,</div><div>Nithya</div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 14 November 2018 at 21:03, Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11/14/2018 10:04 AM, Nithya Balachandran wrote:<br>
> Hi Mohit,<br>
> <br>
> The regression run in the subject has failed because a brick has crashed in <br>
> <br>
> bug-1432542-mpx-restart-crash.<wbr>t<br>
> <br>
> <br>
</span>> *06:03:38* 1 test(s) generated core <br>
> *06:03:38* ./tests/bugs/core/bug-1432542-<wbr>mpx-restart-crash.t<br>
> *06:03:38*<br>
<span class="">> <br>
> <br>
> The brick process has crashed in posix_fs_health_check as this->priv<br>
> contains garbage. It looks like it might have been freed already. Can<br>
> you take a look at it?<br>
<br>
</span>Sounds like another incarnation of:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1636570" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1636570</a><br>
<br>
@mohit, any further clues?<br>
<div><div class="h5"><br>
> <br>
> <br>
> <br>
> (gdb) bt<br>
> #0 0x00007f4019ea1f19 in vfprintf () from ./lib64/libc.so.6<br>
> #1 0x00007f4019eccf49 in vsnprintf () from ./lib64/libc.so.6<br>
> #2 0x00007f401b87705a in gf_vasprintf (string_ptr=0x7f3e81ff99f0,<br>
> format=0x7f400df32f40 "op=%s;path=%s;error=%s;brick=<wbr>%s:%s timeout is<br>
> %d", arg=0x7f3e81ff99f8)<br>
> at<br>
> /home/jenkins/root/workspace/<wbr>centos7-regression/<wbr>libglusterfs/src/mem-pool.c:<wbr>234<br>
> #3 0x00007f401b8de6e2 in _gf_event<br>
> (event=EVENT_POSIX_HEALTH_<wbr>CHECK_FAILED, fmt=0x7f400df32f40<br>
> "op=%s;path=%s;error=%s;brick=<wbr>%s:%s timeout is %d")<br>
> at<br>
> /home/jenkins/root/workspace/<wbr>centos7-regression/<wbr>libglusterfs/src/events.c:89<br>
> #4 0x00007f400def07f9 in posix_fs_health_check (this=0x7f3fd78b7840) at<br>
> /home/jenkins/root/workspace/<wbr>centos7-regression/xlators/<wbr>storage/posix/src/posix-<wbr>helpers.c:1960<br>
> #5 0x00007f400def0926 in posix_health_check_thread_proc<br>
> (data=0x7f3fd78b7840)<br>
> at<br>
> /home/jenkins/root/workspace/<wbr>centos7-regression/xlators/<wbr>storage/posix/src/posix-<wbr>helpers.c:2005<br>
> #6 0x00007f401a68ae25 in start_thread () from ./lib64/libpthread.so.0<br>
> #7 0x00007f4019f53bad in clone () from ./lib64/libc.so.6<br>
> (gdb) f 4<br>
> #4 0x00007f400def07f9 in posix_fs_health_check (this=0x7f3fd78b7840) at<br>
> /home/jenkins/root/workspace/<wbr>centos7-regression/xlators/<wbr>storage/posix/src/posix-<wbr>helpers.c:1960<br>
> 1960 gf_event(EVENT_POSIX_HEALTH_<wbr>CHECK_FAILED,<br>
> (gdb) l<br>
> 1955 sys_close(fd);<br>
> 1956 }<br>
> 1957 if (ret && file_path[0]) {<br>
> 1958 gf_msg(this->name, GF_LOG_WARNING, errno,<br>
> P_MSG_HEALTHCHECK_FAILED,<br>
> 1959 "%s() on %s returned", op, file_path);<br>
> 1960 gf_event(EVENT_POSIX_HEALTH_<wbr>CHECK_FAILED,<br>
> 1961 "op=%s;path=%s;error=%s;<wbr>brick=%s:%s timeout is %d", op,<br>
> 1962 file_path, strerror(op_errno), priv->hostname,<br>
> priv->base_path,<br>
> 1963 timeout);<br>
> 1964 }<br>
> (gdb) p pri->hostname<br>
> No symbol "pri" in current context.<br>
</div></div>> *(gdb) p priv->hostname*<br>
> *$14 = 0xa200 <error: Cannot access memory at address 0xa200>*<br>
> *(gdb) p priv->base_path*<br>
> *$15 = 0x7f3ddeadc0de00 <error: Cannot access memory at address<br>
> 0x7f3ddeadc0de00>*<br>
> (gdb) <br>
> <br>
> <br>
> <br>
> Thanks,<br>
> Nithya<br>
> <br>
> <br>
> ______________________________<wbr>_________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
> <br>
</blockquote></div><br></div>