search for: 42cf

...ss-NCS shows two errors related to a de-comissionned DC (dc02) and cannot auto-fix this.. How do I fix those errors? [root at dc00 ~]# samba-tool dbcheck --cross-ncs --fix --yes Checking 3574 objects ERROR: no target object found for GUID component for link fromServer in object CN=4b3f95b1-7774-42cf-8bc0-755c7d29f6cc,CN=LostAndFoundConfig,CN=Configuration,DC=ad,DC=lasthome,DC=solace,DC=krynn - <GUID=c8bf60b8-c3b9-442f-a330-d706221bc889>;CN=NTDS Settings\0ADEL:c8bf60b8-c3b9-442f-a330-d706221bc889,CN=DC02\0ADEL:53a02791-a186-4a2f-aef9-6e180b814d8a,CN=Servers,CN=Krynn,CN=Sites,CN=Configur...

...) >> and cannot auto-fix this.. How do I fix those errors? >> >> [root at dc00 ~]# samba-tool dbcheck --cross-ncs --fix --yes >> Checking 3574 objects >> ERROR: no target object found for GUID component for link fromServer >> in object >> CN=4b3f95b1-7774-42cf-8bc0-755c7d29f6cc,CN=LostAndFoundConfig,CN=Configuration,DC=ad,DC=lasthome,DC=solace,DC=krynn >> - <GUID=c8bf60b8-c3b9-442f-a330-d706221bc889>;CN=NTDS >> Settings\0ADEL:c8bf60b8-c3b9-442f-a330-d706221bc889,CN=DC02\0ADEL:53a02791-a186-4a2f-aef9-6e180b814d8a,CN=Servers,CN=Krynn,CN...

...o a de-comissionned DC (dc02) > and cannot auto-fix this.. How do I fix those errors? > > [root at dc00 ~]# samba-tool dbcheck --cross-ncs --fix --yes > Checking 3574 objects > ERROR: no target object found for GUID component for link fromServer > in object > CN=4b3f95b1-7774-42cf-8bc0-755c7d29f6cc,CN=LostAndFoundConfig,CN=Configuration,DC=ad,DC=lasthome,DC=solace,DC=krynn > - <GUID=c8bf60b8-c3b9-442f-a330-d706221bc889>;CN=NTDS > Settings\0ADEL:c8bf60b8-c3b9-442f-a330-d706221bc889,CN=DC02\0ADEL:53a02791-a186-4a2f-aef9-6e180b814d8a,CN=Servers,CN=Krynn,CN=Sites,C...

...this.. How do I fix those errors? > >> > >> [root at dc00 ~]# samba-tool dbcheck --cross-ncs --fix --yes > >> Checking 3574 objects > >> ERROR: no target object found for GUID component for link > >> fromServer in object > >> CN=4b3f95b1-7774-42cf-8bc0-755c7d29f6cc,CN=LostAndFoundConfig,CN=Configuration,DC=ad,DC=lasthome,DC=solace,DC=krynn > >> - <GUID=c8bf60b8-c3b9-442f-a330-d706221bc889>;CN=NTDS > >> Settings\0ADEL:c8bf60b8-c3b9-442f-a330-d706221bc889,CN=DC02\0ADEL:53a02791-a186-4a2f-aef9-6e180b814d8a,CN=Servers,C...

...acl > sysvolreset' This is what the sysvolcheck returns: # samba-tool ntacl sysvolcheck ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO directory /usr/local/samba/var/locks/sysvol/my.example.com/Policies/{E2BC0255-64C8- 42CF-A27A-59A7D3DCD2DC} O:DAG:DAD:PAI(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;EA)(A;OICIIO; 0x001f01ff;;;CO)(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;SY)(A;OICI; 0x001200a9;;;AU)(A;OICI;0x001200a9;;;ED) does not match expected value O:DAG:DAD:P(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;EA)(A;OI...

Hi Denis, Thanks for taking the time to answer. Yes, I may have been wrong with --forced-sync and --full-sync since the start but in fact I wanted to make sure to force replication between the servers. Here is what I have noticed: - replication works from dc00 -> dc00 but not from dc01 -> dc00: [root at dc00 ~]# samba-tool drs replicate DC01 DC00 dc=ad,dc=lasthome,dc=solace,dc=krynn

...; This is what the sysvolcheck returns: > # samba-tool ntacl sysvolcheck > ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - > ProvisioningError: DB ACL on GPO directory > /usr/local/samba/var/locks/sysvol/my.example.com/Policies/{E2BC0255-64C8- > 42CF-A27A-59A7D3DCD2DC} > O:DAG:DAD:PAI(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;EA)(A;OICIIO; > 0x001f01ff;;;CO)(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;SY)(A;OICI; > 0x001200a9;;;AU)(A;OICI;0x001200a9;;;ED) does not match expected value > O:DAG:DAD:P(A;OICI;0x001f01ff;;;DA)(A;OICI;0...

...nsec: NT_STATUS_INVALID_SERVER_STATE =================================== Windows system log provides: =================================== The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=Machine,cn={E2BC0255-64C8-42CF-A27A-59A7D3DCD2DC},cn=policies,cn= system,DC=my,DC=example,DC=com. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure. =================================== How to solve? Thanks, Chri...

On Sun, Oct 25, 2020 at 3:31 PM Rowland penny via samba <samba at lists.samba.org> wrote: > OK, if you look at the end of the permissions, there is a '+' sign, this > shows that extended acls set, to see these: > > getfacl /usr/local/samba/var/locks/sysvol The difference in acls is that the non-working domain includes: user:3000001:r-x user:3000002:rwx user:3000003:r-x

> It's needed after every GPO addition and edit. There must be a root > cause to hunt down somewhere. Or is it a bug in 4.13.0 ? Yes, and no. Yes, its a bug. No, in my opionion its an old setting thats just needs some updating. Try this. samba-tool ntacl set "O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01

..._10_2016&Policy=Microsoft.Policies.WindowsLogon::SyncForegroundPolicy > > The local system is Event ID 1096: > The processing of Group Policy failed. Windows could not apply the > registry-based policy settings for the Group Policy object > LDAP://CN=Machine,cn={E2BC0255-64C8-42CF-A27A-59A7D3DCD2DC},cn > =policies,cn= > system,DC=my,DC=example,DC=com. Group Policy settings will > not be resolved until this event is resolved. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc727302(v=ws.10)?redirectedfrom=MSDN So h...

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

...eb9358/AAC4004EC7A576C0D23B78198BD1D5FF875CF75B (54574cee-4bec-49e4-9f19-469f48232d25) on home-client-2 [2017-10-25 10:14:13.716172] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/8197318C6FEB2E83A50BADAA42CF502067F5992E (83d7d46d-3225-48d1-8380-f9a98fa195c0) on home-client-2 [2017-10-25 10:14:13.724896] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/47B6E3FFB341C2DF68862E46939D0F48F958C692 (d696f984-d44c-43e...