[Samba] Error with dbcheck after upgrade to 4.10.2
pinja-liina.jalkanen at vihreat.fi
Wed May 22 15:18:20 UTC 2019
Interestingly, for me this resolved itself upon upgrading from Samba 4.8
to 4.9. But, at the same time the build configuration changed, because I
did what I had been considering to do a long time: stopped compiling
Samba by myself and started to use whatever is cureently shipped with
Debian (in this case Buster; 4.9.5+dfsg-4). I migrated data to the right
directories manually on each DC (locks, private & smb.conf) before
restarting Samba post-upgrade, and everything seems to be working again;
no replication errors, and only two minor errors on dbcheck that were
fixed by it.
Anyway, the issue looks like it's not limited to 4.10, because for me it
occurred on 4.8 as well, but then not on 4.9.
On 29/04/2019 19.26, Pinja-Liina Jalkanen via samba wrote:
> Hi Louis and others,
> While I cannot speak for the GP, I've had this same problem since I
> recently (finally!) upgraded to Samba 4.8 (4.8.11). In fact, the very
> reason I wanted to run dbcheck for was to confirm that Samba still works
> correctly after upgrading (it does seem to replicate normally, anyway).
> I've configured Samba with the following switches:
> --enable-debug --enable-selftest --prefix=/usr/local/samba4
> --localstatedir=/var/lib/samba4 --sysconfdir=/etc/samba4
> --with-logfilebase=/var/log/samba4 --with-piddir=/var/run/samba4
> --with-sockets-dir=/var/run/samba4 --with-cachedir=/var/cache/samba4
> # Global parameters
> workgroup = SAMDOM
> realm = samba.domain
> netbios name = dc1
> server role = active directory domain controller
> server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
> winbindd, ntp_signd, kcc, dnsupdate
> idmap_ldb:use rfc2307 = yes
> template homedir = /home/%ACCOUNTNAME%
> template shell = /bin/bash
> path = /var/lib/samba4/locks/sysvol/samba.domain/scripts
> read only = No
> path = /var/lib/samba4/locks/sysvol
> read only = No
> Worth perhaps mentioning that the setup is quite old, having been
> upgraded all the way from Samba 4.0. The same compile switches have most
> likely already been in use back then.
> I wish that a solution could be found, for the setup feels a bit fragile
> when dbcheck doesn't work. And for the 4.8 there is no downgrade option...
>  I'm currently not planning to upgrade to Samba 4.9 until after
> Debian 10 "Buster" is released. Past that I may consider migrating to
> the distro-supplied Samba.
> On 25/04/2019 16.01, L.P.H. van Belle via samba wrote:
>> What is the OS?
>> Samba version you did upgrade from?
>> I see you compiled samba, can you share the build parameters?
>> And smb.conf with this might be handy.
>> AD-DC or Member or other?
>> If AD-DC, with or without bind9_DLZ
>> Sorry, but more info is better..
>>> -----Oorspronkelijk bericht-----
>>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Al
>>> Slater via samba
>>> Verzonden: donderdag 25 april 2019 13:07
>>> Aan: samba at lists.samba.org
>>> Onderwerp: [Samba] Error with dbcheck after upgrade to 4.10.2
>>> I am seeing the following error when running samba-tool dbcheck
>>> # samba-tool dbcheck --cross-ncs
>>> ERROR(<class 'KeyError'>): uncaught exception - 'No such element'
>>> line 185, in _run
>>> return self.run(*args, **kwargs)
>>> line 141, in run
>>> .py", line
>>> 221, in __init__
>>> self.tombstoneLifetime = int(res["tombstoneLifetime"])
>>> dbcheck did work initially after upgrading, but this is now
>>> occurring on
>>> all 3 DCs.
>>> Al Slater
>>> Essiell is a limited company registered in England with
>>> company number: 1957652 and VAT registered number: GB 760
>>> 2433 55. Our registered office is at 5th Floor, Park Gate,
>>> 161-163 Preston Road, Brighton, East Sussex BN1 6AU.
>>> This message is intended solely for the addressee and may
>>> contain confidential information. It may also contain
>>> material which is subject to legal privilege. If you have
>>> received this message in error please delete it and all
>>> copies from your system and notify us immediately by return email.
>>> For information about how we process data and monitor
>>> communications please read our Privacy
>>> Policy<https://essiell.com/privacy-policy> and Cookie
>>> Policy<https://essiell.com/cookie-policy>. And please read
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions: https://lists.samba.org/mailman/options/samba
More information about the samba