samba - Jul 2004 - Samba 3.0.5 PANIC

Hi, all:

   I am using Samba 3.0.5 with patch at
http://samba.org/~jerry/patches/post-3.0.4/.
But I found the follow messages in samba log:

  ==============================================================[2004/07/29
01:01:57, 0] lib/util.c:smb_panic2(1398)
  PANIC: internal error
[2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1406)
  BACKTRACE: 3 stack frames:
   #0 smbd(smb_panic2+0xef) [0x8179111]
   #1 /lib/libc.so.6(abort+0x18b) [0x4016389b]
   #2 smbd(readdirname+0) [0x81791d1]
[2004/07/29 01:01:57, 0] tdb/tdbutil.c:tdb_log(725)
  tdb(/var/samba/ntforms.tdb): tdb_reopen: open failed (No such file or
directory)
[2004/07/29 01:01:57, 0] smbd/server.c:open_sockets_smbd(419)
  tdb_reopen_all failed.
[2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1398)
  PANIC: tdb_reopen_all failed.
[2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1406)
  BACKTRACE: 1 stack frames:
   #0 smbd(smb_panic2+0xef) [0x8179111]
[2004/07/29 01:01:57, 0] lib/fault.c:fault_report(36)
  ==============================================================[2004/07/29
01:01:57, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 6 in pid 4711 (3.0.5)
  Please read the appendix Bugs of the Samba HOWTO collection
[2004/07/29 01:01:57, 0] lib/fault.c:fault_report(39)
  ===============================================================	

Best Regards!

Jacky Kim
.

On Thu, Jul 29, 2004 at 09:18:54AM +0800, Jacky Kim
wrote:
> Hi, all:
> 
>    I am using Samba 3.0.5 with patch at
http://samba.org/~jerry/patches/post-3.0.4/.
> But I found the follow messages in samba log:
This may be a bug we have already fixed in the 3.0.6 stream (what was
called 3.0.5 before the security release). Can you try one of these
pre-releases and see if the problem still occurs ?

Jeremy.

Hi, David:
	
   I don't use printers at all. so i think it has nothing with printer lock.

Best Regards!

Jacky Kim
.
>Hi,
>
>This is worrying as we have had exactly the same error with 3.0.2a on
>Solaris/cups.
>
>Have you had a problem with printers as well? I believe our error was caused
>by printing crashing samba, and a quick fix was to delete the printer lock
>file. However, when I emailed the problem, we were told by Samba.org to
>upgrade to 3.0.5!
>
>David