Displaying 5 results from an estimated 5 matches for "node003".
Did you mean:
node008
2017 Aug 24
1
using both ConnectTo and AutoConnect to avoid network partitions
...n.
- We see several log messages that we dont currently understand - Can you
comment on what they mean and if they are concerning? I've obfuscated IP's
and node names so please ignore those. Our tinc daemon command is: tincd -n
<vpn name>
-- Received short packet
-- Got REQ_KEY from node003 while we already started a SPTPS session!
-- Invalid packet seqno: 7951 != 1 from node003 (22.22.22.22 port 655)
-- Failed to verify SIG record from node003 (22.22.22.22 port 655)
-- message repeated 3 times: [ Received short packet]
-- Metadata socket read error for node004 (33.33.33.33 port 655):...
2014 Jun 27
1
geo-replication status faulty
...--------------------------------------------
[2014-06-26 17:09:08.795387] I [monitor(monitor):130:monitor] Monitor: starting gsyncd worker
[2014-06-26 17:09:09.358588] I [gsyncd(/data/glusterfs/vol0/brick0/brick):532:main_i] <top>: syncing: gluster://localhost:gluster_vol0 -> ssh://root at node003:gluster://localhost:gluster_vol1
[2014-06-26 17:09:09.537219] I [monitor(monitor):129:monitor] Monitor: ------------------------------------------------------------
[2014-06-26 17:09:09.540030] I [monitor(monitor):130:monitor] Monitor: starting gsyncd worker
[2014-06-26 17:09:10.137434] I [gsyncd(/...
2011 Mar 28
1
gluster 3.1.3 mount using nfs
...retrying(1) for: /mnt after 5 seconds
nfs mount: retry: giving up on: /mnt
and it was ok when I tried it in linux machine.
I attached the volume setting
Plz help me out.
Volume Name: isi
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: node003:/data02
Brick2: node004:/data02
Brick3: node005:/data02
Brick4: node006:/data02
Options Reconfigured:
nfs.rpc-auth-allow: 150.2.223.249
nfs.rpc-auth-unix: on
Cloud Computing Business Team
Andrew Kong Assistant Manager | andrew.kong at sk.com| T:+82-2-6400-4328 | M:+82-10-8776-5025
SK u-Tower, 25...
2017 Aug 22
3
using both ConnectTo and AutoConnect to avoid network partitions
Hi Guus
Thanks for clarifying. Some follow up questions:
- How do we patch 1.1pre14 with this fix? Or will there be a 1.1pre15 to
upgrade to?
- What is the workaround until we patch with this fix? Using a combination
of AutoConnect and ConnectTo?
- When we use ConnectTo, is it mandatory to have a cert file in the hosts/*
dir with an IP to ConnectTo ?
-nirmal
On Tue, Aug 22, 2017 at 12:10
2012 Jan 04
0
FUSE init failed
...volume
7:
8: volume test-volume-client-1
9: type protocol/client
10: option remote-host node002
11: option remote-subvolume /local
12: option transport-type tcp
13: end-volume
14:
15: volume test-volume-client-2
16: type protocol/client
17: option remote-host node003
18: option remote-subvolume /local
19: option transport-type tcp
20: end-volume
21:
22: volume test-volume-client-3
23: type protocol/client
24: option remote-host node004
25: option remote-subvolume /local
26: option transport-type tcp
27: end-volume
28:
29: v...