Bug 1285976 - [GlusterD]: Continuous warning messages are populating to glusterd log if NFS server is not running
[GlusterD]: Continuous warning messages are populating to glusterd log if NFS...
Status: CLOSED NOTABUG
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.1
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
Byreddy
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-27 01:15 EST by Byreddy
Modified: 2015-11-27 02:17 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-27 02:17:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Byreddy 2015-11-27 01:15:44 EST
Description of problem:
=======================
If NFS service not running in a node then continuous warning messages are populating to glusterd log. 

Warning messages seen in the glusterd log:
-----------------------------------------
[2015-11-27 05:27:40.165481] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:27:43.166050] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:27:46.166478] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:27:49.167016] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:27:52.167613] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:27:55.168167] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:27:58.168738] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:28:01.169318] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)
[2015-11-27 05:28:04.170061] W [socket.c:588:__socket_rwv] 0-nfs: readv on /var/run/gluster/482342bbafd7129626ce23c9693c54ec.socket failed (Invalid argument)



Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.5-7


How reproducible:
=================
100%


Steps to Reproduce:
===================
1.Have a node with latest RHGS (3.1.2)
2.Create a sample Distributed volume (Eg: 1*2)
3.Start the volume 
4. Kill the NFS service
5. Check glusterd log for the warning messages // you will see continuous messages populating

Actual results:
===============
Warning messages are populating continuously 


Expected results:
=================
One OR Two relates warning messages should be there in glusterd log.


Additional info:
Comment 2 Gaurav Kumar Garg 2015-11-27 02:02:17 EST
Hi byreddy,

This is a expected behaviour. If you kill nfs manually then rpc layer will keep polling for it and you will see continuous warning log. but if you enable nfs.disable option then you will not see any kind of these warning message.
Comment 3 Byreddy 2015-11-27 02:17:39 EST
I am not seeing the issue if i do "nfs.disable on".
Closing this Bug based on above comment.

Note You need to log in before you can comment on or make changes to this bug.