Samba 3.0.4 with recommendes patches on Solaris 8 (with increased settings for filedescriptor). System runs well under normal load. In peak hours (500-600 Clients) the following message appears. [2004/06/08 16:39:28, 0] lib/util.c:smb_panic2(1398) PANIC: internal error [2004/06/08 16:39:28, 0] smbd/tdbutil.c:smbd_tdb_log(42) tdb(/usr/local/smb/xxxxx/locking.tdb): tdb_reopen: open failed (No such file or directory) [2004/06/08 16:39:28, 0] smbd/server.c:open_sockets_smbd(419) tdb_reopen_all failed. [2004/06/08 16:39:28, 0] lib/util.c:smb_panic2(1398) PANIC: tdb_reopen_all failed. [2004/06/08 16:39:28, 0] lib/fault.c:fault_report(36) =============================================================== [2004/06/08 16:39:28, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 6 in pid 10969 (3.0.4) Please read the appendix Bugs of the Samba HOWTO collection [2004/06/08 16:39:28, 0] lib/fault.c:fault_report(39) =============================================================== [2004/06/08 16:39:28, 0] lib/util.c:smb_panic2(1398) PANIC: internal error As stated in the messages the logging.tdb disappears. Login of new users is impossible. Users already logged in seems to be unaffected, as long no new resource is mounted. After restart system works without problems, after a short time, the same problem appears.
Just to add a comment: I've seen that as well, but I did not have the time to track it down. The locking.tdb simply vanished. *VERY* weird. This was a customer system and I was not sure that someone else on the system might have done it. Volker Lendecke
This seems to be real. Just got another report. What on earth can just delete the locking.tdb???? Volker
Just to make sure all information is collected here. We suspect that the unlink of locking.tdb might have happened in smbd_tdb_log after a corruption. The calls to smbd_tdb_log have been removed in svn (and 3.0.5.rc1), so this comes down to a tdb corruption problem. Volker
i was able to repoduce the bug only one time: while executing ./smbstatus in 10-seconds-intervals, ./smbstatus told after a while, that locking.tdb is corrupt one time, after this, smbstatus did not report locks at all.
On the advice of Volker I'm closing this one. During my work on deferred opens I discovered a bug in the locking code that could cause memory overwrites and corruption in the code that called the tdb writes to locking.tdb. This could cause this bug. If this can be reproduced in 3.0.5preX or above then please re-open. Jeremy.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.