search for: dbchecke

I have been experiencing issues with an R script hanging when connecting to an Oracle database. To help debug, I found a function here in the nabble forum and made a small test script: #!/usr/bin/Rscript --no-restore --no-save --no-init-file library("RJDBC") drv<-JDBC("oracle.jdbc.OracleDriver","/home/oracle/lib/ojdbc6.jar", "'") dbCheck =

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 6 maart 2020 10:41 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] DCs from 4.10.x to 4.11.x > > Am 06.03.20 um 10:11 schrieb L.P.H. van Belle via samba: > > After upgrade indexing is done as far i know.

After updating our Samba4 server from alpha17 to beta8 "samba-tool dbcheck" shows 24 "incorrect GUID" errors. What does it mean and what should i do to fix this? Thx

Hi, Have changed the subject line to make my question clearer :) What is the expected behaviour of 'samba-tool dbcheck --fix'? Should running this command two times still produce the same output? I think I was bitten by bug 13228, but am not sure if I'm running the right command to resolve. Cheers Jonathan On 7 February 2018 at 23:44, Jonathan Hunter <jmhunter1 at

Hi everyone, yesterday I had to debug a failing join on a large domain for a group of primary schools with 1000+ desktop and 10k accounts. The domain run mostly ok except for some replications issues, however joining a new DC just takes eons and so does dbcheck. After some investigation into dbcheck (4.1.17) and some "human powered" valgrind like evalution using pudb, I came to the

I'm upgrading an old samba4 instance (Samba version: 4.3.0pre1-GIT-1e32ada) which despite it's age works fine. Running 'samba-tool dbcheck --cross-ncs' before the upgrade results in no errors. Building and installing using samba-4.7.3.tar.gz source (same ./configure) and the running 'samba-tool dbcheck --cross-ncs' results in 'Checked 3994 objects (4367

[Is it true that nobody replied to this in four months?] On Mon Jul 18 09:34:08 EDT 2011, Joseph L. Casale wrote: > Anyone else notice that /usr/libexec/bacula/make_catalog_backup.pl runs a "dbcheck -B" > which doesn't seem to exist in the version of dbcheck shipped with it? > > That makes it rather hard to do a catalogue backup with the shipped script? That's an

root at dom2:~# samba-tool dbcheck --fix --yes Checking 705 objects Checked 705 objects (0 errors) root at dom2:~# samba-tool dbcheck --cross-ncs Checking 4506 objects Not resetting nTSecurityDescriptor on CN=Deleted Objects,CN=Configuration,DC=tlk,DC=loc Not resetting nTSecurityDescriptor on CN=Deleted Objects,DC=DomainDnsZones,DC=tlk,DC=loc Not resetting nTSecurityDescriptor on CN=Deleted

.../python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _run return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/dbcheck.py", line 157, in run controls=controls, attrs=attrs) File "/usr/lib/python2.7/dist-packages/samba/dbchecker.py", line 222, in check_database error_count += self.check_object(object.dn, attrs=attrs) File "/usr/lib/python2.7/dist-packages/samba/dbchecker.py", line 2315, in check_object expected_dn = ldb.Dn(self.samdb, "RDN=RDN,%s" % (parent_dn)) ---------- As far a...

Hai,   Question..   2 DC's.  ( debian stretch samba 4.7.5 ) .   DC1 upgraded,  ( DC with FSMO roles)   samba-tool dbcheck --fix samba-tool dbcheck --cross-nc --fix   That fixed on DC1  6 errors. samba-tool drs showrepl show no error.   login on DC2. upgraded. samba-tool drs showrepl show no error and is in sync. samba-tool dbcheck --fix  shows 16 errors   uhm, synced, but not synced..   

I did it: root at dom2:~# samba-tool dbcheck --fix Checking 705 objects Reset nTSecurityDescriptor on CN=Deleted Objects,DC=tlk,DC=loc back to provision default? Owner mismatch: SY (in ref) DA(in current) Group mismatch: SY (in ref) DA(in current) Part dacl is different between reference and current here is the detail:

On Fri, 2024-04-12 at 08:03 +0200, Daniel M?ller via samba wrote: > Hello to all, > > After updating to samba 4.20 (from samba 4.19) on Debian 11, samba-tool > dbcheck --cross-ncs > results in: > samba-tool dbcheck --cross-ncs > Checking 4499 objects > Not resetting nTSecurityDescriptor on CN=Deleted > Objects,CN=Configuration,DC=tlk,DC=loc > Not resetting

On Mon, 15 Apr 2024 07:53:16 +0200 Daniel M?ller via samba <samba at lists.samba.org> wrote: > I did it: > root at dom2:~# samba-tool dbcheck --fix > Checking 705 objects > Reset nTSecurityDescriptor on CN=Deleted Objects,DC=tlk,DC=loc back > to provision default? Owner > mismatch: SY (in ref) DA(in current) Group mismatch: SY (in ref)

Hello, Today I tried to upgrade from samba 4.0.0 to 4.0.3 on my test environment. I patched the source with the diffs patch-4.0.0-4.0.1.diffs, patch-4.0.1-4.0.2.diffs, patch-4.0.2-4.0.3.diffs , then make, make install. # samba-tool dbcheck Checking 807 objects Not fixing nTSecurityDescriptor on CN=Performance Monitor Users,CN=Builtin,DC=inview,DC=local <--- all errors were

...177, in _run >> return self.run(*args, **kwargs) >> File >> "/usr/lib/python2.7/dist-packages/samba/netcmd/dbcheck.py", line >> 157, in run >> controls=controls, attrs=attrs) >> File >> "/usr/lib/python2.7/dist-packages/samba/dbchecker.py", line 222, >> in check_database >> error_count += self.check_object(object.dn, attrs=attrs) >> File >> "/usr/lib/python2.7/dist-packages/samba/dbchecker.py", line 2315, >> in check_object >> expected_dn = ldb.Dn(self.samdb, "...

...turn self.run(*args, **kwargs) > >> File > >> "/usr/lib/python2.7/dist-packages/samba/netcmd/dbcheck.py", line > >> 157, in run > >> controls=controls, attrs=attrs) > >> File > >> "/usr/lib/python2.7/dist-packages/samba/dbchecker.py", line 222, > >> in check_database > >> error_count += self.check_object(object.dn, attrs=attrs) > >> File > >> "/usr/lib/python2.7/dist-packages/samba/dbchecker.py", line 2315, > >> in check_object > >> expected_...

Recently upgraded my 3 dc's to samba 4.12.1 as part of the install ran dbcheck --cross-ncs on each dc after make install first dc dbcheck reported 5474 objectssecond dc reported 5476 objects last dc (the one with all the fsmo roles, etc.)? reported 1406 objects! now all of them report 1406 objects. (drs replication obviously) ADUC, DNS, GPO manager all seem to have the requisite data. I

...y", line 185, in _run return self.run(*args, **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 a...

Hi On 5 October 2012 21:25, <X-Dimension at gmx.net> wrote: > > -------- Original-Nachricht -------- >> Datum: Thu, 4 Oct 2012 12:22:54 +0200 >> Von: Michael Wood <esiotrot at gmail.com> >> An: Julian Timm <X-Dimension at gmx.net> >> CC: samba at lists.samba.org >> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after

Hi, Replying to my own query, for those following along at home (or reading the archives in the future). Thanks very much to Garming for giving me these pointers. My initial query probably wasn't very clear - apologies - but what it boiled down to was that "samba-tool dbcheck --cross-ncs" identified a number of errors, but these were *NOT* fixed when I ran the same command with