hello, i deleted the passdb backend line and have no more panics. it seems like it solved the problem with the help of your analysis, thank you.
an advice for debian users : start with an empty smb.conf, do not use the proposed smb.conf, especially if u want to setup a member server with winbind. the one proposed is for tdbsam setup. regards "�ric le h�naff" <[EMAIL PROTECTED]> a �crit dans le message de news:[EMAIL PROTECTED] > I'm wondering if i really need a tdbsam ? i'm using winbindd and the users > and groups base is on a windows NT4 PDC. > may be i should delete those three lines from smb.con : > passdb backend = tdbsam, guest > passwd program = /usr/bin/passwd %u > passwd chat = *Enter\snew\sUNIX\spassword:* %n\n > *Retype\snew\sUNIX\spassword:* %n\n . > see smb.conf below. > > > --------------- > # Global parameters > [global] > workgroup = DOM_BIBLIO > server string = Serveur %h (Samba %v) > security = DOMAIN > passdb backend = tdbsam, guest > passwd program = /usr/bin/passwd %u > passwd chat = *Enter\snew\sUNIX\spassword:* %n\n > *Retype\snew\sUNIX\spassword:* %n\n . > syslog = 0 > log file = /var/log/samba/log.%m > max log size = 1000 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > dns proxy = No > panic action = /usr/share/samba/panic-action %d > idmap uid = 10000-20000 > idmap gid = 10000-20000 > winbind separator = + > invalid users = root > > [users] > path = /share/users > read only = No > create mask = 0770 > force create mode = 0770 > directory mask = 0770 > force directory mode = 0770 > > [groupes] > path = /share/groupes > read only = No > create mask = 0770 > force create mode = 0770 > directory mask = 0770 > force directory mode = 0770 > ------------ > > "Jeremy Allison" <[EMAIL PROTECTED]> a �crit dans le message de > news:[EMAIL PROTECTED] > On Thu, Sep 09, 2004 at 11:46:45AM +0200, ?ric le h?naff wrote: > > hello, > > server : debian sarge on a dell pe 1750 . Secondary file server holding > > homes and groups shares documents. the pdc is a windows nt 4. > > clients are NT4, w2k some xp. about 100 clients. > > > > i want to upgrade smbd from 3.0.2a to 3.0.6 but keep winbindd at 3.02a > > because of a bug in winbindd 3.0.6. > > Do you think it's possible ? > > > > i have a lot of panic actions when users access to mail client eudora's > > files. see log below. > > what does mean "call_nt_transact_ioctl(0x90028): Currently not > > implemented.". it creates a panic. > > No, this is not causing the panic - what is causing the > panic looks like a corrupted tdb sam database. > > The following gives it away : > > > #0 /usr/sbin/smbd(smb_panic+0x101) [0x81c1d11] > > #1 /usr/sbin/smbd [0x81aff28] > > #2 /lib/libc.so.6 [0x401ed4a8] > > #3 /usr/sbin/smbd(init_sam_from_buffer+0x61c) [0x819379c] > > #4 /usr/sbin/smbd [0x81a4941] > > #5 /usr/sbin/smbd [0x81a4e10] > > #6 /usr/sbin/smbd [0x81a4f60] > > #7 /usr/sbin/smbd [0x8194ad5] > > #8 /usr/sbin/smbd(pdb_getsampwsid+0x35) [0x81960d5] > > #9 /usr/sbin/smbd(make_server_info_guest+0x89) [0x81fbfb9] > > #10 /usr/sbin/smbd [0x81f9d82] > > #11 /usr/sbin/smbd [0x81f4e3f] > > #12 /usr/sbin/smbd [0x80a80fe] > > #13 /usr/sbin/smbd(reply_sesssetup_and_X+0x758) [0x80a9bd8] > > #14 /usr/sbin/smbd [0x80c809a] > > #15 /usr/sbin/smbd [0x80c8300] > > #16 /usr/sbin/smbd(process_smb+0x8c) [0x80c850c] > > #17 /usr/sbin/smbd(smbd_process+0x168) [0x80c9188] > > #18 /usr/sbin/smbd(main+0x4bc) [0x822cb8c] > > The init_sam_from_buffer is the key. Can you get a > proper stack backtrace with symbols - or try to > restore your 3.0.2 tdbsam and re-install 3.0.6. > The first start of 3.0.6 should upgrade your tdbsam > database correctly. > > Jeremy. > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
