Bug 919209 - Disabling NFS causes E level errors in nfs.log.
Summary: Disabling NFS causes E level errors in nfs.log.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.1
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: rjoseph
QA Contact: Ben Turner
URL:
Whiteboard:
Depends On:
Blocks: 976750 1095330
TreeView+ depends on / blocked
 
Reported: 2013-03-07 21:01 UTC by Ben Turner
Modified: 2014-05-07 13:16 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.4.0.12rhs.beta4
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 976750 (view as bug list)
Environment:
Last Closed: 2013-09-23 22:39:27 UTC
Embargoed:

Attachments (Terms of Use)

Description Ben Turner 2013-03-07 21:01:43 UTC 
Description of problem:

When I run "gluster volume set <volume> nfs.disable yes" I see several E level errors get generated in nfs.log.

Version-Release number of selected component (if applicable):

glusterfs-3.3.0.5rhs-43.el6rhs.x86_64

How reproducible:

Every time I disable NFS on a volume.

Steps to Reproduce:
1.  Create a volume.
2.  Start the volume.
3.  Run gluster volume set <volume> nfs.disable yes
  
Actual results:

The following errors are generated:

[2013-03-07 20:00:49.807896] I [glusterfsd.c:1776:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.0.5rhs (/usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /var/run/b44dfe80d1fce87cc70968d5f9f65ddd.socket)
[2013-03-07 20:00:49.819651] E [nfs.c:520:nfs_init_state] 0-nfs: nfs must have at least one child subvolume
[2013-03-07 20:00:49.819675] E [nfs.c:779:init] 0-nfs: Failed to init nfs option
[2013-03-07 20:00:49.819685] E [xlator.c:385:xlator_init] 0-nfs-server: Initialization of volume 'nfs-server' failed, review your volfile again
[2013-03-07 20:00:49.819694] E [graph.c:294:glusterfs_graph_init] 0-nfs-server: initializing translator failed
[2013-03-07 20:00:49.819703] E [graph.c:483:glusterfs_graph_activate] 0-graph: init failed
[2013-03-07 20:00:49.819850] W [glusterfsd.c:924:cleanup_and_exit] (-->/usr/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0xa5) [0x3b3be0f385] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0xe0) [0x40cb60] (-->/usr/sbin/glusterfs(glusterfs_process_volfp+0x198) [0x4059c8]))) 0-: received signum (0), shutting down

Expected results:

An informational or warning level message saying that NFS has been disabled instead of the error level messages.

Additional info:
Comment 2 Amar Tumballi 2013-07-03 11:54:47 UTC 
https://code.engineering.redhat.com/gerrit/#/c/9537/1
Comment 4 Ben Turner 2013-08-09 20:23:18 UTC 
Looks good in the .18 version:

[2013-08-09 20:18:33.940411] I [nfs.c:537:nfs_init_state] 0-nfs: NFS is manually disabled: Exiting

Marking as verified.
Comment 5 Scott Haines 2013-09-23 22:39:27 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html
Comment 6 Scott Haines 2013-09-23 22:43:44 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html
Note You need to log in before you can comment on or make changes to this bug.