Hi, I have an issue with Samba version 3.0.25b on Debian. I am receiving a number of mails from my server with the following:> The Samba 'panic action' script, /usr/share/samba/panic-action, > was called for PID 18483 ().> This means there was a problem with the program, such as a segfault. > However, the executable could not be found for process 18483. > It may have died unexpectedly, or you may not have permission to debug > the process.Also, when running 'smbstatus' I get the following at the bottom of the output: -- tdb(/var/run/samba/locking.tdb): tdb_rec_read bad magic 0xd9fee666 at offset=678200 locked file list truncated -- I'm not sure what's happening here as it only seems to do this once in a while. If I restart samaba it will be OK for a week or so but then I will have users report that open files are locking up etc, then I start receiving the panic e-mails and have to restart the process again. I am away until next Monday now but will reply on return, in the meantime I'd be most grateful if anyone can help me out with this issue! Regards, Dan
On Sat, Aug 11, 2007 at 10:24:07PM +0100, Dan Peachey wrote:> I have an issue with Samba version 3.0.25b on Debian. I am receiving a > number of mails from my server with the following: > > > The Samba 'panic action' script, /usr/share/samba/panic-action, > > was called for PID 18483 ().We need a backtrace from that. The log file should have it.> Also, when running 'smbstatus' I get the following at the bottom of the > output: > > -- > tdb(/var/run/samba/locking.tdb): tdb_rec_read bad magic 0xd9fee666 at > offset=678200 > locked file list truncatedThat's not desirable, but normal. smbstatus opens the tdbs readonly, which means no locking. When there's heavy activity on a larger file server, these messages are possible. It should not happen in quiet periods. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20070812/22ea81b2/attachment.bin
> On Sun, Aug 12, 2007 at 09:12:58AM +0100, Dan Peachey wrote: > > Thanks for the reply. Here is the backtrace info from the log file: > > > > -- > > [2007/08/08 08:49:54, 1] smbd/service.c:make_connection_snum(1033) > > ian (192.168.1.35) connect to service shared initially as user ianlang > > (uid=1005, gid=106) (pid 18483) > > [2007/08/08 09:00:43, 0] lib/util.c:smb_panic(1632) > > PANIC (pid 18483): Could not store share mode entry > > Is it possible that the file system where you store the > locking.tdb is full? > > VolkerHi, It is OK, there is a lot of space left on the disk. Regards, Dan
On Sun, Aug 12, 2007 at 10:31:47AM +0100, Dan Peachey wrote:> It is OK, there is a lot of space left on the disk.The next most likely reason is that you locking.tdb is indeed corrupt. reiserfs? Does it become better if you shut down smbd, delete it and restart smbd? Voler -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20070812/0fb93874/attachment.bin