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

[Atin Mukherjee]

On 11/24/2015 03:59 PM, Sachidananda URS wrote:
> Hi Soumya,
> 
> On Tue, Nov 24, 2015 at 3:35 PM, Soumya Koduri <skoduri at redhat.com
> <mailto:skoduri at redhat.com>> wrote:
> 
>     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).
      Although runner framework as of now doesn't have the capability of
returning any other data apart from ret code but the consumer can always
construct the error messages if different ret values can be returned
based on error cases. Does that make sense?	
> 
> 
> Do those threads log the error messages? Can we point at the log file
> along with the message:
They should as runner framework has the capability of it. But once
runner framework starts the executable/script, its the later's
responsibility to take care of the required logging.
> 
> msg: volume set: failed: Failed to create NFS-Ganesha export config file.
> 
> Because with just this message we couldn't derive much as to what went
> wrong.
>  
> 
>     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?
> 
> 
> That would be useful if we cannot derive as to which log file to point to.
> 
> -sac
> 
>  
> 
>     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 <mailto:Gluster-devel at gluster.org>
>         http://www.gluster.org/mailman/listinfo/gluster-devel
> 
> 
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>