[Gluster-devel] Logging improvements needed in nfs-ganesha

[Soumya Koduri]

Hi Sac,

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).

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,

HA script logs at - /var/log/messages'
nfs-ganesha service logs at - /var/log/ganesha.log
pacemaker logs - /var/log/pacemaker.log
pcsd logs - /var/log/pcsd.log

We have already documented steps to refer to for troubleshooting 
NFS-Ganesha related issues. But it hasn't been ported to upstream yet.

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?

Thanks,
Soumya

On 11/23/2015 05:25 PM, Sachidananda URS wrote:
> Hi,
>
> Recently while we came across some messages in log files which said
> "Please see log files for details". We encountered these while trying to
> setup NFS-Ganesha, the messages are very vague and doesn't add any value.
>
> I've raised a bug for this:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1284449
>
> We need quite a bit of improvement in the logs. For example, on console
> message is printed:
>
> msg: volume set: failed: Failed to create NFS-Ganesha export config file.
>
> It would be great if the logs mentioned why it failed to create export
> config file.
>
> -sac.
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>