Bug 3723 - Fails with panic when inadvertently started in "security=user" mode
Summary: Fails with panic when inadvertently started in "security=user" mode
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: winbind (show other bugs)
Version: 3.0.22
Hardware: Other Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL: http://bugs.debian.org/337070
Depends on:
Reported: 2006-04-25 16:20 UTC by Christian Perrier (dead mail address)
Modified: 2006-04-25 16:36 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Christian Perrier (dead mail address) 2006-04-25 16:20:02 UTC
The same goes actually when winbind in started with "security=domain" but the domain hasn't been joined.

In such cases, winbind panics with stuff like the following:

  PANIC: Could not fetch our SID - did we join?

[2006/04/25 23:11:31, 0] lib/util.c:smb_panic2(1562)
  BACKTRACE: 6 stack frames:
   #0 /usr/sbin/winbindd(smb_panic2+0x7c) [0x80e711c]
   #1 /usr/sbin/winbindd(smb_panic+0x1a) [0x80e733a]
   #2 /usr/sbin/winbindd(init_domain_list+0x13c) [0x807b81c]
   #3 /usr/sbin/winbindd(main+0x4b2) [0x8074a22]
   #4 /lib/libc.so.6(__libc_start_main+0x9e) [0x4019f3be]
   #5 /usr/sbin/winbindd [0x80731f1]

This is actually Debian bug #337070. Reproduced from 3.0.14a to 3.0.22
Comment 1 Gerald (Jerry) Carter (dead mail address) 2006-04-25 16:36:45 UTC
Already fixed in 3.0.23pre1.