Bug 9623 - Unable to provision a *NEW* domain.
Summary: Unable to provision a *NEW* domain.
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Other (show other bugs)
Version: 4.0.2
Hardware: x86 Linux
: P5 critical (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
Depends on:
Reported: 2013-01-31 21:03 UTC by charles.heselton
Modified: 2024-01-11 11:59 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description charles.heselton 2013-01-31 21:03:33 UTC
When trying to provision a *NEW* domain....

Realm: charlesheselton.com
 Domain [charlesheselton]:
 Server Role (dc, member, standalone) [dc]:
 DNS forwarder IP address (write 'none' to disable forwarding) []:
Administrator password:
Retype password:
Looking up IPv4 addresses
Looking up IPv6 addresses
No IPv6 address will be assigned
Setting up share.ldb
Setting up secrets.ldb
Setting up the registry
Setting up the privileges database
Setting up idmap db
Setting up SAM db
Setting up sam.ldb partitions and settings
Setting up sam.ldb rootDSE
Pre-loading the Samba 4 and AD schema
Adding DomainDN: DC=charlesheselton,DC=com
Adding configuration container
Setting up sam.ldb schema
Setting up sam.ldb configuration data
Setting up display specifiers
Adding users container
Modifying users container
Adding computers container
Modifying computers container
Setting up sam.ldb data
Setting up well known security principals
Setting up sam.ldb users and groups

Setting up self join
set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER.
Segmentation fault

This is on a 4.0.2 tarball, that was updated from git.
Comment 1 Björn Jacke 2024-01-11 11:59:12 UTC
Looks like a problem of that specific setup, please file a new report if this is still a problem for you with latest versions and more details about the setup