On 08/09/2016 03:33 PM, Mahdi Adnan wrote:
Hi,
Im using NFS-Ganesha to access my volume, it's working fine for now but
im seeing lots of traffic on the Loopback interface, in fact it's the
same amount of traffic on the bonding interface, can anyone please
explain to me why is this happening ?
Could you please capture packets on those interfaces using tcpdump and
examine the traffic?
also, i got the following error in the ganesha log file;
09/08/2016 11:35:54 : epoch 57a5da0c : gfs04 :
ganesha.nfsd-1646[dbus_heartbeat] dbus_heartbeat_cb :DBUS :WARN :Health
status is unhealthy. Not sending heartbeat
09/08/2016 11:46:04 : epoch 57a5da0c : gfs04 :
ganesha.nfsd-1646[dbus_heartbeat] dbus_heartbeat_cb :DBUS :WARN :Health
status is unhealthy. Not sending heartbeat
09/08/2016 11:54:39 : epoch 57a5da0c : gfs04 :
ganesha.nfsd-1646[dbus_heartbeat] dbus_heartbeat_cb :DBUS :WARN :Health
status is unhealthy. Not sending heartbeat
09/08/2016 12:06:04 : epoch 57a5da0c : gfs04 :
ganesha.nfsd-1646[dbus_heartbeat] dbus_heartbeat_cb :DBUS :WARN :Health
status is unhealthy. Not sending heartbeat
is it something i should care about ?
Above warnings are thrown when the outstanding rpc request queue count
doesn't change within two heartbeats, in other words the server may be
taking a while to process the requests and responding slowly to its clients.
Thanks,
Soumya
My ganesha config is the following;
EXPORT{
Export_Id = 1 ;
Path = "/vlm02";
FSAL {
name = GLUSTER;
hostname = "gfs04";
volume = "vlm02";
}
Access_type = RW;
Disable_ACL = TRUE;
Squash = No_root_squash;
Protocols = "3" ;
Transports = "TCP";
}
Im accessing it via a floating ip assigned by CTDB.
Thank you.
--
Respectfully*
**Mahdi A. Mahdi*
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
