Bug 5250 - Starting a AD Member Server before the DC causes winbind panic
Starting a AD Member Server before the DC causes winbind panic
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: winbind
3.0.26a
Other Linux
: P3 major
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-08 03:40 UTC by Jens Nissen
Modified: 2008-06-10 04:16 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 Jens Nissen 2008-02-08 03:40:30 UTC
Whenever I start my Samba AD Domain Member Server before I start the Domain controller, each request to connect to the Samba Server results in the following panic.
If I start SAMBA after starting the Windows 2000 DC, everything works fine.

Possibly related: Using wbinfo if the DC is absent locks down the complete SAMBA Server making it unavailable for any network service (including telnet and http).

[2008/02/08 10:18:45, 0] nsswitch/winbindd_cache.c:centry_string(295)
  centry corruption? needed 45 bytes, have 37
[2008/02/08 10:18:45, 0] lib/util.c:smb_panic(1632)
  PANIC (pid 7925): centry_string
[2008/02/08 10:18:45, 0] lib/util.c:log_stack_trace(1736)
  BACKTRACE: 1 stack frames:
   #0 /boot/usr/local/samba/sbin/winbindd(log_stack_trace+0x20) [0xcd1a8]
[2008/02/08 10:18:45, 0] lib/util.c:smb_panic(1637)
  smb_panic(): calling panic action [cp -p /var/log/smblog.ad /var/lib/adsamba/panic.log]
cp: /var/log/smblog.ad: No such file or directory
[2008/02/08 10:18:45, 0] lib/util.c:smb_panic(1645)
  smb_panic(): action returned status 1
[2008/02/08 10:18:45, 0] lib/fault.c:dump_core(181)
  dumping core in /var/log/cores/winbindd

My configuration roughly looks like this (skipped non-related stuff):
[global]
        dos charset = ISO-8859-1
        unix charset = ISO-8859-1
        display charset = ISO-8859-1
        interfaces = ixp0
        security = ADS
        passdb backend = tdbsam
        name resolve order = wins bcast host
        preferred master = No
        local master = No
        domain master = No
        wins server = 192.168.1.4
        idmap uid = 1000-60000
        idmap gid = 1000-60000
        winbind enum users = Yes
        winbind enum groups = Yes
        winbind offline logon = Yes
        ldapsam:trusted = Yes
        ea support = Yes
        allow trusted domains=Yes
Comment 1 Jens Nissen 2008-06-10 04:16:20 UTC
It looks as though the bug has gone in version 3.0.30
For me, this is fine (even though slightly unsatisfactory)