Bug 6612 - Signal 11 killing auth thread?
Signal 11 killing auth thread?
Status: RESOLVED FIXED
Product: Samba 3.2
Classification: Unclassified
Component: File services
3.2.13
x86 Linux
: P3 major
: ---
Assigned To: Volker Lendecke
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-05 15:02 UTC by Eric Ireland
Modified: 2009-08-06 08:52 UTC (History)
0 users

See Also:


Attachments
7zip'd core from the referenced log event (97.38 KB, application/octet-stream)
2009-08-05 15:10 UTC, Eric Ireland
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Ireland 2009-08-05 15:02:15 UTC
I have a samba install that all of the sudden has started getting signal 11.  I have done a memory test, and can find no issues.  I have trying reinstalling, different version, and as far as I can tell this issue started randomly.  Here is the relevent portion of the log of a crash event.

[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option TCP_NODELAY = 1
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option TCP_KEEPCNT = 9
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option TCP_KEEPIDLE = 7200
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option TCP_KEEPINTVL = 75
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option IPTOS_LOWDELAY = 0
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option IPTOS_THROUGHPUT = 0
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option SO_SNDBUF = 16384
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option SO_RCVBUF = 87380
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option SO_SNDLOWAT = 1
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option SO_RCVLOWAT = 1
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option SO_SNDTIMEO = 0
[2009/08/05 14:34:07,  5] lib/util_sock.c:print_socket_options(781)
  socket option SO_RCVTIMEO = 0
[2009/08/05 14:35:07, 10] lib/events.c:run_events(258)
  Running event "DNS registration handler" 8061f1a8
[2009/08/05 14:35:07, 10] lib/events.c:timed_event_destructor(65)
  Destroying timed event 8061f1a8 "DNS registration handler"
[2009/08/05 14:35:07,  6] smbd/dnsregister.c:dns_register_smbd(133)
  registering _smb._tcp service on port 445
[2009/08/05 14:35:10,  0] lib/fault.c:fault_report(40)
  ===============================================================
[2009/08/05 14:35:10,  0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 11 in pid 30901 (3.2.13)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2009/08/05 14:35:10,  0] lib/fault.c:fault_report(43)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2009/08/05 14:35:10,  0] lib/fault.c:fault_report(44)
  ===============================================================
  ===============================================================
[2009/08/05 14:35:10,  0] lib/util.c:smb_panic(1670)
  PANIC (pid 30901): internal error
[2009/08/05 14:35:10,  0] lib/util.c:log_stack_trace(1774)
  BACKTRACE: 10 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8027b141]
   #1 /usr/sbin/smbd(smb_panic+0x80) [0x8027b29e]
   #2 /usr/sbin/smbd [0x80265d93]
   #3 [0xb7f20420]
   #4 /usr/lib/libdns_sd.so.1(DNSServiceRegister+0x247) [0xb7c42b17]
   #5 /usr/sbin/smbd(dns_register_smbd+0x145) [0x800eb58b]
   #6 /usr/sbin/smbd [0x804bf2e1]
   #7 /usr/sbin/smbd(main+0xbaf) [0x804c0484]
   #8 /lib/libc.so.6(__libc_start_main+0xe5) [0xb7af4725]
   #9 /usr/sbin/smbd [0x80068541]
[2009/08/05 14:35:10,  0] lib/util.c:smb_panic(1675)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 30901]
sh: /usr/share/samba/panic-action: No such file or directory
[2009/08/05 14:35:10,  0] lib/util.c:smb_panic(1683)
  smb_panic(): action returned status 127
[2009/08/05 14:35:10,  0] lib/fault.c:dump_core(201)
  dumping core in /var/log/samba/cores/smbd
[2009/08/05 14:49:37,  0] smbd/server.c:main(1210)
  smbd version 3.2.13 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/08/05 14:49:37,  5] lib/debug.c:debug_dump_status(407)
  INFO: Current debug levels:
    all: True/10
    tdb: False/0
    printdrivers: False/0
    lanman: False/0
    smb: False/0
    rpc_parse: False/0
    rpc_srv: False/0
    rpc_cli: False/0
    passdb: False/0
    sam: False/0
    auth: False/0
    winbind: False/0
    vfs: False/0
    idmap: False/0
 quota: False/0
    acls: False/0
    locking: False/0
    msdfs: False/0
    dmapi: False/0
    registry: False/0
  doing parameter max log size = 1000
  doing parameter syslog = 0
  doing parameter panic action = /usr/share/samba/panic-action %d
  doing parameter encrypt passwords = true
  doing parameter passdb backend = tdbsam
  doing parameter obey pam restrictions = yes
  doing parameter invalid users = root
  doing parameter passwd program = /usr/bin/passwd %u
  doing parameter passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *passwd:*password\supdated\ssuccessfully* .
  doing parameter socket options = TCP_NODELAY
  doing parameter wins support = no
[2009/08/05 14:49:37,  4] param/loadparm.c:lp_load_ex(8797)

I do have a core file available as well, but I see no place to attach it.

Thanks for your time
Comment 1 Eric Ireland 2009-08-05 15:10:14 UTC
Created attachment 4518 [details]
7zip'd core from the referenced log event
Comment 2 Volker Lendecke 2009-08-05 16:15:01 UTC
Please recompile Samba with --enable-dnssd=no. Please use the native avahi support for the same features.

Thanks,

Volker
Comment 3 Eric Ireland 2009-08-06 08:48:05 UTC
This has worked.  Im going to submit a patch to my distro (gentoo) to fix this problem.  Do you plan on supporting external avahi libraries in the future?  How I fix the build script depends on that answer.

Once again I want to thank for your time and support!
Comment 4 Volker Lendecke 2009-08-06 08:52:23 UTC
We already do with 3.3, using the native avahi interface. Even the avahi website itself recommends to not use the old Apple-compatible interface anymore. I left the legacy stuff in for someone from Apple to pick it up and fix it. But so far nobody has volunteered, so Mac OS/X seems not so important anymore these days.

Volker