search for: tombstonelifetime

...un(*args, **kwargs) ? File "/opt/samba/lib/python3.6/site-packages/samba/netcmd/dbcheck.py", line 141, in run ??? check_expired_tombstones=selftest_check_expired_tombstones) ? File "/opt/samba/lib/python3.6/site-packages/samba/dbchecker.py", line 221, in __init__ ??? self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) === samba-tool dbcheck --cross-ncs --fix --yes ERROR(<class 'KeyError'>): uncaught exception - 'No such element' ? File "/opt/samba/lib/python3.6/site-packages/samba/netcmd/__init__.py", line 185, in _run ??? retu...

...mba/lib/python3.6/site-packages/samba/netcmd/dbcheck.py", >> line 141, in run >> ??? check_expired_tombstones=selftest_check_expired_tombstones) >> ? File "/opt/samba/lib/python3.6/site-packages/samba/dbchecker.py", >> line 221, in __init__ >> ??? self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) > > I think this is a python 3 problem, the code around line 221 in > dbchecker is this: > > ??????? res = samdb.search(base=ntds_service_dn, > ?????????????????????????? scope=ldb.SCOPE_BASE, > ?????????????????????????? express...

...6/site-packages/samba/netcmd/dbcheck.py", >>> line 141, in run >>> check_expired_tombstones=selftest_check_expired_tombstones) >>> ? File "/opt/samba/lib/python3.6/site-packages/samba/dbchecker.py", >>> line 221, in __init__ >>> ??? self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) >> >> I think this is a python 3 problem, the code around line 221 in >> dbchecker is this: >> >> ??????? res = samdb.search(base=ntds_service_dn, >> ?????????????????????????? scope=ldb.SCOPE_BASE, >> expres...

UNCLASSIFIED Hi Rowland No tombstonelifetime. Do I need to upgrade the schema? The current schema is 30 (Windows 2003). When I try to update the schema, I get the following error: Applying Sch31.ldf updates... Exception [Errno 2] No such file or directory I downloaded sch31.ldf and tried to apply that. samba-tool domain schemaupgrade --...

Hi, ok, now join(with samba 4.10.6) was ok, but same original error :-/ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter XXXXXXX\Administrator's password: session setup failed: NT_STATUS_INTERNAL_DB_CORRUPTION Regards; On 24/07/2019 10:17, Rowland penny via samba wrote: > On 24/07/2019 12:53, Carlos via samba wrote: >> HI >> >> As the reported

...**kwargs) File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/dbcheck.py", line 142, in run check_expired_tombstones=selftest_check_expired_tombstones) File "/usr/local/samba/lib64/python2.7/site-packages/samba/dbchecker.py", line 200, in __init__ self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) dbcheck ran fine before the upgrade Any ideas on how to fix this? My smb.conf is: # Global parameters [global] workgroup = SSUNIT050 realm = SSUNIT050.local netbios name = JULIUS server role = active directory domain controller server service...

...list, Does anybody know how to lower the tombstone lifetime in samba 4.5 or later? There used to be a wiki entry, but this has been deleted as it is probably not adequate anymore: https://wiki.samba.org/index.php/Restoring_deleted_AD_objects#Changing_the_defaults_for_msDS-deletedObjectLifetime_and_tombstoneLifetime I used to change the attribute tombstoneLifetime in CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration, but this doesn't seem to work anymore. Thanks and best regards, Tim

...> "/opt/samba/lib/python3.6/site-packages/samba/netcmd/dbcheck.py", line > 141, in run > ??? check_expired_tombstones=selftest_check_expired_tombstones) > ? File "/opt/samba/lib/python3.6/site-packages/samba/dbchecker.py", > line 221, in __init__ > ??? self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) > > === > > samba-tool dbcheck --cross-ncs --fix --yes > ERROR(<class 'KeyError'>): uncaught exception - 'No such element' > ? File > "/opt/samba/lib/python3.6/site-packages/samba/netcmd/__init__.py&quo...

The system described by https://lists.samba.org/archive/samba/2016-May/199829.html (Invalid data for index DN=@INDEX:OBJECTCLASS:DNSNODE) now appears to perform DNS updates correctly, all systems are 4.2.10-Debian, and we've been able to add a user and a new DC. (Thanks for the help!) Synchronisation between v-ward (the new local DC), and empire isn't entirely working, though. >

...s, **kwargs) File "/usr/local/samba4/lib/python3.6/site-packages/samba/netcmd/dbcheck.py", line 141, in run check_expired_tombstones=selftest_check_expired_tombstones) File "/usr/local/samba4/lib/python3.6/site-packages/samba/dbchecker.py", line 221, in __init__ self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) dbcheck did work initially after upgrading, but this is now occurring on all 3 DCs. regards -- Al Slater Essiell is a limited company registered in England with company number: 1957652 and VAT registered number: GB 760 2433 55. Our registered off...

Hi, all. What is greatest period for AD DC (non FSMO) can be unavailable, for example, because network segment is unavailable for long time (3, 4 weeks)? Is the controller will be removed from AD automatically? And what to do after this network segment will become available? I have read about tombstoneLifeTime attribute of Directory Service (Configuration, Services, Windows NT), which default value is 180 days. But what is about replication? Thank you for your explanation. Best regards, Valery

An awful response: change tombstoneLifetime : ) When deleting objects they go to recycle bin then to deleted objects then are deleted. This if you have some recycle bin working which is not the case by default I reckon. tombstoneLifetime is the number of days AD has to keep deleted objects before the real deletion. If you use the recycle b...

...DC, the same DC208 but its old object. This deleted object appears on every DIT except "schema" and "configuration" (both haven't changed for a while). Most important question: How can this be possible? A lower important question: How to get rid of that? Except modifying tombstoneLifetime. Cheers : )

...mba/netcmd/db >> check.py", >> line 141, in run >> check_expired_tombstones=selftest_check_expired_tombstones) >> File >> "/usr/local/samba4/lib/python3.6/site-packages/samba/dbchecker >> .py", line >> 221, in __init__ >> self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) >> >> >> dbcheck did work initially after upgrading, but this is now >> occurring on >> all 3 DCs. >> >> regards >> >> -- >> Al Slater >> >> Essiell is a limited company register...

...al/samba/lib64/python2.7/site-packages/samba/netcmd/d > bcheck.py", line 142, in run > check_expired_tombstones=selftest_check_expired_tombstones) > File > "/usr/local/samba/lib64/python2.7/site-packages/samba/dbchecke > r.py", line 200, in __init__ > self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) > > dbcheck ran fine before the upgrade > > Any ideas on how to fix this? > > My smb.conf is: > > # Global parameters > [global] > workgroup = SSUNIT050 > realm = SSUNIT050.local > netbios name = JULIUS >...

...4/lib/python3.6/site-packages/samba/netcmd/db > check.py", > line 141, in run > check_expired_tombstones=selftest_check_expired_tombstones) > File > "/usr/local/samba4/lib/python3.6/site-packages/samba/dbchecker > .py", line > 221, in __init__ > self.tombstoneLifetime = int(res[0]["tombstoneLifetime"][0]) > > > dbcheck did work initially after upgrading, but this is now > occurring on > all 3 DCs. > > regards > > -- > Al Slater > > Essiell is a limited company registered in England with > company number: 19...

Hi, To upgrade my secondary DC Samba 4.5-16 to 4.8 should I remove the smb.conf file in /etc/samba first? I remember I tried last month to upgrade from 4.5-16 to 4.7 and broke the installation. Or are just the procedures below enough? Create this file repo file for apt. echo "deb http://apt.van-belle.nl/debian stretch-samba48 main contrib non-free" | sudo tee -a

...KCC?). Sorry to say that but what else? Deleted object are objects which are not in use. They have something to do perhaps with replication but they MUST NOT be used as valid source (or destination) for replication. So, a bug. Question 2: as previously said I don't want to have to modify the tombstoneLifetime because this implies modifying the schema which is not something to perform regularly. What if: - object deletion can't be performed - removal of this replication path is not possible because the path does not really exist (not listed into KCC CONNECTION OBJECTS section of drs showrepl, not exi...

...ve the same name as the old one (we are not fussy about the surrounding OS, just the hostname and to a lesser extent the IP). > Do I have any options other than waiting 179 more days? I mean, besides a DeLorean with a Flux Capacitor, or cryogenic stasis… or (gulp) patience? You can change the tombstoneLifetime, but please turn it back up once you are done. Andrew Bartlett -- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Development and Support, Catalyst IT https://catalyst.net.nz/services/samba

...e (or destination) for replication. So, a > bug. It just means that it has in the past replicated from this DC, as the repsFrom entry is by GUID. It is transformed into a DN at presentation time for display. > > Question 2: as previously said I don't want to have to modify the > tombstoneLifetime because this implies modifying the schema which is > not > something to perform regularly. > What if: > - object deletion can't be performed > - removal of this replication path is not possible because the path > does > not really exist (not listed into KCC CONNECTION OBJEC...