Bug 4969 - samba 4 (alpha1 and svn version)
Summary: samba 4 (alpha1 and svn version)
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: x86 Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Andrew Bartlett
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-12 13:25 UTC by wolfgang_schleicher
Modified: 2007-09-13 02:08 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wolfgang_schleicher 2007-09-12 13:25:05 UTC
Trying to install current samba4 svn version on a fedora core (6) system (2xXeon 2.4 ghz, 2gb ram).

Followed the included howto:

svn co svn://svnanon.samba.org/samba/branches/SAMBA_4_0 samba4
cd /usr/src/samba4/source
./autogen.sh
./configure --prefix=/usr/local/samba --enable-developer --enable-automatic-dependencies
make pch all
make install

Included /usr/local/samba/bin into the PATH

cd /usr/src/samba4/source
./setup/provision --domain=demo --realm=demo.local --adminpass=demo

I got the following error:

ERROR: Could not determine network interfaces, you must use a interfaces conf line
WARNING: no network interfaces found
set DOMAIN SID: S-1-5-21-3479567878-3861543463-2998501656
smbscript: ejsEvalScript(): Assertion failure

Backtrace: [ 0] provision_fix_subobj:9 -> assert(valid_netbios_name(sub.NETBIOSNAME))
[ 1]:133 -> provision_fix_subobj(subobj, paths)

When compiling the official released tar file (alpha1) there´s no error about "problems determing network interface" but the error concerning "valid_netbios_name" still remains.

I tried serveral different fc6 kernel environments (xen, non-xen) (kernel-xen-2.6.20.x, kernel-2.6.18.x, kernel-2.6.22.x)

Googled around but found no similiar reported problems.

Any help is appreceated.
Kinds regards
Wolfgang
Comment 1 wolfgang_schleicher 2007-09-13 02:08:55 UTC
Sorry for wrong reporting. Does not seem to be a bug! Used the additional provision option "--host-name=XYZ" and it seems to work.