Displaying 3 results from an estimated 3 matches for "a533".
Did you mean:
533
2014 Jan 16
1
Replication errors (WERR_DS_DRA_SCHEMA_MISMATCH)
...e of the Windows 2008R2 DC's, name=Stilton:
##################################
C:\Users\Administrator>repadmin /showrepl
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\STILTON
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 24f13466-e54e-4e61-a533-4626b06c17ec
DSA invocationID: 24f13466-e54e-4e61-a533-4626b06c17ec
==== INBOUND NEIGHBORS ======================================
DC=gigl,DC=polymtl,DC=ca
Default-First-Site-Name\ROQUEFORT via RPC
DSA object GUID: e1a21c83-3c3f-4fbb-bc5e-e2dcd1f2c5ac
Last attempt @ 2014-01-...
2017 Aug 02
0
connection to 10.5.6.32:49155 failed (Connection refused); disconnecting socket
This means shd client is not able to establish the connection with the
brick on port 49155. Now this could happen if glusterd has ended up
providing a stale port back which is not what brick is listening to. If you
had killed any brick process using sigkill signal instead of sigterm this
is expected as portmap_signout is not received by glusterd in the former
case and the old portmap entry is
2017 Aug 01
4
connection to 10.5.6.32:49155 failed (Connection refused); disconnecting socket
how critical is above?
I get plenty of these on all three peers.
hi guys
I've recently upgraded from 3.8 to 3.10 and I'm seeing weird
behavior.
I see: $gluster vol status $_vol detail; takes long timeand
mostly times out.
I do:
$ gluster vol heal $_vol info
and I see:
Brick
10.5.6.32:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER-CYTO-DATA
Status: Transport endpoint is not connected
Number