similar to: samba AD database suspected corruption

Hi, Back in the samba 4.1 days, we experienced a samba database corruption: tombstones not being deleted from sam.lbd, ultimately resulting in a huge database, full root disk, samba crashing, we were completely down. We asked the great guys at sernet to help, they did super work, and managed to get us up and running again, including the addition of a fresh DC4. Currently on 4.5.15, we have

Try again with : samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST As in dc5.your.dns.domain.tld ... Whats the result.? If it fails, please tell os your: OS? Content of /etc/hosts /etc/resolv.conf /etc/nsswitch.conf /etc/samba/smb.conf > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mike > Ray via samba >

All- I've got 3 DCs (version 4.9.6-12) that, prior to today, were running without issue (as best I could tell). Every night I run a few commands to monitor the status of the DCs/domain. I run: * dbcheck --cross-ncs * samba-tool drs kcc <other DCs> * samba-tool ldapcmp <local DC> <other DCs> (domain|configuration|schema|dnsdomain|dnsforest) * samba-tool drs showrepl These

----- On Apr 23, 2019, at 11:34 AM, samba samba at lists.samba.org wrote: > On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) > Mike Ray via samba <samba at lists.samba.org> wrote: > >> About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, >> things are functioning. >> >> However, I have come across several strange behaviors and wandered if >>

On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) Mike Ray via samba <samba at lists.samba.org> wrote: > About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, > things are functioning. > > However, I have come across several strange behaviors and wandered if > anyone else has noticed similar behavior on 4.9.6 or has any > suggestions of what might be occurring. >

About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, things are functioning. However, I have come across several strange behaviors and wandered if anyone else has noticed similar behavior on 4.9.6 or has any suggestions of what might be occurring. As background information, I have 3 DCs (dc3, dc4 and dc5) -- all running the same version (4.9.6) and all have the same configuration;

On 22/05/2019 16:29, Mike Ray via samba wrote: > ----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: > >> Try again with : >> >> samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST >> As in dc5.your.dns.domain.tld ... >> >> Whats the result.? > The failure is still present -- no change in the output of the command:

----- On May 22, 2019, at 11:07 AM, samba samba at lists.samba.org wrote: > On 22/05/2019 16:29, Mike Ray via samba wrote: >> ----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: >> >>> Try again with : >>> >>> samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST >>> As in dc5.your.dns.domain.tld ...

----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: > Try again with : > > samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST > As in dc5.your.dns.domain.tld ... > > Whats the result.? The failure is still present -- no change in the output of the command: # samba-tool ldapcmp dc3.domain.local dc5.domain.local DNSFOREST ERROR(ldb):

Le 19/11/2018 à 15:00, Julien TEHERY via samba a écrit : > Le 19/11/2018 à 12:33, Julien TEHERY via samba a écrit : >> Le 19/11/2018 à 11:14, Marco Gaiarin via samba a écrit : >>> Mandi! Julien TEHERY via samba >>>    In chel di` si favelave... >>> >>>> Is there a good pratice when adding new remote DCs in terms of >>>> replication

Hi all, I have just updated our dc's from sernet 4.1.11 to sernet 4.1.12. And suddenly since that update, we're getting many ldapcmp failures on the attribute 'whenChanged'. In 4.1.11 life was good, and ldapcmp reported no differences at all. Here is a sample: (dc2 <-> dc3) Comparing: 'CN=podcast,CN=Users,DC=samba,DC=company,DC=com' [ldap://dc2]

Cordialement, Doe Corp <https://www.openevents.fr/> <https://www.facebook.com/OPENevents-172305449504004/> <https://twitter.com/SocOPENevents> <https://www.linkedin.com/company/openevents/> Julien Téhéry Ingénieur Systèmes & Réseaux | OPENevents 15 avenue de l'Europe 86170 Neuville de Poitou phone : +33 5 49 62 26 03 <tel:+33549622603> mail :

Hello guys, Why did you upgrade the schema to '69' ? > > That is the schema from 2012R2 and is still marked as experimental. I do not know why I did this update. Maybe I thought I could use DC as 2012R2. <sad> Could you run : > samba-tool ldapcmp ldap://dc3 ldap://dc4 --filter=cn,CN,dc,DC > And compair that output? I made the comparison. It has a jumble of

Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba < samba at lists.samba.org> wrote: > Hai, > > Now, differences is fine, but can you see if one of the 2 servers is > correct, and for that it might be handy to share the output. > > You can push the good DB to the

Hello, I had posted this in another topic, but because the problem is different, I decided to create a new topic. Conf: - Primary DC/pdc Emulator as DC3 - Second DC as DC4 After an upgrade from schema 45 to 69 in DCs, when adding a computer in the domain and if the domain to respond is DC4 the synchronization for DC3 is not done. I already did several tests that I already knew and also new

On 16/11/2020 12:56, mj via samba wrote: > Hi all, > > We are running a three DC samba AD, using 4.12.8 sernet packages. Very > stable for years. > > Today at 12:30 my colleague moved two users from > * CN=Users,DC=samba,DC=company,DC=com > to > * OU=disabled,DC=samba,DC=company,DC=com > > This change was done on the DC4 at 12:30 using LAM >

Hi, I migrated our DCs from 4.5/internal dns to 4.7.1/bind9_dlz. Short summary of the steps taken: - added a new temp dc, - removed the old DCs - cleaned sam database - installed new DCs, with their old dns/ip - removed the temp dc again - synced sysvol and all is looking well: no db errors, no replication issues, ldapcmp matches across DCs, etc. So, I took things to production today, and

im on phone, had a quick small look at the dc3 output. is your time in sync, it looks like a 3 - 10 min different. gr. Louis Op 7 mei 2019, om 18:34, Elias Pereira <empbilly at gmail.com> schreef: Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba <samba at

Hai Mason,   I had a look at the debug output.   on 1) why around 15-16 second, that i really dont know. im trying to figure that out. on 2) if DNS is inconsistance, that everything is unrelayable. This is really the first the that needs fixing. then we look again at the replication.   The debug output still shows several messages about zones in flat files. I still do believe also that this

Could you run : samba-tool ldapcmp ldap://dc3 ldap://dc4 --filter=cn,CN,dc,DC And compair that output? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Elias Pereira via samba > Verzonden: dinsdag 7 mei 2019 15:48 > Aan: samba > Onderwerp: [Samba] DN lists have different size: 4065 != 4029 > >