search for: 4bc0

...9d2 Last attempt @ Tue Mar 14 09:26:12 2017 CDT was successful 0 consecutive failure(s). Last success @ Tue Mar 14 09:26:12 2017 CDT DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa Last attempt @ Tue Mar 14 09:25:09 2017 CDT was successful 0 consecutive failure(s). Last success @ Tue Mar 14 09:25:09 2017 CDT DC=DomainDnsZones,DC=mediture,DC=dom epo\EPO-DC01 via RPC DSA object GUID:...

...even trying because last successful was epoch (never) yet there are no errors. Inbound replication for this DC seems fine. [root at vsc-dc02 ~]# samba-tool drs showrepl [...]==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa Last attempt@ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=mediture,DC=dom epo\EPO-DC01 via RPC DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 Last attempt@ NTTIME(0) was successful 0 consecutive failure(s)...

...Inbound >> replication for this DC seems fine. >> >> [root at vsc-dc02 ~]# samba-tool drs showrepl >> [...]==== OUTBOUND NEIGHBORS ==== >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt@ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-48...

...pt @ Tue Mar 14 09:26:12 2017 CDT was > successful > 0 consecutive failure(s). > Last success @ Tue Mar 14 09:26:12 2017 CDT > > DC=DomainDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC > DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa > Last attempt @ Tue Mar 14 09:25:09 2017 CDT was > successful > 0 consecutive failure(s). > Last success @ Tue Mar 14 09:25:09 2017 CDT > > DC=DomainDnsZones,DC=mediture,DC=dom > epo\EPO-DC01 via RPC &g...

I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc =

...as epoch (never) yet there are no errors. Inbound replication for > this DC seems fine. > > [root at vsc-dc02 ~]# samba-tool drs showrepl > [...]==== OUTBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC > DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa > Last attempt@ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=DomainDnsZones,DC=mediture,DC=dom > epo\EPO-DC01 via RPC > DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 > Last attempt@ NTTIME(0) wa...

...ion for this DC seems fine. >>> >>> [root at vsc-dc02 ~]# samba-tool drs showrepl >>> [...]==== OUTBOUND NEIGHBORS ==== >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt@ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA o...

Executing the following with nsupdate seems to have fixed replication. update add 28f7281f-3955-4885-8a7d-42a36ee87590._msdcs.mediture.dom. 900 A 192.168.222.5 show send update add 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa._msdcs.mediture.dom. 900 A 172.16.1.106 show send update add fe066b13-6f9e-4f3c-beb4-37df1292b8cb._msdcs.mediture.dom. 900 A 192.168.168.65 show send New DNS records I create don't resolve though. Also, I get an error when I open Active Directory Users and Computers, &quot...

Replication has been running smoothly until I upgraded to 4.5.0. I had various errors with all BDCs and a force sync didn't resolve it. I shutdown all BDCs, demoted them with --remove-other-dead-server then joined new BDCs with new names. At first replication was intermittently failing (consecutive failures counter kept resetting), but it seemed OK, just slow if anything. Now they all

...b80: 42 5f 50 43 49 30 52 50 30 32 48 50 53 58 a0 43 B_PCI0RP02HPSX.C 4b90: 0b 90 93 52 50 33 44 00 5c 2f 04 5f 53 42 5f 50 ...RP3D.\/._SB_P 4ba0: 43 49 30 52 50 30 33 48 50 53 58 5b 22 0a 64 a0 CI0RP03HPSX[".d. 4bb0: 4b 07 5c 2f 04 5f 53 42 5f 50 43 49 30 52 50 30 K.\/._SB_PCI0RP0 4bc0: 33 50 44 43 58 70 01 5c 2f 04 5f 53 42 5f 50 43 3PDCXp.\/._SB_PC 4bd0: 49 30 52 50 30 33 50 44 43 58 70 01 5c 2f 04 5f I0RP03PDCXp.\/._ 4be0: 53 42 5f 50 43 49 30 52 50 30 33 48 50 53 58 a0 SB_PCI0RP03HPSX. 4bf0: 2a 92 5c 2f 04 5f 53 42 5f 50 43 49 30 52 50 30 *.\/._SB_PCI0RP0 4c00: 33...

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...1C78260C0C38374 (7096f154-682c-4708-a335-010acbbc255c) on home-client-2 [2017-10-25 10:14:04.022795] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/7EC0241DB6D8540755D5382D8F6676A6A0C34DCF (5d87d01c-10e7-4bc0-8e35-219bf8058027) on home-client-2 [2017-10-25 10:14:04.137725] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/860849D3B22E69998CCCD52010E039FDFB945997 (861e6f04-e34d-4713-97aa-ed4e91fb7fe8) on home-cli...