Re: [Gluster-devel] v3.6.2
nfs.log attached. Where is glusterd.log? David -- Original Message -- From: "Atin Mukherjee" To: "David F. Robinson" ; "Pranith Kumar Karampuri" ; "Justin Clift" Cc: "Gluster Users" ; "Gluster Devel" Sent: 1/27/2015 12:42:44 AM Subject: Re: [Gluster-devel] v3.6.2 On 01/27/2015 10:56 AM, David F. Robinson wrote: [root@gfs01bkp ~]# gluster volume status homegfs_bkp Status of volume: homegfs_bkp Gluster process Port Online Pid -- Brick gfsib01bkp.corvidtec.com:/data/brick01bkp/homegfs _bkp 49152 Y 4087 Brick gfsib01bkp.corvidtec.com:/data/brick02bkp/homegfs _bkp 49155 Y 4092 NFS Server on localhost N/A N N/A Ahh!! here is the problem, your NFS server is not started because of which NFS mount is failing. Can you please share the nfs.log & glusterd.log files. ~Atin Task Status of Volume homegfs_bkp -- Task : Rebalance ID : 6d4c6c4e-16da-48c9-9019-dccb7d2cfd66 Status : completed -- Original Message -- From: "Atin Mukherjee" To: "Pranith Kumar Karampuri" ; "Justin Clift" ; "David F. Robinson" Cc: "Gluster Users" ; "Gluster Devel" Sent: 1/26/2015 11:51:13 PM Subject: Re: [Gluster-devel] v3.6.2 On 01/27/2015 07:33 AM, Pranith Kumar Karampuri wrote: On 01/26/2015 09:41 PM, Justin Clift wrote: On 26 Jan 2015, at 14:50, David F. Robinson wrote: I have a server with v3.6.2 from which I cannot mount using NFS. The FUSE mount works, however, I cannot get the NFS mount to work. From /var/log/message: Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying I also am continually getting the following errors in /var/log/glusterfs: [root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:06.262935] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:09.263334] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:12.263761] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:15.264177] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:18.264623] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:21.265053] W [soc
Re: [Gluster-devel] v3.6.2
On 01/27/2015 10:56 AM, David F. Robinson wrote: > [root@gfs01bkp ~]# gluster volume status homegfs_bkp > Status of volume: homegfs_bkp > Gluster process PortOnline Pid > -- > > Brick gfsib01bkp.corvidtec.com:/data/brick01bkp/homegfs > _bkp49152 Y > 4087 > Brick gfsib01bkp.corvidtec.com:/data/brick02bkp/homegfs > _bkp49155 Y > 4092 > NFS Server on localhost N/A N N/A Ahh!! here is the problem, your NFS server is not started because of which NFS mount is failing. Can you please share the nfs.log & glusterd.log files. ~Atin > > Task Status of Volume homegfs_bkp > -- > > Task : Rebalance > ID : 6d4c6c4e-16da-48c9-9019-dccb7d2cfd66 > Status : completed > > > > > -- Original Message -- > From: "Atin Mukherjee" > To: "Pranith Kumar Karampuri" ; "Justin Clift" > ; "David F. Robinson" > Cc: "Gluster Users" ; "Gluster Devel" > > Sent: 1/26/2015 11:51:13 PM > Subject: Re: [Gluster-devel] v3.6.2 > >> >> >> On 01/27/2015 07:33 AM, Pranith Kumar Karampuri wrote: >>> >>> On 01/26/2015 09:41 PM, Justin Clift wrote: >>>> On 26 Jan 2015, at 14:50, David F. Robinson >>>> wrote: >>>>> I have a server with v3.6.2 from which I cannot mount using NFS. The >>>>> FUSE mount works, however, I cannot get the NFS mount to work. From >>>>> /var/log/message: >>>>>Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server >>>>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>>>> I also am continually getting the following errors in >>>>> /var/log/glusterfs: >>>>>[root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log >>>>> [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] >>>>> 0-management: readv on >>>>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>>>> argument) >>>>> [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] >>>>> 0-management: readv on >>>>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>>>> argument) >>>>> [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] >>>>> 0-management: readv on >>>>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>>>> argument) >>>>> [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] >>>>> 0-management: readv on >>>>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>>>> argument) >>>>> [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] >&
Re: [Gluster-devel] v3.6.2
[root@gfs01bkp ~]# gluster volume status homegfs_bkp Status of volume: homegfs_bkp Gluster process PortOnline Pid -- Brick gfsib01bkp.corvidtec.com:/data/brick01bkp/homegfs _bkp49152 Y 4087 Brick gfsib01bkp.corvidtec.com:/data/brick02bkp/homegfs _bkp49155 Y 4092 NFS Server on localhost N/A N N/A Task Status of Volume homegfs_bkp -- Task : Rebalance ID : 6d4c6c4e-16da-48c9-9019-dccb7d2cfd66 Status : completed -- Original Message -- From: "Atin Mukherjee" To: "Pranith Kumar Karampuri" ; "Justin Clift" ; "David F. Robinson" Cc: "Gluster Users" ; "Gluster Devel" Sent: 1/26/2015 11:51:13 PM Subject: Re: [Gluster-devel] v3.6.2 On 01/27/2015 07:33 AM, Pranith Kumar Karampuri wrote: On 01/26/2015 09:41 PM, Justin Clift wrote: On 26 Jan 2015, at 14:50, David F. Robinson wrote: I have a server with v3.6.2 from which I cannot mount using NFS. The FUSE mount works, however, I cannot get the NFS mount to work. From /var/log/message: Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying I also am continually getting the following errors in /var/log/glusterfs: [root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:06.262935] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:09.263334] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:12.263761] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:15.264177] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:18.264623] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:21.265053] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:24.265504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) I believe this error message comes when the socket file is not present. I see the following commit which changed the locatio
Re: [Gluster-devel] v3.6.2
On 01/27/2015 07:33 AM, Pranith Kumar Karampuri wrote: > > On 01/26/2015 09:41 PM, Justin Clift wrote: >> On 26 Jan 2015, at 14:50, David F. Robinson >> wrote: >>> I have a server with v3.6.2 from which I cannot mount using NFS. The >>> FUSE mount works, however, I cannot get the NFS mount to work. From >>> /var/log/message: >>> Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server >>> 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying >>> I also am continually getting the following errors in >>> /var/log/glusterfs: >>> [root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log >>> [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:06.262935] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:09.263334] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:12.263761] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:15.264177] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:18.264623] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:21.265053] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) >>> [2015-01-26 14:42:24.265504] W [socket.c:611:__socket_rwv] >>> 0-management: readv on >>> /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid >>> argument) > I believe this error message comes when the socket file is not present. > I see the following commit which changed the location of the sockets. > May be Atin may know more. about this: +Atin. > Can we get the output of 'gluster volume status' for the volume which you are trying to mount? ~Atin > Pranith >>> ^C >>> Also, when I try to NFS mount my gluster volume, I am getting >> Any chance there's a network or host based firewall stopping some of >> the ports? >> >> + Justin >> >> -- >> GlusterFS - http://www.gluster.org >> >> An open source, distributed file system scaling to several >> petabytes, and handling thousands of clients. >> >> My personal twitter: twitter.com/realjustinclift >> >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.6.2
On 01/26/2015 09:41 PM, Justin Clift wrote: On 26 Jan 2015, at 14:50, David F. Robinson wrote: I have a server with v3.6.2 from which I cannot mount using NFS. The FUSE mount works, however, I cannot get the NFS mount to work. From /var/log/message: Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying I also am continually getting the following errors in /var/log/glusterfs: [root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:06.262935] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:09.263334] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:12.263761] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:15.264177] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:18.264623] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:21.265053] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:24.265504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) I believe this error message comes when the socket file is not present. I see the following commit which changed the location of the sockets. May be Atin may know more. about this: +Atin. Pranith ^C Also, when I try to NFS mount my gluster volume, I am getting Any chance there's a network or host based firewall stopping some of the ports? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.6.2
No firewall used on that machine. [root@gfs01bkp ~]# /etc/init.d/iptables status iptables: Firewall is not running. [ [root@gfs01bkp ~]# cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted -- Original Message -- From: "Justin Clift" To: "David F. Robinson" Cc: "Gluster Users" ; "Gluster Devel" Sent: 1/26/2015 11:11:15 AM Subject: Re: [Gluster-devel] v3.6.2 On 26 Jan 2015, at 14:50, David F. Robinson wrote: I have a server with v3.6.2 from which I cannot mount using NFS. The FUSE mount works, however, I cannot get the NFS mount to work. From /var/log/message: Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying I also am continually getting the following errors in /var/log/glusterfs: [root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:06.262935] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:09.263334] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:12.263761] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:15.264177] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:18.264623] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:21.265053] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:42:24.265504] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) ^C Also, when I try to NFS mount my gluster volume, I am getting Any chance there's a network or host based firewall stopping some of the ports? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.6.2
On 26 Jan 2015, at 14:50, David F. Robinson wrote: > I have a server with v3.6.2 from which I cannot mount using NFS. The FUSE > mount works, however, I cannot get the NFS mount to work. From > /var/log/message: > > Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:31:28 gfs01bkp mount[2810]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:31:53 gfs01bkp mount[4456]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:33:28 gfs01bkp mount[2810]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:33:53 gfs01bkp mount[4456]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:35:28 gfs01bkp mount[2810]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > Jan 26 09:35:53 gfs01bkp mount[4456]: mount to NFS server > 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying > > > I also am continually getting the following errors in /var/log/glusterfs: > > [root@gfs01bkp glusterfs]# tail -f etc-glusterfs-glusterd.vol.log > [2015-01-26 14:41:51.260827] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:41:54.261240] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:41:57.261642] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:00.262073] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:03.262504] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:06.262935] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:09.263334] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:12.263761] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:15.264177] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:18.264623] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:21.265053] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > [2015-01-26 14:42:24.265504] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid > argument) > ^C > > Also, when I try to NFS mount my gluster volume, I am getting Any chance there's a network or host based firewall stopping some of the ports? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.6.2
Tried shutting down glusterd and glusterfsd and restarting. [2015-01-26 14:52:53.548330] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.549763] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.551245] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.552819] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.554289] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.555769] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.564429] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-01-26 14:52:53.565578] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/0cdef7faa934cfe52676689ff8c0110f.socket failed (Invalid argument) [2015-01-26 14:52:53.566488] I [MSGID: 106005] [glusterd-handler.c:4142:__glusterd_brick_rpc_notify] 0-management: Brick gfsib01bkp.corvidtec.com:/data/brick01bkp/Software_bkp has disconnected from glusterd. [2015-01-26 14:52:53.567453] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/09e734d5e8d52bb796896c7a33d0a3ff.socket failed (Invalid argument) [2015-01-26 14:52:53.568248] I [MSGID: 106005] [glusterd-handler.c:4142:__glusterd_brick_rpc_notify] 0-management: Brick gfsib01bkp.corvidtec.com:/data/brick02bkp/Software_bkp has disconnected from glusterd. [2015-01-26 14:52:53.569009] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3f6844c74682f39fa7457082119628c5.socket failed (Invalid argument) [2015-01-26 14:52:53.569851] I [MSGID: 106005] [glusterd-handler.c:4142:__glusterd_brick_rpc_notify] 0-management: Brick gfsib01bkp.corvidtec.com:/data/brick01bkp/Source_bkp has disconnected from glusterd. [2015-01-26 14:52:53.570818] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/34d5cc70aba63082bbb467ab450bd08b.socket failed (Invalid argument) [2015-01-26 14:52:53.571777] I [MSGID: 106005] [glusterd-handler.c:4142:__glusterd_brick_rpc_notify] 0-management: Brick gfsib01bkp.corvidtec.com:/data/brick02bkp/Source_bkp has disconnected from glusterd. [2015-01-26 14:52:53.572681] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/0cd747876dca36cb21ecc7a36f7f897c.socket failed (Invalid argument) [2015-01-26 14:52:53.573533] I [MSGID: 106005] [glusterd-handler.c:4142:__glusterd_brick_rpc_notify] 0-management: Brick gfsib01bkp.corvidtec.com:/data/brick01bkp/homegfs_bkp has disconnected from glusterd. [2015-01-26 14:52:53.574433] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/88744e1365b414d41e720e480700716a.socket failed (Invalid argument) [2015-01-26 14:52:53.575399] I [MSGID: 106005] [glusterd-handler.c:4142:__glusterd_brick_rpc_notify] 0-management: Brick gfsib01bkp.corvidtec.com:/data/brick02bkp/homegfs_bkp has disconnected from glusterd. [2015-01-26 14:52:53.575434] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/1f0cee5a2d074e39b32ee5a81c70e68c.socket failed (Invalid argument) [2015-01-26 14:52:53.575447] I [MSGID: 106006] [glusterd-handler.c:4257:__glusterd_nodesvc_rpc_notify] 0-management: nfs has disconnected from glusterd. [2015-01-26 14:52:53.579663] I [glusterd-pmap.c:227:pmap_registry_bind] 0-pmap: adding brick /data/brick01bkp/homegfs_bkp on port 49152 [2015-01-26 14:52:53.581943] I [glusterd-pmap.c:227:pmap_registry_bind] 0-pmap: adding brick /data/brick02bkp/Source_bkp on port 49156 [2015-01-26 14:52:53.583487] I [glusterd-pmap.c:227:pmap_registry_bind] 0-pmap: adding brick /data/brick01bkp/Source_bkp on port 49153 [2015-01-26 14:52:53.584921] I [glusterd-pmap.c:227:pmap_registry_bind] 0-pmap: adding brick /data/brick02bkp/Software_bkp on port 49157 [2015-01-26 14:52:53.585719] I [glusterd-pmap.c:227:pmap_registry_bind] 0-pmap: adding brick /data/brick01bkp/Software_bkp on port 49154 [2015-01-26 14:52:53.586281] I [glusterd-pmap.c:227:pmap_registry_bind] 0-pmap: adding brick /data/brick02bkp/homegfs_bkp on port 49155 -- Original Message -- From: "David F. Robinson" To: "gluster-us...@gluster.org" ; "Gluster Devel" Sent: 1/26/2015 9:50:09 AM Subject: v3.6.2 I have a server with v3.6.2 from which I cannot mount using NFS. The FUSE mount works, however, I cannot get the NFS mount to work. From /var/log/message: Jan 26 09:27:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:27:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:28 gfs01bkp mount[2810]: mount to NFS server 'gfsib01bkp.corvidtec.com' failed: Connection refused, retrying Jan 26 09:29:53 gfs01bkp mount[4456]: mount to NFS server 'gfsib01bkp.corvidtec
