Smbd startup failure caused by a failure to create an NT token for the guest account.

Bug #382136 reported by whale
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Fix Released
Undecided
Chuck Short
Karmic
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: samba

Hi
I've just intalled Ubuntu Server 8.04 LTS in order to run Samba/Ldap PDC but I,ve encountered an error which looks like a bug 3905 that was fixed in samba 3.0.23 according to changelog. I tried two different configuration both ends in the same moment with an error. first one is exact copy of solution from chapter 5 from "Samba3 by example". Second one based on SAMBA-LDAP Howto from smbldap-tools. Slapd is empty but working gives correct DSE responses. but when I lunch samba smbd crashes with this information in logs:

[2009/05/30 20:44:57, 10] lib/smbldap.c:smbldap_search_ext(1246)
  Failed search for base: ou=Groups,dc=dil,dc=edu, error: 32 (No such object) (unknown)
[2009/05/30 20:44:57, 10] auth/auth_util.c:add_aliases(656)
  pdb_enum_alias_memberships failed: NT_STATUS_UNSUCCESSFUL
[2009/05/30 20:44:57, 3] smbd/sec_ctx.c:pop_sec_ctx(356)
  pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2009/05/30 20:44:57, 10] auth/auth_util.c:make_new_server_info_guest(1508)
  create_local_token failed: NT_STATUS_NO_SUCH_USER
[2009/05/30 20:44:57, 0] smbd/server.c:main(1059)
  ERROR: failed to setup guest info.

if I run: smbd -d 10 -i

Primary group is 0 and contains 0 supplementary groups
smbldap_search_ext: base => [ou=Groups,dc=dil,dc=edu], filter => [(&(objectClass=sambaGroupMapping)(sambaSID=S-1-5-32-545))], scope => [2]
Failed search for base: ou=Groups,dc=dil,dc=edu, error: 32 (No such object) (unknown)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
LEGACY: mapping failed for sid S-1-5-32-545
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1
push_conn_ctx(0) : conn_ctx_stack_ndx = 0
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
NT user token: (NULL)
UNIX token of user 0
Primary group is 0 and contains 0 supplementary groups
smbldap_search_ext: base => [ou=Groups,dc=dil,dc=edu], filter => [(&(|(objectclass=sambaGroupMapping)(sambaGroupType=4))(|(sambaSIDList=S-1-5-21-1900305026-286758470-1266315604-501)(sambaSIDList=S-1-22-2-65534)(sambaSIDList=S-1-1-0)(sambaSIDList=S-1-5-2)(sambaSIDList=S-1-5-32-546)))], scope => [2]
Failed search for base: ou=Groups,dc=dil,dc=edu, error: 32 (No such object) (unknown)
pdb_enum_alias_memberships failed: NT_STATUS_UNSUCCESSFUL
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
create_local_token failed: NT_STATUS_NO_SUCH_USER
ERROR: failed to setup guest info.
talloc report on 'null_context' (total 4427 bytes in 228 blocks)
    auth_serversupplied_info contains 219 bytes in 3 blocks (ref 0) 0xa8dde0
    struct passwd * contains 117 bytes in 7 blocks (ref 0) 0xa8ebd0
    struct samu contains 582 bytes in 14 blocks (ref 0) 0xa8f8c0
    main loop talloc (mainly parse_misc) contains 573 bytes in 7 blocks (ref 0) 0xa8e100
    SORTED_TREE contains 915 bytes in 44 blocks (ref 0) 0xa8bb60
    struct pdb_methods contains 704 bytes in 5 blocks (ref 0) 0xa81a30
    lp_talloc contains 1317 bytes in 147 blocks (ref 0) 0x9da440

if I add
winbind nested groups = no

I can start smbd daemon but it is workaround not proper solution for server.
The same configuration on US 9.04 works without problems. Does anybody meet this error.

Revision history for this message
whale (wojtekgiel) wrote :
Revision history for this message
whale (wojtekgiel) wrote :
Revision history for this message
Chuck Short (zulcss) wrote :

This is actually fixed in karmic according to the upstream changelog. Marking fixed for karmic will look at getting a fix for hardy for this.

Regards
chuck

Changed in samba (Ubuntu Karmic):
status: New → Fix Released
Chuck Short (zulcss)
Changed in samba (Ubuntu Hardy):
assignee: nobody → Chuck Short (zulcss)
Revision history for this message
Chuck Short (zulcss) wrote :

This should be fixed in hardy as well.

Regards
chuck

Changed in samba (Ubuntu Hardy):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.