I build new version of talloc-2.1.6 (build from external tarball) and
samba-4.3.6.
But if I provision domain by command
samba-tool domain provision --realm=test.alt --domain test
--adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc
--use-rfc2307 --use-xattrs=yes
I got error:
Fixing provision GUIDs
ERROR(runtime): uncaught exception - pytalloc_reference_ex() called for
object type not based on talloc
File "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py",
line 175, in _run
return self.run(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/samba/netcmd/domain.py",
line 442, in run
nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode)
File
"/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", line
2172, in provision
skip_sysvolacl=skip_sysvolacl)
File
"/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", line
1864, in provision_fill
attrs=['defaultObjectCategory'])
File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", line
138, in check_database
error_count += self.check_object(object.dn, attrs=attrs)
File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", 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
On 12/03/16 14:20, Andrey Cherepanov wrote:> I build new version of talloc-2.1.6 (build from external tarball) and > samba-4.3.6. > But if I provision domain by command > > samba-tool domain provision --realm=test.alt --domain test > --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc > --use-rfc2307 --use-xattrs=yes > > I got error: > Fixing provision GUIDs > ERROR(runtime): uncaught exception - pytalloc_reference_ex() called > for object type not based on talloc > File "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py", > line 175, in _run > return self.run(*args, **kwargs) > File "/usr/lib64/python2.7/site-packages/samba/netcmd/domain.py", > line 442, in run > nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode) > File > "/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", line > 2172, in provision > skip_sysvolacl=skip_sysvolacl) > File > "/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", line > 1864, in provision_fill > attrs=['defaultObjectCategory']) > File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", line > 138, in check_database > error_count += self.check_object(object.dn, attrs=attrs) > File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", 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? >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 Samba relies on the builtin version of Samba. Rowland
12.03.2016 17:57, Rowland penny пишет:>> 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 > Samba relies on the builtin version of Samba.It's good practice for shared libraries: $ apt-cache whatdepends libtalloc | grep '^ [a-z]' | wc -l 57 It is used for samba and samba-DC, sssd and openchange, cifs-utils and sogo-openchange-backend -- Andrey Cherepanov cas at altlinux.org
On 17:21:44 wrote Andrey Cherepanov:> I build new version of talloc-2.1.6 (build from external tarball) and > samba-4.3.6. > But if I provision domain by command > > samba-tool domain provision --realm=test.alt --domain test > --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc > --use-rfc2307 --use-xattrs=yes > > I got error: > Fixing provision GUIDs > ERROR(runtime): uncaught exception - pytalloc_reference_ex() called > for object type not based on talloc > File > "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py", line > 175, in _run > return self.run(*args, **kwargs) > File "/usr/lib64/python2.7/site-packages/samba/netcmd/domain.py", > line 442, in run > nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode) > File > "/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", > line 2172, in provision > skip_sysvolacl=skip_sysvolacl) > File > "/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", > line 1864, in provision_fill > attrs=['defaultObjectCategory']) > File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", line > 138, in check_database > error_count += self.check_object(object.dn, attrs=attrs) > File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", 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?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 way debian will do. But be carefull, use a clean new system to build, no samba related packages should be installed. And the ordering of building and installing is important, each package depends on the previous one. compile & install order: talloc tevent tdb ldb samba -- Regards Harry Jede
12.03.2016 19:31, Harry Jede пишет:> On 17:21:44 wrote Andrey Cherepanov: >> I build new version of talloc-2.1.6 (build from external tarball) and >> samba-4.3.6. >> But if I provision domain by command >> >> samba-tool domain provision --realm=test.alt --domain test >> --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc >> --use-rfc2307 --use-xattrs=yes >> >> I got error: >> Fixing provision GUIDs >> ERROR(runtime): uncaught exception - pytalloc_reference_ex() called >> for object type not based on talloc >> File >> "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py", line >> 175, in _run >> return self.run(*args, **kwargs) >> File "/usr/lib64/python2.7/site-packages/samba/netcmd/domain.py", >> line 442, in run >> nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode) >> File >> "/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", >> line 2172, in provision >> skip_sysvolacl=skip_sysvolacl) >> File >> "/usr/lib64/python2.7/site-packages/samba/provision/__init__.py", >> line 1864, in provision_fill >> attrs=['defaultObjectCategory']) >> File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", line >> 138, in check_database >> error_count += self.check_object(object.dn, attrs=attrs) >> File "/usr/lib64/python2.7/site-packages/samba/dbchecker.py", 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? > 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 way debian will do. But be carefull, > use a clean new system to build, no samba related packages should be > installed. And the ordering of building and installing is important, > each package depends on the previous one.I know. There was no problem to use samba-4.3.6 with talloc-2.1.5. Only with 2.1.6. I prepare to build samba-4.4.0rc4. It should work with new talloc without problem. -- Andrey Cherepanov cas at altlinux.org