samba - Mar 2005 - Problem changing password - Samba 3.0.13

First thank you to the team for the Samba software. I have been using 
this on a number of sites with excellent results and very few 
problems over the years.

I have just upgraded two sites to Samba 3.0.13 from 3.0.11. Both 
sites are small and use smbpasswd as the password db backend. Since 
the upgrade I am unable to change a users password (as root) using 
smbpasswd. 

There are two reported errors  

account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum 
password age (seconds since 1970)), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum 
password age (seconds since 1970)), returning 0

The systems are both RedHat 9.0, Samba was installed using RPMS from 
samba.org 

Converting the smbpasswd file to a tdbsam and then reconfiguring 
Samba to use passdb.tdb makes no difference.

Using pdbedit to import the old smbpasswd and export as a new 
smbpasswd file makes no difference - so I do not think that this is a 
problem of an old format smbpasswd file - although that was my first 
thought.

Reverting to samba 3.0.11 fixes the problem.

Has anyone any suggestions please?

Thank you

Richard Smart

Hello Richard,

Richard Smart wrote:
> I have just upgraded two sites to Samba 3.0.13 from 3.0.11. Both
> sites are small and use smbpasswd as the password db backend. Since
> the upgrade I am unable to change a users password (as root) using
> smbpasswd.
> 
> There are two reported errors
> 
> account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum
> password age (seconds since 1970)), returning 0
> account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum
> password age (seconds since 1970)), returning 0
the ldap schema changed between samba 3.0.11 an d 3.0.12.
> The systems are both RedHat 9.0, Samba was installed using RPMS from
> samba.org
> 
> Converting the smbpasswd file to a tdbsam and then reconfiguring
> Samba to use passdb.tdb makes no difference.
I don't know as other admins fix this, updating the schema was not
sufficient to me and that I did was recreate the account_policy.tdb
file.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/IT d- s+:+() a31 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w---
O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++
G++ e- h+(++) !r !z
------END GEEK CODE BLOCK------