Christian Perrier wrote:
Quoting Dale Schroeder (d...@briannassaladdressing.com):
I gave up trying to fix the existing systems and downgraded to stable.
Today, I took a test machine and reinstalled the entire system.
There were no improvements.
Winbind would panic at a "getent group" command every time. getent
passwd, wbinfo -u,
and wbinfo -g do not appear to cause this anomaly.
Looking at the original bug report you sent (which we apparently
loosely noticed, sorry for this), I notice that we don't have much
details about your specific setup.
What kind of machine is the domain controller?
Could you post relevant parts of your smb.conf file (or, even better, the
output of "testparm")?
Maybe installing the samba-dbg package would help getting more
information in the panic trace, too (here, Steve Langasek would have
bette radvice than me, though).
The domain controller is a Windows 2000 Server.
samba-dbg is already installed, so I assume that's all the output I'm
going to get.
Output of testparm on test system:
[global]
workgroup = DOMAIN
realm = DOMAIN.COM
server string = %h server (Samba %v)
security = ADS
allow trusted domains = No
map to guest = Bad User
obey pam restrictions = Yes
password server = ad_pdc
username map = /etc/samba/users.map
log level = 1 winbind:3 idmap:3
log file = /var/log/samba/%m
max log size = 1000
name resolve order = wins hosts bcast
deadtime = 15
printcap name = cups
wins server = ###.###.###.###
ldap ssl = no
panic action = /usr/share/samba/panic-action %d
idmap backend = rid:DOMAIN=1000-20000000
idmap uid = 1000-20000000
idmap gid = 1000-20000000
template homedir = /home/domain/%U
template shell = /bin/bash
winbind cache time = 10
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = Yes
winbind offline logon = Yes
ea support = Yes
veto oplock files = /*.doc/*.xls/*.mdb/
map archive = No
map readonly = No
store dos attributes = Yes
One thing I failed to mention yesterday. Originally, when I ran the
upgrade on four systems,
two went into panic and two functioned as usual. The two that
originally were working
suddenly began to panic after last week's kernel upgrade
(2.6.30-8squeeze1). I don't
know if that provides a clue or not.
