Skip site navigation (1)Skip section navigation (2) 
Date:      Sat, 07 Jan 2017 18:53:48 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 215859] net/samba36: upgrade of talloc/tevent/tdb to talloc-2.1.8 tevent-0.9.31 tdb-1.3.12,1 breaks samba36-3.6.25_3
Message-ID:  <bug-215859-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215859

            Bug ID: 215859
           Summary: net/samba36: upgrade of talloc/tevent/tdb to
                    talloc-2.1.8 tevent-0.9.31 tdb-1.3.12,1 breaks
                    samba36-3.6.25_3
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: timur@FreeBSD.org
          Reporter: la5lbtyi@aon.at
             Flags: maintainer-feedback?(timur@FreeBSD.org)
          Assignee: timur@FreeBSD.org

The recent upgrade of (probably one of) talloc/tevent/tdb breaks samba,
specifically smbd.

I tried rebuilding samba36, to no avail.

The interesting part may be "Bad talloc magic value - unknown value" in the
second log below.

log.smbd shows the following:

[2017/01/07 18:16:30,  0] smbd/server.c:1072(main)
  smbd version 3.6.25 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2011
[2017/01/07 18:16:30.895072,  0] lib/fault.c:51(fault_report)
  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/07 18:16:30.895237,  0] lib/fault.c:52(fault_report)
  INTERNAL ERROR: Signal 11 in pid 99933 (3.6.25)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2017/01/07 18:16:30.895266,  0] lib/fault.c:54(fault_report)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2017/01/07 18:16:30.895321,  0] lib/fault.c:55(fault_report)
  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/07 18:16:30.895341,  0] lib/util.c:1117(smb_panic)
  PANIC (pid 99933): internal error
[2017/01/07 18:16:30.910685,  0] lib/util.c:1221(log_stack_trace)
  BACKTRACE: 5 stack frames:
   #0 0x1409188 <log_stack_trace+0x28> at /usr/local/sbin/smbd
   #1 0x1408a92 <smb_panic+0x52> at /usr/local/sbin/smbd
   #2 0x13f94d0 <fault_setup+0x190> at /usr/local/sbin/smbd
   #3 0x802ded78f <pthread_sigmask+0x4ff> at /lib/libthr.so.3
   #4 0x802decd6f <pthread_getspecific+0xe9f> at /lib/libthr.so.3
[2017/01/07 18:16:30.910851,  0] lib/fault.c:416(dump_core)
  dumping core in /var/log/samba/cores/smbd
[2017/01/07 18:16:30.913026,  0] lib/fault.c:51(fault_report)
  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/07 18:16:30.913083,  0] lib/fault.c:52(fault_report)
  INTERNAL ERROR: Signal 11 in pid 99928 (3.6.25)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2017/01/07 18:16:30.913110,  0] lib/fault.c:54(fault_report)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2017/01/07 18:16:30.913135,  0] lib/fault.c:55(fault_report)
  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/07 18:16:30.913156,  0] lib/util.c:1117(smb_panic)
  PANIC (pid 99928): internal error
[2017/01/07 18:16:30.927939,  0] lib/util.c:1221(log_stack_trace)
  BACKTRACE: 5 stack frames:
   #0 0x1409188 <log_stack_trace+0x28> at /usr/local/sbin/smbd
   #1 0x1408a92 <smb_panic+0x52> at /usr/local/sbin/smbd
   #2 0x13f94d0 <fault_setup+0x190> at /usr/local/sbin/smbd
   #3 0x802ded78f <pthread_sigmask+0x4ff> at /lib/libthr.so.3
   #4 0x802decd6f <pthread_getspecific+0xe9f> at /lib/libthr.so.3
[2017/01/07 18:16:30.928086,  0] lib/fault.c:416(dump_core)
  dumping core in /var/log/samba/cores/smbd

After cleaning /var/db/samba, log.smbd changes to:

[2017/01/07 19:26:18.661062,  0] ../lib/util/debug.c:413(talloc_log_fn)
  Bad talloc magic value - unknown value
[2017/01/07 19:26:18.661179,  0] lib/util.c:1117(smb_panic)
  PANIC (pid 2024): Bad talloc magic value - unknown value
[2017/01/07 19:26:18.672698,  0] lib/fault.c:51(fault_report)
  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/07 19:26:18.672898,  0] lib/fault.c:52(fault_report)
  INTERNAL ERROR: Signal 11 in pid 2171 (3.6.25)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2017/01/07 19:26:18.672996,  0] lib/fault.c:54(fault_report)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2017/01/07 19:26:18.673086,  0] lib/fault.c:55(fault_report)
  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/07 19:26:18.673150,  0] lib/util.c:1117(smb_panic)
  PANIC (pid 2171): internal error
[2017/01/07 19:26:18.678661,  0] lib/util.c:1221(log_stack_trace)
  BACKTRACE: 15 stack frames:
   #0 0x1409188 <log_stack_trace+0x28> at /usr/local/sbin/smbd
   #1 0x1408a92 <smb_panic+0x52> at /usr/local/sbin/smbd
   #2 0x80321bc47 <talloc_set_memlimit+0xdd7> at /usr/local/lib/libtalloc.s=
o.2
   #3 0x80321b783 <talloc_set_memlimit+0x913> at /usr/local/lib/libtalloc.s=
o.2
   #4 0x80321b783 <talloc_set_memlimit+0x913> at /usr/local/lib/libtalloc.s=
o.2
   #5 0x1418451 <server_event_context_free+0x21> at /usr/local/sbin/smbd
   #6 0x16355ed <exit_server+0x14d> at /usr/local/sbin/smbd
   #7 0x1635741 <exit_server_cleanly+0x11> at /usr/local/sbin/smbd
   #8 0x1634700 <main+0x1730> at /usr/local/sbin/smbd
   #9 0x80342992e <tevent_common_check_signal+0xee> at
/usr/local/lib/libtevent.so.0
   #10 0x1417b9b <run_events_poll+0x2b> at /usr/local/sbin/smbd
   #11 0x14182e4 <s3_tevent_context_init+0x164> at /usr/local/sbin/smbd
   #12 0x803424fe8 <_tevent_loop_once+0x78> at /usr/local/lib/libtevent.so.0
   #13 0x16340e7 <main+0x1117> at /usr/local/sbin/smbd
   #14 0x1128b11 <_start+0x1b1> at /usr/local/sbin/smbd
[2017/01/07 19:26:18.680380,  0] lib/fault.c:416(dump_core)
  dumping core in /var/log/samba/cores/smbd
[2017/01/07 19:26:18.689473,  0] lib/util.c:1221(log_stack_trace)
  BACKTRACE: 5 stack frames:
   #0 0x1409188 <log_stack_trace+0x28> at /usr/local/sbin/smbd
   #1 0x1408a92 <smb_panic+0x52> at /usr/local/sbin/smbd
   #2 0x13f94d0 <fault_setup+0x190> at /usr/local/sbin/smbd
   #3 0x802ded78f <pthread_sigmask+0x4ff> at /lib/libthr.so.3
   #4 0x802decd6f <pthread_getspecific+0xe9f> at /lib/libthr.so.3
[2017/01/07 19:26:18.689815,  0] lib/fault.c:416(dump_core)
  dumping core in /var/log/samba/cores/smbd

Reverting to talloc-2.1.6, tevent-0.9.28, and tdb-1.3.12,1 solved the issue.

--=20
You are receiving this mail because:
You are the assignee for the bug.=

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215859-13>