<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 14/10/2019 08:33, Sanju Rakonde
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABj3WN0VxsmvWdSHZU9rE=g5W825baGXCCYNaRLebnMWzPSuug@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">please check contents of /var/lib/glusterd/peers/
directory, it should not have any information regarding the
localhost. Please check the uuid of the local node at
/var/lib/glusterd/<a href="http://glusterd.info"
moz-do-not-send="true">glusterd.info</a> file and figure out
if you have a file with this uuid at /var/lib/glusterd/peers/*.
If you find any such file, please delete it and restart glusterd
on that node.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Oct 11, 2019 at 3:15
PM lejeczek <<a href="mailto:peljasz@yahoo.co.uk"
moz-do-not-send="true">peljasz@yahoo.co.uk</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hi
guys,<br>
<br>
as per the subject.<br>
<br>
Only one thing that I'd like to tell first is that on that
peer/node<br>
Samba runs. Other two peers do not show this in their logs.<br>
<br>
I gluster log for the volume I get plenty of:<br>
<br>
...<br>
<br>
t)<br>
[2019-10-11 09:40:40.768647] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:40:43.777129] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:40:46.785522] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:40:49.794393] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:40:52.805158] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:40:55.817603] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:40:58.826136] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:41:01.836104] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
[2019-10-11 09:41:04.842676] E [socket.c:3498:socket_connect]<br>
0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer"
target="_blank" moz-do-not-send="true">127.0.0.1:24007</a>
failed, (Invalid<br>
argument)<br>
...<br>
<br>
Cluster runs off Centos 7 an ver is 6.5.<br>
<br>
glusterd.vol is on all three peers as here:<br>
<br>
volume management<br>
type mgmt/glusterd<br>
option working-directory /var/lib/glusterd<br>
option transport-type socket,rdma<br>
option transport.socket.keepalive-time 10<br>
option transport.socket.keepalive-interval 2<br>
option transport.socket.read-fail-log off<br>
option transport.socket.listen-port 24007<br>
option transport.rdma.listen-port 24008<br>
option ping-timeout 0<br>
option event-threads 1<br>
# option lock-timer 180<br>
# option transport.address-family inet6<br>
# option base-port 49152<br>
option max-port 60999<br>
end-volume<br>
<br>
Any thoughts & suggestions very appreciated.<br>
<br>
Many thanks, L.<br>
<br>
________<br>
<br>
Community Meeting Calendar:<br>
<br>
APAC Schedule -<br>
Every 2nd and 4th Tuesday at 11:30 AM IST<br>
Bridge: <a href="https://bluejeans.com/118564314"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://bluejeans.com/118564314</a><br>
<br>
NA/EMEA Schedule -<br>
Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
Bridge: <a href="https://bluejeans.com/118564314"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://bluejeans.com/118564314</a><br>
<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank"
moz-do-not-send="true">Gluster-users@gluster.org</a><br>
<a
href="https://lists.gluster.org/mailman/listinfo/gluster-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>Thanks,<br>
</div>
Sanju<br>
</div>
</div>
</blockquote>
<p>okey, @devel - this might be worth more investigation &
should be easy to reproduce.</p>
<p>These errors will show up if a user, in my case it was user's
home fuse-mounted, is accessing some files, in my case it was just
a shell session but(& maybe only in this specific scenario)
with 'screen' program upon login - and (in my case) automount was
restart (and possibly gluster's vol or gluster itself was
re/started).</p>
<p>I spotted it here:</p>
<p>$ sudo journalctl -lf -o cat -u autofs
<br>
...
<br>
setautomntent: lookup(sss): setautomntent: No such file or
directory
<br>
mounted indirect on /misc with timeout 300, freq 75 seconds
<br>
ghosting enabled
<br>
mounted indirect on /net with timeout 300, freq 75 seconds
<br>
ghosting enabled
<br>
mounted indirect on /0-ALL.DATA with timeout 300, freq 75 seconds
<br>
ghosting enabled
<br>
mounted indirect on /0-ALL.SYSDATA with timeout 300, freq 75
seconds
<br>
ghosting enabled
<br>
mounted indirect on /home with timeout 300, freq 75 seconds
<br>
re-connected to /home/jt455
<br>
ghosting enabled
<br>
</p>
<p>The user got logged out(or any user accessing fuse-mounted
gluster vol) and autofs restarted (errors gone) and gluster
stopped spitting out:</p>
<p>0-glusterfs: connection attempt on <a
href="http://127.0.0.1:24007" rel="noreferrer" target="_blank">127.0.0.1:24007</a>
failed, (Invalid argument)</p>
<p>many thanks, L<br>
</p>
</body>
</html>