Bug 5146 - segfault adding winXP machine to Samba 3.0.28 domain
Summary: segfault adding winXP machine to Samba 3.0.28 domain
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Domain Control (show other bugs)
Version: 3.0.28
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-15 10:27 UTC by Tom Burkholder
Modified: 2022-01-05 16:55 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Burkholder 2007-12-15 10:27:43 UTC 
I was unable to join a WinXP sp2 client to my samba-hosted domain using samba 3.0.28 (bugzilla doesn't have a 3.0.28 version tag yet) and got the following level 1 log.  I have a log level 3 trace as well.  I reverted to 3.0.26a and joined without problem.

The samba host is a rather old gentoo linux (release 1.4.1.2) running kernel 2.4.25 and glibc 2.3.6  (gentoo's ebuild 2.3.6-r4)  Built with gcc 4.1.1

This seems similar to bug 4727.


[2007/12/15 09:16:40, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2007/12/15 09:16:40, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 22440 (3.0.28)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/12/15 09:16:40, 0] lib/fault.c:fault_report(44)
  
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/12/15 09:16:40, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2007/12/15 09:16:40, 0] lib/util.c:smb_panic(1633)
  PANIC (pid 22440): internal error
[2007/12/15 09:16:40, 0] lib/util.c:log_stack_trace(1737)
  BACKTRACE: 29 stack frames:
   #0 /opt/samba/bin/smbd(log_stack_trace+0x2d) [0x8021c5d9]
   #1 /opt/samba/bin/smbd(smb_panic+0x74) [0x8021c701]
   #2 /opt/samba/bin/smbd [0x80208bf9]
   #3 /lib/libpthread.so.0 [0x40273765]
   #4 /lib/libc.so.6 [0x40350148]
   #5 /opt/samba/bin/smbd(winbindd_send_request+0x66) [0x8022bdfd]
   #6 /lib/libnss_winbind.so.2(winbindd_request+0x26) [0x4066ec28]
   #7 /lib/libnss_winbind.so.2(_nss_winbind_getpwnam_r+0x9e) [0x4066f5ec]
   #8 /lib/libc.so.6(getpwnam_r+0xad) [0x403acbbd]
   #9 /lib/libc.so.6(getpwnam+0x6c) [0x403ac6dc]
   #10 /opt/samba/bin/smbd(sys_getpwnam+0x1d) [0x8020b437]
   #11 /opt/samba/bin/smbd(getpwnam_alloc+0xcc) [0x8020e5fa]
   #12 /opt/samba/bin/smbd(Get_Pwnam_alloc+0x201) [0x8020e11f]
   #13 /opt/samba/bin/smbd [0x801d4e89]
   #14 /opt/samba/bin/smbd(pdb_create_user+0x38) [0x801d534e]
   #15 /opt/samba/bin/smbd(_samr_create_user+0x2f2) [0x8015bcef]
   #16 /opt/samba/bin/smbd [0x80151b93]
   #17 /opt/samba/bin/smbd(api_rpcTNP+0x292) [0x8016cdcb]
   #18 /opt/samba/bin/smbd(api_pipe_request+0x1f6) [0x8016d2cd]
   #19 /opt/samba/bin/smbd [0x80166d76]
   #20 /opt/samba/bin/smbd(write_to_pipe+0x12d) [0x801653f0]
   #21 /opt/samba/bin/smbd [0x800644cb]
   #22 /opt/samba/bin/smbd [0x80064bcc]
   #23 /opt/samba/bin/smbd(reply_trans+0x6d6) [0x800657d1]
   #24 /opt/samba/bin/smbd [0x800bc400]
   #25 /opt/samba/bin/smbd(smbd_process+0x8c1) [0x800bd69a]
   #26 /opt/samba/bin/smbd(main+0xb97) [0x802e5f54]
   #27 /lib/libc.so.6(__libc_start_main+0xa6) [0x4033d3d6]
   #28 /opt/samba/bin/smbd [0x80049191]
[2007/12/15 09:16:40, 0] lib/fault.c:dump_core(181)
  dumping core in /opt/samba/var/cores/smbd
[2007/12/15 09:16:40, 1] smbd/ipc.c:api_fd_reply(290)
  api_fd_reply: INVALID PIPE HANDLE: 7660
Comment 1 Björn Jacke 2022-01-05 16:55:47 UTC 
sorry for the late response, whatever the problem was, it was probaby fixed in the meantime, this is not a known issue in the last years.