Hello everyone! After upgrading from samba 3.4.9 to samba 3.6.1 on a FreeBSD 8.1 x86 system smbd stopped working. It starts successfully, but crashes as soon as someone tries to connect to a share. Log file contains a lot of entries like the following: [2012/02/06 11:05:13, 1] lib/util_tdb.c:521(tdb_wrap_log) tdb(unnamed): tdb_open_ex: spinlocks no longer supported [2012/02/06 11:05:13, 0] lib/messages_local.c:112(messaging_tdb_init) ERROR: Failed to initialise messages database: Unknown error: 0 [2012/02/06 11:05:13, 0] lib/messages.c:245(messaging_reinit) messaging_tdb_init failed: NT_STATUS_UNSUCCESSFUL [2012/02/06 11:05:13, 0] lib/util.c:961(reinit_after_fork) messaging_reinit() failed: NT_STATUS_UNSUCCESSFUL [2012/02/06 11:05:13, 0] smbd/server.c:388(smbd_accept_connection) reinit_after_fork() failed [2012/02/06 11:05:13, 0] lib/util.c:1480(smb_panic) PANIC (pid 50503): reinit_after_fork() failed [2012/02/06 11:05:13, 0] lib/util.c:1584(log_stack_trace) BACKTRACE: 8 stack frames: #0 0x12ec7cd <smb_panic+93> at /usr/local/sbin/smbd #1 0x15b164d <main+5437> at /usr/local/sbin/smbd #2 0x12fc401 <run_events+385> at /usr/local/sbin/smbd #3 0x12fc62e <event_add_to_select_args+526> at /usr/local/sbin/smbd #4 0x12fcc45 <_tevent_loop_once+149> at /usr/local/sbin/smbd #5 0x15b1247 <main+4407> at /usr/local/sbin/smbd #6 0x107a12b <_start+203> at /usr/local/sbin/smbd #7 0x107a075 <_start+21> at /usr/local/sbin/smbd [2012/02/06 11:05:13, 0] lib/fault.c:370(dump_core) dumping core in /var/log/samba34/cores/smbd It seems that something is wrong with the messages.tdb file. I have tried removing it, it was re-created but nothing has changed. Please let me know how can this be fixed? Many thanks in advance. With best regards, P. Trifonov
On Mon, Feb 06, 2012 at 11:10:05AM +0400, Peter Trifonov wrote:> Hello everyone! > > After upgrading from samba 3.4.9 to samba 3.6.1 on a FreeBSD 8.1 x86 system > smbd stopped working. > It starts successfully, but crashes as soon as someone tries to connect to a > share. > Log file contains a lot of entries like the following: > > [2012/02/06 11:05:13, 1] lib/util_tdb.c:521(tdb_wrap_log) > tdb(unnamed): tdb_open_ex: spinlocks no longer supported > [2012/02/06 11:05:13, 0] lib/messages_local.c:112(messaging_tdb_init) > ERROR: Failed to initialise messages database: Unknown error: 0 > [2012/02/06 11:05:13, 0] lib/messages.c:245(messaging_reinit) > messaging_tdb_init failed: NT_STATUS_UNSUCCESSFUL > [2012/02/06 11:05:13, 0] lib/util.c:961(reinit_after_fork) > messaging_reinit() failed: NT_STATUS_UNSUCCESSFUL > [2012/02/06 11:05:13, 0] smbd/server.c:388(smbd_accept_connection) > reinit_after_fork() failed > [2012/02/06 11:05:13, 0] lib/util.c:1480(smb_panic) > PANIC (pid 50503): reinit_after_fork() failed > [2012/02/06 11:05:13, 0] lib/util.c:1584(log_stack_trace) > BACKTRACE: 8 stack frames: > #0 0x12ec7cd <smb_panic+93> at /usr/local/sbin/smbd > #1 0x15b164d <main+5437> at /usr/local/sbin/smbd > #2 0x12fc401 <run_events+385> at /usr/local/sbin/smbd > #3 0x12fc62e <event_add_to_select_args+526> at /usr/local/sbin/smbd > #4 0x12fcc45 <_tevent_loop_once+149> at /usr/local/sbin/smbd > #5 0x15b1247 <main+4407> at /usr/local/sbin/smbd > #6 0x107a12b <_start+203> at /usr/local/sbin/smbd > #7 0x107a075 <_start+21> at /usr/local/sbin/smbd > [2012/02/06 11:05:13, 0] lib/fault.c:370(dump_core) > dumping core in /var/log/samba34/cores/smbd > > It seems that something is wrong with the messages.tdb file. I have tried > removing it, it was re-created but nothing has changed. > Please let me know how can this be fixed?Please also upgrade the libtdb from ports. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt at sernet.de
Hi Volker,> > It seems that something is wrong with the messages.tdb file. I have > > tried removing it, it was re-created but nothing has changed. > > Please let me know how can this be fixed? > > Please also upgrade the libtdb from ports.It was upgraded automatically to version 1.2.9 while building samba. The problem affects only smbd, winbind seems to work properly. With best regards, P. Trifonov
Hello folks,> After upgrading from samba 3.4.9 to samba 3.6.1 on a FreeBSD 8.1 x86 > system smbd stopped working. > It starts successfully, but crashes as soon as someone tries to connect toa> share. > Log file contains a lot of entries like the following: > > [2012/02/06 11:05:13, 1] lib/util_tdb.c:521(tdb_wrap_log) > tdb(unnamed): tdb_open_ex: spinlocks no longer supported > [2012/02/06 11:05:13, 0] lib/messages_local.c:112(messaging_tdb_init) > ERROR: Failed to initialise messages database: Unknown error: 0The problem still remains after upgrading to samba 3.6.3. It appears that spinlocks are somehow automatically enabled for any newly created database. Is there any way to avoid this behavior? With best regards, P. Trifonov
Hi all, I managed to fix the problem. The solution was to apply this patch http://www.opensource.apple.com/source/samba/samba-235/patches/ignore-tdb-sp inlock-flag to libtdb sources. Maybe this helps someone facing the same problem... With best regards, P. Trifonov> -----Original Message----- > From: samba-bounces at lists.samba.org [mailto:samba- > bounces at lists.samba.org] On Behalf Of Peter Trifonov > Sent: Thursday, February 09, 2012 12:57 AM > To: samba at lists.samba.org > Subject: Re: [Samba] smbd crashes > > Hello folks, > > > > After upgrading from samba 3.4.9 to samba 3.6.1 on a FreeBSD 8.1 x86 > > system smbd stopped working. > > It starts successfully, but crashes as soon as someone tries to > > connect to > a > > share. > > Log file contains a lot of entries like the following: > > > > [2012/02/06 11:05:13, 1] lib/util_tdb.c:521(tdb_wrap_log) > > tdb(unnamed): tdb_open_ex: spinlocks no longer supported > > [2012/02/06 11:05:13, 0] lib/messages_local.c:112(messaging_tdb_init) > > ERROR: Failed to initialise messages database: Unknown error: 0 > > The problem still remains after upgrading to samba 3.6.3. > It appears that spinlocks are somehow automatically enabled for any newly > created database. Is there any way to avoid this behavior? > > > > > > With best regards, > P. Trifonov > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >