<div dir="ltr">Hi Soumya,<br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 24, 2015 at 3:35 PM, Soumya Koduri <span dir="ltr"><<a href="mailto:skoduri@redhat.com" target="_blank">skoduri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Sac,<br>
<br>
While we understand the intent of this mail, please note that most of the operations performed by ganesha related CLI are executed by the runner threads. AFAIK, apart from the return status, we cannot read any error messages from these threads (request glusterd team to confirm that).<br>
<br></blockquote><div><br></div><div>Do those threads log the error messages? Can we point at the log file along with the message:</div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">msg: volume set: failed: Failed to create NFS-Ganesha export config file.</span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Because with just this message we couldn't derive much as to what went wrong.</span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
In addition, since ganesha setup related operations are performed by multiple tools or services, the error messages also gets logged at multiple places. For example,<br>
<br>
HA script logs at - /var/log/messages'<br>
nfs-ganesha service logs at - /var/log/ganesha.log<br>
pacemaker logs - /var/log/pacemaker.log<br>
pcsd logs - /var/log/pcsd.log<br>
<br>
We have already documented steps to refer to for troubleshooting NFS-Ganesha related issues. But it hasn't been ported to upstream yet.<br>
<br>
IMO, it may be good to post those FAQ in upstream as well and maybe provide the link in the log messages to refer to. Any thoughts?<br>
<br></blockquote><div><br></div><div>That would be useful if we cannot derive as to which log file to point to.</div><div><br></div><div>-sac</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Thanks,<br>
Soumya<div><div class="h5"><br>
<br>
On 11/23/2015 05:25 PM, Sachidananda URS wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5">
Hi,<br>
<br>
Recently while we came across some messages in log files which said<br>
"Please see log files for details". We encountered these while trying to<br>
setup NFS-Ganesha, the messages are very vague and doesn't add any value.<br>
<br>
I've raised a bug for this:<br>
<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1284449" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1284449</a><br>
<br>
We need quite a bit of improvement in the logs. For example, on console<br>
message is printed:<br>
<br>
msg: volume set: failed: Failed to create NFS-Ganesha export config file.<br>
<br>
It would be great if the logs mentioned why it failed to create export<br>
config file.<br>
<br>
-sac.<br>
<br>
<br></div></div>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote>
</blockquote></div><br></div></div>