Something wrong with autobuild?

[Michael Adam]

Hi Richard,

I think it is not a real error but this:

* the databases are ususally opened without O_CREAT
  first. and only with CREAT when the first open fails.
  Now tdb2 seems to log the failure at a much lower
  debug level than tdb(1), which is why you see it in
  each make test run at least in the first open.
  The second open succeeds and you don't see a
  corresponding success log message.

* We also see here the fact that the tdb2 log messages
  generally lack a "\n" at the end.. ;)

* the account policy messages are also harmless. if I get
  it right, these record simply don't exist in the freshly
  created db. This is logged and default values are used
  instead.

Could this explain the phenomena or are you really seeing failures?

Cheers - Michael

Richard Sharpe wrote:
> Hi,
> 
> It seems that every tdbsam open is failing like this:
> 
> Version 4.0.0alpha19-DEVELOPERBUILD
> OPTIONS --configfile=$SMB_CONF_PATH
> --maximum-runtime=$SELFTEST_MAXTIME --target=samba4
> --basedir=$SELFTEST_TMPDIR --option=torture:progress=no
> --format=subunit
> WARNING: allowing empty subunit output from ldb.base
> WARNING: allowing empty subunit output from samba4.urgent_replication.python(dc)
> WARNING: allowing empty subunit output from samba4.blackbox.samba3dump
> tdbsam_open: Converting version 0.0 database to version 4.0.
> tdbsam_convert_backup: updated
> /memdisk/sharpe/a/b18058/samba4/bin/ab/s3dc/private/passdb.tdb file.
> tdb(/memdisk/sharpe/a/b18058/samba4/bin/ab/s3dc/lockdir/winbindd_idmap.tdb):IO
> Error: tdb_open: could not open file
> /memdisk/sharpe/a/b18058/samba4/bin/ab/s3dc/lockdir/winbindd_idmap.tdb:
> No such file or
> directorytdb(/memdisk/sharpe/a/b18058/samba4/bin/ab/s3dc/lockdir/account_policy.tdb):IO
> Error: tdb_open: could not open file
> /memdisk/sharpe/a/b18058/samba4/bin/ab/s3dc/lockdir/account_policy.tdb:
> No such file or directoryaccount_policy_get: tdb_fetch_uint32 failed
> for type 1 (min password length), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 2 (password
> history), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 3 (user must
> logon to change password), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 4 (maximum
> password age), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 5 (minimum
> password age), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 6 (lockout
> duration), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 7 (reset count
> minutes), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 8 (bad lockout
> attempt), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 9 (disconnect
> time), returning 0
> account_policy_get: tdb_fetch_uint32 failed for type 10 (refuse
> machine password change), returning 0
> 
> Is it something I did or an error on the build server?
> 
> -- 
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20120331/8dd9b889/attachment.pgp>