<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 3, 2019 at 11:56 AM Jiffin Thottan &lt;<a href="mailto:jthottan@redhat.com">jthottan@redhat.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
is_nfs_export_available is just a wrapper around &quot;showmount&quot; command AFAIR.<br>
I saw following messages in console output.<br>
 mount.nfs: rpc.statd is not running but is required for remote locking.<br>
05:06:55 mount.nfs: Either use &#39;-o nolock&#39; to keep locks local, or start statd.<br>
05:06:55 mount.nfs: an incorrect mount option was specified<br>
<br>
For me it looks rpcbind may not be running on the machine.<br>
Usually rpcbind starts automatically on machines, don&#39;t know whether it can happen or not. <br></blockquote><div><br></div><div>That&#39;s precisely what the question is. Why suddenly we&#39;re seeing this happening too frequently. Today I saw atleast 4 to 5 such failures already.</div><div><br></div><div>Deepshika - Can you please help in inspecting this?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Regards,<br>
Jiffin<br>
<br>
<br>
----- Original Message -----<br>
From: &quot;Atin Mukherjee&quot; &lt;<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>&gt;<br>
To: &quot;gluster-infra&quot; &lt;<a href="mailto:gluster-infra@gluster.org" target="_blank">gluster-infra@gluster.org</a>&gt;, &quot;Gluster Devel&quot; &lt;<a href="mailto:gluster-devel@gluster.org" target="_blank">gluster-devel@gluster.org</a>&gt;<br>
Sent: Wednesday, April 3, 2019 10:46:51 AM<br>
Subject: [Gluster-devel] is_nfs_export_available from nfs.rc failing too        often?<br>
<br>
I&#39;m observing the above test function failing too often because of which arbiter-mount.t test fails in many regression jobs. Such frequency of failures wasn&#39;t there earlier. Does anyone know what has changed recently to cause these failures in regression? I also hear when such failure happens a reboot is required, is that true and if so why? <br>
<br>
One of the reference : <a href="https://build.gluster.org/job/centos7-regression/5340/consoleFull" rel="noreferrer" target="_blank">https://build.gluster.org/job/centos7-regression/5340/consoleFull</a> <br>
<br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div></div>