search for: 40a0

...y.domain.tld. > Checking 0 100 389 DC1.my.domain.tld. against SRV > _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 > Failed to find matching DNS entry SRV > _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 > Looking for DNS entry SRV > _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld > DC2.my.domain.tld 389 as > _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld. > Checking 0 100 389 DC1.my.domain.tld. against SRV > _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld...

On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>

...389 as _ldap._tcp.dc._msdcs.my.domain.tld. Checking 0 100 389 DC1.my.domain.tld. against SRV _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 Failed to find matching DNS entry SRV _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 Looking for DNS entry SRV _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld DC2.my.domain.tld 389 as _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld. Checking 0 100 389 DC1.my.domain.tld. against SRV _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld DC2.my.domain.tld...

...hecking 0 100 389 DC1.my.domain.tld. against SRV >> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 >> Failed to find matching DNS entry SRV >> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 >> Looking for DNS entry SRV >> _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld >> DC2.my.domain.tld 389 as >> _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld. >> Checking 0 100 389 DC1.my.domain.tld. against SRV >> _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msd...

...my.domain.tld. against SRV > >> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 > >> Failed to find matching DNS entry SRV > >> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 > >> Looking for DNS entry SRV > >> _ldap._tcp.c2e92ed0-e889-40a0-a272- > 7375f90de91d.domains._msdcs.my.domain.tld > >> DC2.my.domain.tld 389 as > >> _ldap._tcp.c2e92ed0-e889-40a0-a272- > 7375f90de91d.domains._msdcs.my.domain.tld. > >> Checking 0 100 389 DC1.my.domain.tld. against SRV > >> _ldap._tcp.c2e92ed0-e889-40a0-a...

...1.my.domain.tld. against SRV >>> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 >>> Failed to find matching DNS entry SRV >>> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 >>> Looking for DNS entry SRV >>> _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld >>> DC2.my.domain.tld 389 as >>> _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de91d.domains._msdcs.my.domain.tld. >>> Checking 0 100 389 DC1.my.domain.tld. against SRV >>> _ldap._tcp.c2e92ed0-e889-40a0-a272-7375f90de...

...V > > >> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 > > >> Failed to find matching DNS entry SRV > > >> _ldap._tcp.dc._msdcs.my.domain.tld DC2.my.domain.tld 389 > > >> Looking for DNS entry SRV > > >> _ldap._tcp.c2e92ed0-e889-40a0-a272- > > 7375f90de91d.domains._msdcs.my.domain.tld > > >> DC2.my.domain.tld 389 as > > >> _ldap._tcp.c2e92ed0-e889-40a0-a272- > > 7375f90de91d.domains._msdcs.my.domain.tld. > > >> Checking 0 100 389 DC1.my.domain.tld. against SRV > > >> _...

...d-dc-failover-replication/ but basically most howtos discuss this the same way. - samba-tool drs showrepl on the old, existing DC (yes, it's named pdc) Default-First-Site-Name\PDC DSA Options: 0x00000001 DSA object GUID: 0b562545-29f5-4d2f-a6d9-81e4359fc6b1 DSA invocationId: 2c0b1f12-f0c5-40a0-8de1-a562a93b7839 ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=biuro,DC=gpm-vindexus,DC=pl Default-First-Site-Name\QDC via RPC DSA object GUID: 8d384b11-053d-486b-bfb6-3e00ff8d3d34 Last attempt @ Tue Apr 24 23:36:05 2018 CEST failed, result 2 (WERR_BADFILE) 10695 consecutive failure(s). Last...

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia

...Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 19 Region 0: I/O ports at 40a8 [size=8] Region 1: I/O ports at 40b4 [size=4] Region 2: I/O ports at 40a0 [size=8] Region 3: I/O ports at 40b0 [size=4] Region 4: I/O ports at 4060 [size=32] Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Co...

...p+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Latency: 0 >> Interrupt: pin B routed to IRQ 19 >> Region 0: I/O ports at 40a8 [size=8] >> Region 1: I/O ports at 40b4 [size=4] >> Region 2: I/O ports at 40a0 [size=8] >> Region 3: I/O ports at 40b0 [size=4] >> Region 4: I/O ports at 4060 [size=32] >> Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] >> Capabilities: <access denied> >> Kernel driver in use: ahci >> Kernel modules: ahci >&...

...;TAbort- >> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>> Latency: 0 >>>> Interrupt: pin B routed to IRQ 19 >>>> Region 0: I/O ports at 40a8 [size=8] >>>> Region 1: I/O ports at 40b4 [size=4] >>>> Region 2: I/O ports at 40a0 [size=8] >>>> Region 3: I/O ports at 40b0 [size=4] >>>> Region 4: I/O ports at 4060 [size=32] >>>> Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] >>>> Capabilities: <access denied> >>>> Kernel driver in use: a...

...- <PERR- INTx- >>>>>> Latency: 0 >>>>>> Interrupt: pin B routed to IRQ 19 >>>>>> Region 0: I/O ports at 40a8 [size=8] >>>>>> Region 1: I/O ports at 40b4 [size=4] >>>>>> Region 2: I/O ports at 40a0 [size=8] >>>>>> Region 3: I/O ports at 40b0 [size=4] >>>>>> Region 4: I/O ports at 4060 [size=32] >>>>>> Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] >>>>>> Capabilities: <access denied> &...

...Tx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin B routed to IRQ 19 > Region 0: I/O ports at 40a8 [size=8] > Region 1: I/O ports at 40b4 [size=4] > Region 2: I/O ports at 40a0 [size=8] > Region 3: I/O ports at 40b0 [size=4] > Region 4: I/O ports at 4060 [size=32] > Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] > Capabilities: <access denied> > Kernel driver in use: ahci > Kernel modules: ahci > > 00:1f.3 SMBus: Int...

...ParErr- DEVSEL=medium >TAbort- ><TAbort- <MAbort- >SERR- <PERR- INTx- >>> Latency: 0 >>> Interrupt: pin B routed to IRQ 19 >>> Region 0: I/O ports at 40a8 [size=8] >>> Region 1: I/O ports at 40b4 [size=4] >>> Region 2: I/O ports at 40a0 [size=8] >>> Region 3: I/O ports at 40b0 [size=4] >>> Region 4: I/O ports at 4060 [size=32] >>> Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] >>> Capabilities: <access denied> >>> Kernel driver in use: ahci >>> Ke...

...<MAbort- >SERR- <PERR- INTx- >>>>> Latency: 0 >>>>> Interrupt: pin B routed to IRQ 19 >>>>> Region 0: I/O ports at 40a8 [size=8] >>>>> Region 1: I/O ports at 40b4 [size=4] >>>>> Region 2: I/O ports at 40a0 [size=8] >>>>> Region 3: I/O ports at 40b0 [size=4] >>>>> Region 4: I/O ports at 4060 [size=32] >>>>> Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] >>>>> Capabilities: <access denied> >>>>&...

...t;>>>>>> Latency: 0 >>>>>>> Interrupt: pin B routed to IRQ 19 >>>>>>> Region 0: I/O ports at 40a8 [size=8] >>>>>>> Region 1: I/O ports at 40b4 [size=4] >>>>>>> Region 2: I/O ports at 40a0 [size=8] >>>>>>> Region 3: I/O ports at 40b0 [size=4] >>>>>>> Region 4: I/O ports at 4060 [size=32] >>>>>>> Region 5: Memory at f423c000 (32-bit, non-prefetchable) [size=2K] >>>>>>> Capabilities: <acc...

...[ 4060: 84 2e 46 4e 30 30 00 00 00 14 0b 5f 53 54 41 08 ..FN00....._STA. 4070: a4 56 46 4e 30 14 0c 5f 4f 4e 5f 08 70 01 56 46 .VFN0.._ON_.p.VF 4080: 4e 30 14 0c 5f 4f 46 46 08 70 00 56 46 4e 30 5b N0.._OFF.p.VFN0[ 4090: 82 21 46 41 4e 30 08 5f 48 49 44 0c 41 d0 0c 0b .!FAN0._HID.A... 40a0: 08 5f 55 49 44 00 08 5f 50 52 30 12 06 01 46 4e ._UID.._PR0...FN 40b0: 30 30 5b 84 2e 46 4e 30 31 00 00 00 14 0b 5f 53 00[..FN01....._S 40c0: 54 41 08 a4 56 46 4e 31 14 0c 5f 4f 4e 5f 08 70 TA..VFN1.._ON_.p 40d0: 01 56 46 4e 31 14 0c 5f 4f 46 46 08 70 00 56 46 .VFN1.._OFF.p.VF 40e0: 4e...

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