I have just compiled Samba 2.2.4 with the following configure. ./configure --with-pam --with-winbind I used the same instructions as I did go get Samba 2.2.2 working. I noticed the winbind daemon dies after about a minute. I set the debug to 10 for it and I found some confusing things. Why is it trying to connect to GIGDC1 with a null username? Is this why the connection is refused? <--snip--> [2002/05/10 08:04:13, 5] nsswitch/winbindd_cm.c:cm_open_connection(346) connecting to GIGDC1 from PRINT02P with username []\[] [2002/05/10 08:04:13, 3] libsmb/cliconnect.c:cli_full_connection(980) Connecting to host=GIGDC1 share=IPC$ [2002/05/10 08:04:13, 3] lib/util_sock.c:open_socket_out(843) Connecting to XXX.XXX.4.3 at port 445 [2002/05/10 08:04:13, 2] lib/util_sock.c:open_socket_out(872) error connecting to XXX.XXX.4.3:445 (Connection refused) <--snip--> ............. <--snip--> [2002/05/10 08:04:35, 10] nsswitch/winbindd_group.c:winbindd_getgrent(550) got gid 10000 for group f42 [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(38) ==============================================================[2002/05/10 08:04:35, 0] lib/fault.c:fault_report(39) INTERNAL ERROR: Signal 11 in pid 26422 (2.2.4) Please read the file BUGS.txt in the distribution [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(41) ==============================================================[2002/05/10 08:04:35, 0] lib/util.c:smb_panic(1092) PANIC: internal error <End of File> Any help is appreciated!! Josh Konkol, CNE MCSE Senior Network Analyst GuideOne Insurance Mail Stop AB-1 515-267-2427 jkonkol@guidemail.com .~. /V\ /( )\ ^^-^^
Tim, Sorry for the multiple messages but I think I have got the back trace you requested. I cleared the logs, restared the smb daemons, and ran gdb winbindd <winbindprocid> . After the program started I hit 'c' to continue. To cause the fault all I have to do is goto Start-Run and type \\print02p (print02p is the instance name). At that point I started seeing output from gdb. Below is the output. print02p:/samba # ps -ae | grep winbind 24598 ? 00:00:00 winbindd print02p:/samba # gdb winbind 24598 GNU gdb 5.0 <--snip licensing info--> /usr/local/samba/24598: No such file or directory. Attaching to Pid 24598 0x400f2e8a in ?? () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x400ac8d6 in ?? () (gdb) c Continuing. Program received signal SIGABRT, Aborted. 0x4006cd4e in ?? () (gdb) c Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. Josh Konkol, CNE MCSE Senior Network Analyst GuideOne Insurance Mail Stop AB-1 515-267-2427 jkonkol@guidemail.com .~. /V\ /( )\ ^^-^^ -----Original Message----- From: Konkol, Josh Sent: Monday, May 13, 2002 7:58 AM To: 'Tim Potter' Subject: RE: [Samba] Samba 2.2.4 on s/390 Tim, Thanks for the reply. I have re-compiled Samba as you requested using: ./configure.developer --with-pam --with-winbind . I then did make && make install. I'm still getting the error in log.winbindd. Excuse my newbieness but I don't know how to get a stack backtrace. If you give me instructions I will get it for you. Thanks again, Josh Konkol, CNE MCSE Senior Network Analyst GuideOne Insurance Mail Stop AB-1 515-267-2427 jkonkol@guidemail.com .~. /V\ /( )\ ^^-^^ -----Original Message----- From: Tim Potter [mailto:tpot@samba.org] Sent: Sunday, May 12, 2002 7:29 PM To: Konkol, Josh Subject: Re: [Samba] Samba 2.2.4 on s/390 On Fri, May 10, 2002 at 08:19:09AM -0500, Konkol, Josh wrote:> I have just compiled Samba 2.2.4 with the following configure. > > ./configure --with-pam --with-winbind> [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(38) > ==============================================================> [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(39) > INTERNAL ERROR: Signal 11 in pid 26422 (2.2.4) > Please read the file BUGS.txt in the distribution > [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(41) > ==============================================================> [2002/05/10 08:04:35, 0] lib/util.c:smb_panic(1092) > PANIC: internal error > <End of File>Hello. Any chance of getting a stack backtrace from this? If you compile winbindd with -g also that would be good. If you do a make clean then ./configure.developer <other config args> it will build winbindd and others with -g. Tim.
OK, I think I got it right this time. print02p:/samba/var # ps -ae | grep winbind 26482 ? 00:00:00 winbindd print02p:/samba/var # gdb winbind 26482 This GDB was configured as "s390-suse-linux"...winbind: No such file or directory. /usr/local/samba/var/26482: No such file or directory. Attaching to Pid 26482 0x400f2e8a in ?? () (gdb) backtrace #0 0x400f2e8a in ?? () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x400ac8d6 in ?? () (gdb) backtrace #0 0x400ac8d6 in ?? () #1 0x4008d868 in ?? () (gdb) c Continuing. Program received signal SIGABRT, Aborted. 0x4006cd4e in ?? () (gdb) backtrace #0 0x4006cd4e in ?? () (gdb) c Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. Please let me know if you need anything else. Thanks sooo much for your help. Josh -----Original Message----- From: Tim Potter [mailto:tpot@samba.org] Sent: Monday, May 13, 2002 6:07 PM To: Samba Subject: Re: [Samba] Samba 2.2.4 on s/390 On Mon, May 13, 2002 at 08:24:21AM -0500, Samba wrote:> Sorry for the multiple messages but I think I have got the back trace you > requested. I cleared the logs, restared the smb daemons, and ran gdb > winbindd <winbindprocid> . After the program started I hit 'c' tocontinue.> To cause the fault all I have to do is goto Start-Run and type \\print02p > (print02p is the instance name). At that point I started seeing outputfrom> gdb. Below is the output. > > print02p:/samba # ps -ae | grep winbind > 24598 ? 00:00:00 winbindd > print02p:/samba # gdb winbind 24598 > GNU gdb 5.0 > <--snip licensing info--> > /usr/local/samba/24598: No such file or directory. > Attaching to Pid 24598 > 0x400f2e8a in ?? () > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x400ac8d6 in ?? () > (gdb) c > Continuing. > > Program received signal SIGABRT, Aborted. > 0x4006cd4e in ?? () > (gdb) c > Continuing. > > Program terminated with signal SIGABRT, Aborted. > The program no longer exists.Ah OK you're nearly there! Just type 'backtrace' into gdb and send me the output. This should contain the stack frames where winbindd crashed and is usually extremely helpful in tracking down these things. Tim.
Tim, Have you had time to look at this? Josh Konkol, CNE MCSE Senior Network Analyst GuideOne Insurance Mail Stop AB-1 515-267-2427 jkonkol@guidemail.com .~. /V\ /( )\ ^^-^^ -----Original Message----- From: Konkol, Josh [mailto:JKonkol@guidemail.com] Sent: Tuesday, May 14, 2002 6:59 AM To: 'Tim Potter' Cc: Samba (E-mail) Subject: RE: [Samba] Samba 2.2.4 on s/390 OK, I think I got it right this time. print02p:/samba/var # ps -ae | grep winbind 26482 ? 00:00:00 winbindd print02p:/samba/var # gdb winbind 26482 This GDB was configured as "s390-suse-linux"...winbind: No such file or directory. /usr/local/samba/var/26482: No such file or directory. Attaching to Pid 26482 0x400f2e8a in ?? () (gdb) backtrace #0 0x400f2e8a in ?? () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x400ac8d6 in ?? () (gdb) backtrace #0 0x400ac8d6 in ?? () #1 0x4008d868 in ?? () (gdb) c Continuing. Program received signal SIGABRT, Aborted. 0x4006cd4e in ?? () (gdb) backtrace #0 0x4006cd4e in ?? () (gdb) c Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. Please let me know if you need anything else. Thanks sooo much for your help. Josh -----Original Message----- From: Tim Potter [mailto:tpot@samba.org] Sent: Monday, May 13, 2002 6:07 PM To: Samba Subject: Re: [Samba] Samba 2.2.4 on s/390 On Mon, May 13, 2002 at 08:24:21AM -0500, Samba wrote:> Sorry for the multiple messages but I think I have got the back trace you > requested. I cleared the logs, restared the smb daemons, and ran gdb > winbindd <winbindprocid> . After the program started I hit 'c' tocontinue.> To cause the fault all I have to do is goto Start-Run and type \\print02p > (print02p is the instance name). At that point I started seeing outputfrom> gdb. Below is the output. > > print02p:/samba # ps -ae | grep winbind > 24598 ? 00:00:00 winbindd > print02p:/samba # gdb winbind 24598 > GNU gdb 5.0 > <--snip licensing info--> > /usr/local/samba/24598: No such file or directory. > Attaching to Pid 24598 > 0x400f2e8a in ?? () > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x400ac8d6 in ?? () > (gdb) c > Continuing. > > Program received signal SIGABRT, Aborted. > 0x4006cd4e in ?? () > (gdb) c > Continuing. > > Program terminated with signal SIGABRT, Aborted. > The program no longer exists.Ah OK you're nearly there! Just type 'backtrace' into gdb and send me the output. This should contain the stack frames where winbindd crashed and is usually extremely helpful in tracking down these things. Tim. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba