[Bugs] [Bug 1222065] GlusterD fills the logs when the NFS-server is disabled

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1222065

krishnan parthasarathi <kparthas at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(matorola at gmail.co
                   |                            |m)



--- Comment #11 from krishnan parthasarathi <kparthas at redhat.com> ---
(In reply to Anatoly Pugachev from comment #10)
> Created attachment 1044665 [details]
> glusterfs log node01
> 
> file logs attachment, it has upgrade to 3.7.2 and NFS related logs, from
> node01

IIUC, you are seeing repeated log messages when nfs.disable is to "off" on
vol2. As a side effect of setting nfs.disable to off, we have at least one
volume (i.e, vol2) which is started and has nfs service enabled. This tells
glusterd that it has to start the NFS service if it's not running. I wonder why
glusterd is failing to 'reach' the gluster NFS process via the unix domain
socket file mentioned in the log messages. Could you check if the gluster NFS
process is running on the node where you see these log messages in glusterd's
log file? It would help if you could attach the gluster nfs and glusterd log
files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EwAiyUdAY9&a=cc_unsubscribe