[2005/09/16 12:08:37, 0] lib/fault.c:fault_report(36) =============================================================== [2005/09/16 12:08:37, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 13026 (3.0.20-UL) Please read the appendix Bugs of the Samba HOWTO collection [2005/09/16 12:08:37, 0] lib/fault.c:fault_report(39) =============================================================== [2005/09/16 12:08:37, 0] lib/util.c:smb_panic2(1548) PANIC: internal error [2005/09/16 12:08:37, 0] lib/util.c:smb_panic2(1556) BACKTRACE: 12 stack frames: #0 /usr/sbin/winbindd(smb_panic2+0x1b6) [0x80e2f2e] #1 /usr/sbin/winbindd(smb_panic+0x19) [0x80e2d74] #2 /usr/sbin/winbindd [0x80d001d] #3 /usr/sbin/winbindd [0x80d0092] #4 /lib/libc.so.6 [0x401c7e48] #5 /usr/sbin/winbindd [0x809b05a] #6 /usr/sbin/winbindd [0x809a8a9] #7 /usr/sbin/winbindd(winbind_child_died+0xbb) [0x809adec] #8 /usr/sbin/winbindd(vfprintf+0x3487) [0x8080ee3] #9 /usr/sbin/winbindd(main+0x577) [0x8081485] #10 /lib/libc.so.6(__libc_start_main+0xa2) [0x401b6522] #11 /usr/sbin/winbindd(ldap_msgfree+0x95) [0x807f8b1]
Could you please recompile Samba with debugging symbols. Instead of ./configure you might use ./configure.developer. And please upload all winbind log files. If it's possible for you, running the -g compiled winbind under valgrind will probably provide much more detailed information on what has failed. You get valgrind from www.valgrind.org. Please run it with the following options: valgrind --tool=memcheck --leak-check=yes -v --num-callers=20 \ --trace-children=yes --log-file=/tmp/smbd.vg winbindd -d 10 -i and upload the resulting file. Thanks, Volker
Created attachment 1449 [details] winbindd Log-File as requested (run with valgrind )
Created attachment 1450 [details] winbindd Log-File as requested ( after using the re-compiled winbindd )
Is it possible that you did not run winbind as root? Volker
Yes, I did run it as root. Fabian (In reply to comment #4) > Is it possible that you did not run winbind as root? > Volker
The error message in the logfile poses a question: Could not fetch our SID - did we join? What is your configuration? Could you attach your smb.conf? Did you join the domain you are member of? Or are you a domain controller? Volker
Here is the smb.conf: I've added the two idmap lines in global. Since then the requests are handled very quickly. Regards, Fabian # Samba config file created using SWAT # from 19.171.98.59 (19.171.98.59) # Date: 2005/09/19 09:36:26 [global] workgroup = EU1.FORD.COM realm = EU1.FORD.COM server string = MTC/DTC Safety-Lab Server - Samba 3.0.20-UL interfaces = 19.171.244.50 security = SERVER password server = mereu101 mereu103 log file = /var/log/samba/%m.log name resolve order = wins lmhosts host bcast preferred master = No local master = No domain master = No dns proxy = No wins server = 19.150.112.37 ldap ssl = no idmap uid = 90000-100000 idmap gid = 90000-100000 printing = lprng print command = lpr -r -P'%p' %s lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j lppause command = lpc hold '%p' %j lpresume command = lpc release '%p' %j queuepause command = lpc stop '%p' queueresume command = lpc start '%p' [safety] comment = MTC Safety-Lab Data path = /crash_vol read only = No create mask = 0664 directory mask = 0775 browseable = No [sdl-web] comment = SDL T-Drive path = /ford/thishost/webapps/sdl-web write list = gcory1, jkellehe, irahim, jweeden, pknibb, mryan4, jhead8, fzurheid read only = No create mask = 0664 directory mask = 0775 [isoverter] comment = Iso-Verter Table Files path = /crash_vol/isoverter read only = No create mask = 0664 directory mask = 0775 [homes] read only = No browseable = No [dec-safety] comment = Safety Dynamics Lab Data - Dunton Technical Centre path = /crash_vol/DEC-Safety-Lab write list = gcory1, jkellehe, irahim, jweeden, pknibb, mryan4, jhead8, fzurheid create mask = 0664 directory mask = 0775 browseable = No [messring] comment = Messring File Share path = /crash_vol/messring read only = No create mask = 0664 directory mask = 0775 [KT] comment = Kayser-Threde File Share path = /crash_vol/KT read only = No create mask = 0664 directory mask = 0775 [slcal] comment = Calibration Lab path = /crash_vol/slcaldaten write list = ddevoge1 read only = No create mask = 0664 directory mask = 0775 [Software] comment = Software Directory path = /crash_vol/software read only = No [localbin] comment = Local Bin Directory path = /usr/local/bin read list = fzurheid write list = fzurheid create mask = 0755 directory mask = 0775 browseable = No [volvo] comment = Volvo Safety Test Data path = /crash_vol/volvo_data read only = No create mask = 0664 directory mask = 0775 [cal-lab] comment = Merkenich Calibration-Lab Data path = /crash_vol/Cal-Lab read only = No create mask = 0664 directory mask = 0775 [webapps] comment = WebApps on MKCRS01 path = /ford/thishost/webapps write list = fzurheid create mask = 0664 directory mask = 0775 [dec-safety-dev] comment = Dunton Safety-Lab Web Development path = /usr/local/WebSphere/AppServer/installedApps/mkcrs01/Safetylab-devEAR.ear/SafetylabWeb-dev.war write list = fzurheid create mask = 0664 directory mask = 0775 [a2mac1] comment = A2MAC1-Application on MKCRS01 path = /ford/thishost/webapps/a2mac1 write list = fzurheid, uviersba, fschamb1 create mask = 0664 directory mask = 0775 [emission] comment = MTC - Emission-Lab Data path = /emission read only = No create mask = 0664 directory mask = 0775 [e-lab] comment = MTC - E-Lab Data path = /e-lab read only = No create mask = 0664 directory mask = 0775 browseable = No [ewt] comment = MTC - Climatic Wind Tunnels path = /ewt read only = No create mask = 0664 directory mask = 0775 ############################################################################# (In reply to comment #6) > The error message in the logfile poses a question: > > Could not fetch our SID - did we join? > > What is your configuration? Could you attach your smb.conf? Did you join the > domain you are member of? Or are you a domain controller? > > Volker
security = server is not a domain member server configuration. Please re-read the docs. Thanks.