[Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)

Marcin Kucharczyk marcinkk at enter.net.pl
Sun Nov 25 12:39:25 GMT 2007


Sunday, November 25, 2007, 12:25:27 AM, you wrote:

DV> marcinkk at enter.net.pl wrote:
>> I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, 
>> SMP, 6.2 RELEASE). My log.smbd looks like below:

>> [...]

>> [2007/11/24 16:55:22, 0] 
>> /usr/ports/net/samba3/work/samba-3.0.26a/source/lib/pidfile.c:pidfile_create(112) 

>>  ERROR: smbd is already running. File /var/run/smbd.pid exists and 
>> process id 1961 is running.

>> --- /var/run/smbd.pid exists, becase the error is created after 
>> unexpected system shutdown...
DV> What os the unexpected system shutdown?  Power failure?  Reset button 
DV> after system freeze?

The power failure.

>> [2007/11/24 16:59:53, 0] lib/util_tdb.c:tdb_log(662)
>>  tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such 
>> file or directory)
>> [2007/11/24 16:59:53, 0] smbd/server.c:open_sockets_smbd(572)
>>  tdb_reopen_all failed.
>> [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632)
>>  PANIC (pid 2621): tdb_reopen_all failed.
>> [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41)
DV> The filesystem didn't flush it's buffers on shutdown.  Unexpectedly, 
DV> files are missing and/or corrupted that should be there on startup.

Probably corrupted, becouse I checked: the files exist...

>> And after start samba works properly until next unexpected system 
>> restart  
DV> You need to fix this and ensure you're using a journaled file system 
DV> with whatever option is available for the safest, most conservative 
DV> journaling mode.

The problem started after 3.0.26a upgrade. I had 3.0.32c run without any problems.

>> Without deleting /var/db/samba, than the samba will start and 
>> procedure described on the start of this message will be repeated  
DV> You should be able to delete /var/db/samba (plus maybe the pid file) and
DV> restart samba.  Samba will create any tdb files it needs like the 
DV> initial startup.

Tried ... reinstall was required

Some mor information:

It looks like the same or similar problem:

My system works with ayhlion 64 x2, but I had similar problem on single processor configuration: pentium 4 and duron too. The problem apears not only after power failure, but also after samba upgrade from ports - make deinstall reinstall. /var/db/samba need to be deleted before reinstall becase samba 3.0.26a has the problem with start with tdb files form 3.0.23c.

Best regards,
 Marcin  K.                          mailto:marcinkk at enter.net.pl

More information about the samba mailing list