search for: ldif_elements

...line 1358, in check_object normalised = self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, [val]) File "/usr/lib64/python2.7/site-packages/samba/samdb.py", line 672, in dsdb_normalise_attributes return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, ldif_elements) What policy of using new version of libraries for stable version of Samba? Can I fix domain provision with talloc-2.1.6 for samba-4.3.6? -- Andrey Cherepanov cas at altlinux.org

...> normalised = > self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, [val]) > File "/usr/lib64/python2.6/site-packages/samba/samdb.py", line 647, > in dsdb_normalise_attributes > return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, > ldif_elements) > > ---- > > The same is on DC2: > samba-tool drs showrepl > > ==== INBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=ad,DC=example,DC=com > Default-First-Site-Name\DC1 via RPC > DSA object GUID: ef78b5d8-520a-4aa9-9c45-6bfe550935f6 >...

...es(self.samdb_schema, >> attrname, [val]) >> File "/usr/lib64/python2.6/site-packages/samba/samdb.py", >> line 647, in dsdb_normalise_attributes >> return dsdb._dsdb_normalise_attributes(ldb, >> ldap_display_name, ldif_elements) >> >> ---- >> >> The same is on DC2: >> samba-tool drs showrepl >> >> ==== INBOUND NEIGHBORS ==== >> >> DC=DomainDnsZones,DC=ad,DC=example,DC=com >> Default-First-Site-Name\DC1 via RPC >&...

...check_object > normalised = self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, obj[attrname]) > File "/usr/lib/python2.7/dist-packages/samba/samdb.py", line 677, in dsdb_normalise_attributes > return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, ldif_elements) All these object classes were tests we did? years ago, and which have been "deleted" (I don't even remember by what mechanism) for almost as long. No object should still be using any of these, and on graz-dc-sem that's true. There is, however, a new class called taoUser with t...

...> normalised = > self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, [val]) > File "/usr/lib64/python2.7/site-packages/samba/samdb.py", line 672, > in dsdb_normalise_attributes > return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, > ldif_elements) > > What policy of using new version of libraries for stable version of > Samba? Can I fix domain provision with talloc-2.1.6 for samba-4.3.6? > Can I ask why you are building talloc separately ? If you build Samba normally, it will be built for you. I am no expert here, but I think...

...ect > normalised = > self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, > [val]) File "/usr/lib64/python2.7/site-packages/samba/samdb.py", > line 672, in dsdb_normalise_attributes > return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, > ldif_elements) > > What policy of using new version of libraries for stable version of > Samba? Can I fix domain provision with talloc-2.1.6 for samba-4.3.6? I am using debian jessie and have backported 4.3.6 from sid to jessie. Talloc is 2.1.5. No problems so far. Building separate packages is the w...

..._object > normalised = > self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, > [val]) File "/usr/lib/python2.7/dist-packages/samba/samdb.py", line > 677, in dsdb_normalise_attributes > return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, > ldif_elements) > It looks like it is falling over whilst trying to 'normalise' an entry in AD, could this be a 'locale' problem ?? Rowland

Hello, after migrating a samba NT-style domain from Samba 4.2.14-debian (debian 8.10) to samba 4.5.12-debian (debian 9.4) We copied all tdb-files to the new machine plus the smb.conf plus /etc/group. The old Samba has tdbsam as backend. we use the same domain and hostname on the new DC as it was set on the old system. We are using bind9 as DNS-backend in the new system. The "samba-tool

...t;> normalised = self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, obj[attrname]) >> File "/usr/lib/python2.7/dist-packages/samba/samdb.py", line 677, in dsdb_normalise_attributes >> return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, ldif_elements) > > All these object classes were tests we did? years ago, and which have > been "deleted" (I don't even remember by what mechanism) for almost as > long. No object should still be using any of these, and on graz-dc-sem > that's true. I would love to know how you d...

...malised = >> self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, >> [val]) File "/usr/lib/python2.7/dist-packages/samba/samdb.py", line >> 677, in dsdb_normalise_attributes >> return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, >> ldif_elements) >> > > It looks like it is falling over whilst trying to 'normalise' an entry > in AD, could this be a 'locale' problem ?? > > Rowland > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: applicatio...