similar to: attributeID is not known in our schema, not fixing replPropertyMetaData

On Fri, 2017-05-26 at 13:32 +0200, Karan Blas via samba wrote: > I expected that someone had the same problem before. > > DBchecker module does not provide fix for this. The implication is > that the main Samba DC is working fine but does not allow replication > with other DCs. They report WERR_DS_DRA_INTERNAL_ERROR in samba-tool > dsr showrepl for two two sections:

On Sat, 2017-05-27 at 03:16 +0200, Karan Blas via samba wrote: > > > We found that replPropertyMetaData is uniquie for each user, setting > > > it empty "fix the error' but breaks the user object. > > > > Correct, if you delete replPropertyMetaData in any way, you totally > > break replication. > > > > dbcheck should wipe that part of

I expected that someone had the same problem before. DBchecker module does not provide fix for this. The implication is that the main Samba DC is working fine but does not allow replication with other DCs. They report WERR_DS_DRA_INTERNAL_ERROR in samba-tool dsr showrepl for two two sections: Configuration and the main one that contains the users. Other sections replicate fine. Promoting new DC

> > We found that replPropertyMetaData is uniquie for each user, setting > > it empty "fix the error' but breaks the user object. > > Correct, if you delete replPropertyMetaData in any way, you totally > break replication. > dbcheck should wipe that part of replPropertyMetaData with --fix but it is not implemented. If that attribute does non replicate, there

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run samba-tool drs showrepl without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]

It's amazing how long Samba just keeps running even when apparently everything's broken. In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on all of them, resulting in: graz-dc-sem: > Checking 3861 objects > Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId > Error:

On Thu, 2016-04-14 at 18:07 +0100, Jonathan Hunter wrote: > On 14 April 2016 at 13:37, Jonathan Hunter <jmhunter1 at gmail.com> > wrote: > > > # samba-tool dbcheck --cross-ncs > > Checking 4079 objects > > MYOBJ=value,OU=myou,DC=mydomain,DC=org,DC=uk: 0x00290001 > > MYOBJ=value,OU=myou,DC=mydomain,DC=org,DC=uk: 0x0029000a > >

Hello, Updated samba from 4.4.5 to 4.5.0. All DC's are Ubuntu 12.04.5 LTS. I install samba from source(./configure,make,make install). Looking at the release notes I see the section on "replPropertyMetaData Chnages". I run 'samba-tool dbcheck --cross-ncs --fix --yes' and see the errors and samba attempts to fix. ERROR: unsorted attributeID values in

Thank you, Andrew - I hadn't done so. (In a good way, I haven't yet had problems with samba that have caused me to delve quite so deeply into the DB :) so I'm not as familiar with the range of tools as I could be, sorry!) This has flagged up quite a few errors, all along the lines of: # samba-tool dbcheck --cross-ncs Checking 4079 objects MYOBJ=value,OU=myou,DC=mydomain,DC=org,DC=uk:

hi bringing this thread back to life i waited to ugprade to 4.5.0 and after installing it i get a lot the same errors for users and computers objects when runnung samba-tool dbcheck --cross-ncs Checked 4744 objects (4909 errors) ERROR: unsorted attributeID values in replPropertyMetaData on CN=50LPT01,OU=Computers,OU=50,OU=MAINOU,DC=DOMAIN,DC=MY Not fixing replPropertyMetaData on

Hi, About a year ago (I think I was using v4.2.x at the time), I extended the schema of my Samba AD. This worked just fine and since then I have been able to create and edit objects from my custom schema via ADSIEdit. This worked fine under 4.3.x as well - the last such object I successfully created was just over two months ago, at which point I was running some variant of 4.3.x (probably 4.3.5).

On Sun, 20 Nov 2016 20:12:11 -0500 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-11-21 at 13:55 +1300, Andrew Bartlett wrote: > > On Sun, 2016-11-20 at 16:50 -0500, Adam Tauno Williams via samba > > wrote: > > > On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba wrote: > > > > On Sun, 20 Nov 2016 15:55:08 -0500

Am 2017-12-06 um 13:20 schrieb Stefan G. Weichinger via samba: > Could it somehow be the case that the kerberos-ticket between DM and DC > runs out after X hours or so? > > Just guessing ... found this thread https://lists.samba.org/archive/samba/2017-October/211476.html sounds quite similar - klist showed no Kerberos ticket, did a kinit ... dunno? I also see this: # tail

Hi ..., I am trying to upgrade from Samba 4.4.4 to Samba 4.7.7 and I am facing an error similar to the one mentioned here - https://bugzilla.samba.org/show_bug.cgi?id=12297 https://bugzilla.samba.org/show_bug.cgi?id=12385 I get the following error message *every time* I run - samba-tool dbcheck --cross-ncs --fix --yes

Hai,   Environment, Debian Jessie.     I got reports about pc's unable to login into the samba ad dc domain. The trust between this workstation and the primary domain failed. This happend on a win7 and win10 pc. Now, this is "normaly" easy fixed,by rejoining the pc to the domain with the domain wizzard in windows. I noticed this didnt work anymore.   I was running without

Ive recently inherited an old samba installation which was originally migrated from a windows 2003 server. It was running samba 4.2.13 so i upgraded to 4.6.4. All is well and everything appears to be working correctly but get the following error error when running the db check tool: Fix replPropertyMetaData on CN=f37883ec-90f7-4ac3-b478-00a266e31f83,CN=NTDS

Hi all, We would appreciate some input here. Not sure where to look... We have three AD DCs, all running samba 4.5.10, and since a few days, the samba DCs are getting stuck regularly, at ramdon times. Happens to all three of them, randomly, and currently it is happening up to a few times per day..! Must be some common cause. For the rest, the systems appear fine, enough diskspace, nothing

On 03.07.19 18:04, Rowland penny via samba wrote: >>>> How do I get rid of these bogus Schema entries, and how do I fix the >>>> user account? >>> I do not think you can remove anything from the schema, but I believe >>> you can deactivate schema objects, try reading this: >>> >>>

hi im still running zarafa Product version: 7,2,1,51838 and when i ran the dbcheck i couldn't authenticate against ldap from zarafa webapp i'll try to upgrade to the latest samba and rerun again and see if it breaks it. Thanks for sharing your experience. Samba - General mailing list wrote > Hai, > > You can fix it, i did it here for my zarafa 7.2.3. after

On Fri, 2016-04-15 at 00:32 +0100, Jonathan Hunter wrote: > Thank you Andrew, really appreciated. > > I have now run 'samba-tool dbcheck --cross-ncs --fix' and it has > successfully fixed some errors; there were 110 previously, however > there are still 69 remaining after a second pass of dbcheck --fix. > > The remaining errors seem to be mainly of this form: >