From owner-freebsd-questions@freebsd.org Mon Feb 13 22:19:16 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F685CDED56 for ; Mon, 13 Feb 2017 22:19:16 +0000 (UTC) (envelope-from freebsd01@dgmm.net) Received: from outbound-queue-adx-2.mail.thdo.gradwell.net (outbound-queue-adx-2.mail.thdo.gradwell.net [212.11.71.247]) by mx1.freebsd.org (Postfix) with ESMTP id 4B7E0116F for ; Mon, 13 Feb 2017 22:19:15 +0000 (UTC) (envelope-from freebsd01@dgmm.net) Received: from outbound-edge-adx-2.mail.thdo.gradwell.net (outbound-edge-adx-2.mail.thdo.gradwell.net [212.11.71.231]) by outbound-queue-adx-2.mail.thdo.gradwell.net (Postfix) with ESMTP id 3A09A21E18 for ; Mon, 13 Feb 2017 22:18:09 +0000 (GMT) Received: from cpc89374-jarr11-2-0-cust348.16-2.cable.virginm.net (HELO amd.asgard.uk) (82.13.141.93) (smtp-auth username fbsd%pop3.dgmm.net, mechanism plain) by outbound-edge-adx-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with ESMTPA; Mon, 13 Feb 2017 22:18:09 +0000 From: Dave To: freebsd-questions@freebsd.org Subject: Re: Samba36 core dumping [solved] Date: Mon, 13 Feb 2017 22:18:08 +0000 Message-ID: <11439909.J1DoK4jPzF@amd.asgard.uk> User-Agent: KMail/4.14.10 (FreeBSD/10.3-RELEASE-p11; KDE/4.14.10; amd64; ; ) In-Reply-To: <9278413.674eVpYzjd@amd.asgard.uk> References: <9278413.674eVpYzjd@amd.asgard.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Gradwell-MongoId: 58a230a1.231a-56a3-2 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: fbsd@pop3.dgmm.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 22:19:16 -0000 On Monday 06 February 2017 02:42:52 Dave wrote: > Anyone else had this samba core dump error and fixed it? > > I just did a rebuild of samba36 and all the related build/run depends ports followed by a service samba restart > > If it's just me with the problem is there enough below to point me in the right direction to fix it? > > uname -a > FreeBSD server.asgard.uk 10.3-RELEASE-p11 FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > server:/var/log/samba %tail -F log.smbd > > [2017/02/06 02:12:55.416399, 0] lib/fault.c:51(fault_report) > =============================================================== > [2017/02/06 02:12:55.416493, 0] lib/fault.c:52(fault_report) > INTERNAL ERROR: Signal 10 in pid 13545 (3.6.25) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2017/02/06 02:12:55.416546, 0] lib/fault.c:54(fault_report) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2017/02/06 02:12:55.416716, 0] lib/fault.c:55(fault_report) > =============================================================== > [2017/02/06 02:12:55.416826, 0] lib/util.c:1117(smb_panic) > PANIC (pid 13545): internal error > [2017/02/06 02:12:55.434707, 0] lib/util.c:1221(log_stack_trace) > BACKTRACE: 5 stack frames: > #0 0x14087a8 at /usr/local/sbin/smbd > #1 0x14080b2 at /usr/local/sbin/smbd > #2 0x13f9050 at /usr/local/sbin/smbd > #3 0x802de0b4a at /lib/libthr.so.3 > #4 0x802de022c at /lib/libthr.so.3 > [2017/02/06 02:12:55.434948, 0] lib/fault.c:416(dump_core) > dumping core in /var/log/samba/cores/smbd Oops, sorry for not getting back on this one. Samba36 is EOL so I finally upgraded to Samba44 and all is well again.