segmentation fault in smbd

Bug #112539 reported by Istvan Szekeres
4
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: samba

when running smbclient:

rhye:~% smbclient '\\localhost\szekeres'
Password:
session setup failed: Call returned zero bytes (EOF)
rhye:~%

This is because smbd segfaults:

[2007/05/05 09:31:06, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2007/05/05 09:31:06, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 6966 (3.0.24)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/05/05 09:31:06, 0] lib/fault.c:fault_report(44)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/05/05 09:31:06, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2007/05/05 09:31:06, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 6966): internal error
[2007/05/05 09:31:06, 0] lib/util.c:log_stack_trace(1706)
  BACKTRACE: 22 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x22) [0x823dd92]
   #1 /usr/sbin/smbd(smb_panic+0x43) [0x823de73]
   #2 /usr/sbin/smbd [0x822c27a]
   #3 [0xffffe420]
   #4 /lib/tls/i686/cmov/libdl.so.2(dlopen+0x44) [0xb7d55b64]
   #5 /lib/libpam.so.0 [0xb7d7f487]
   #6 /lib/libpam.so.0 [0xb7d7f635]
   #7 /lib/libpam.so.0(_pam_init_handlers+0x1d1) [0xb7d80321]
   #8 /lib/libpam.so.0(pam_start+0x359) [0xb7d7e339]
   #9 /usr/sbin/smbd [0x8281b50]
   #10 /usr/sbin/smbd(smb_pam_accountcheck+0x6a) [0x8283e9a]
   #11 /usr/sbin/smbd [0x8276fc4]
   #12 /usr/sbin/smbd [0x8281503]
   #13 /usr/sbin/smbd [0x8132ce5]
   #14 /usr/sbin/smbd(ntlmssp_update+0x210) [0x8132570]
   #15 /usr/sbin/smbd(auth_ntlmssp_update+0x3b) [0x828124b]
   #16 /usr/sbin/smbd(reply_sesssetup_and_X+0x1905) [0x80ccd65]
   #17 /usr/sbin/smbd [0x80f6835]
   #18 /usr/sbin/smbd(smbd_process+0x701) [0x80f7a71]
   #19 /usr/sbin/smbd(main+0x10f3) [0x82da643]
   #20 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7c21ebc]
   #21 /usr/sbin/smbd [0x808c7f1]
[2007/05/05 09:31:06, 0] lib/util.c:smb_panic(1607)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 6966]
[2007/05/05 09:31:08, 0] lib/util.c:smb_panic(1615)
  smb_panic(): action returned status 0
[2007/05/05 09:31:08, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd

samba version:
ii samba 3.0.24-2ubuntu1 a LanManager-like file and printer server for Un

Revision history for this message
LMJ (linuxmasterjedi) wrote :

Same here on a fresh Ubuntu Feisty 64bits install on a new x86_64 Fujitsu server :-/

Revision history for this message
Mathias Gug (mathiaz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Do you still have the issue with the latest version of samba in feisty ?

Changed in samba:
status: New → Incomplete
Revision history for this message
John (cronos6) wrote :

Hello,

  No, I don't have anymore the problem ;) I think I had also a conf problem who generated this crash.

  Thanks for the help

Revision history for this message
Mathias Gug (mathiaz) wrote : Re: [Bug 112539] Re: segmentation fault in smbd

On Thu, Sep 20, 2007 at 05:02:13AM -0000, Johan wrote:
> Hello,
>
> No, I don't have anymore the problem ;) I think I had also a conf
> problem who generated this crash.
>

  status invalid

Changed in samba:
status: Incomplete → Invalid
Revision history for this message
Istvan Szekeres (szekeres) wrote :

Mathias: before setting a bug to invalid I would suggest to at least wait for some feedback from the original problem reporter (This time it was me). Even if the problem is solved for someone else It is not necessarily solved for the original reporter.

To answer your question: I do not have the problem anymore. Though I still do not know the reason, I still use the same samba package with the same configuration, so basically nothing has changed that would explain it.

Thanks for the help anyways.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.