Bug 1302911

Summary: config in blog post is wrong
Product: [Community] Gluster-Documentation Reporter: Ben Werthmann <ben>
Component: OtherAssignee: Soumya Koduri <skoduri>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: ben, gluster-bugs, kaushal, skoduri
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-30 13:43:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Werthmann 2016-01-28 23:49:17 UTC
Description of problem:
Please see:
http://blog.gluster.org/2014/09/glusterfs-and-nfs-ganesha-integration/

Starting nfs-ganesha V2.3.0 with the config:

    Protocols = "3,4" ;	 # NFS protocols supported

results in the service failing to start and this error being logged.

    nfs-ganesha-13725[main] config_errs_to_log :CONFIG :WARN :Config File (/etc/ganesha/default.conf:16): Unknown token (3,4)

Comment 1 Soumya Koduri 2016-08-15 15:30:20 UTC
I updated the doc. Please check the same.

Comment 2 Ben Werthmann 2016-08-29 14:30:03 UTC
Which doc did you update? I don't see any changes to this blog entry:
http://blog.gluster.org/2014/09/glusterfs-and-nfs-ganesha-integration/

This fails to start:
Protocols = "3,4" ;

This works:
Protocols = 3,4;

Comment 3 Kaushal 2016-08-30 07:34:23 UTC
Ben, blog.gluster.org syndicates posts from developers personal blogs. It doesn't syndicate changes done to a post on the original blog.

Soumya has modified the post on her blog [1]. You can view the change there.

[1] https://glusterants.wordpress.com/2014/09/03/glusterfs-and-nfs-ganesha-integration/

Comment 4 Ben Werthmann 2016-08-30 13:43:23 UTC
Interesting. IMHO having a buggy sample config on the seemingly official blog seems like a bug. Glad it's fixed at the source.