Re: [Samba] Issue with Samba version 3.0.25b on Debian
Quoting Volker Lendecke ([EMAIL PROTECTED]): 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. To Dan: please also consider installing the samba-dbg package before trying to reproduce such bug. This is likely to give more information to developers as the binaries in that package are not stripped. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Issue with Samba version 3.0.25b on Debian
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 truncated That'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 pgpE6wTDeWihv.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Issue with Samba version 3.0.25b on Debian
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. 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 [2007/08/08 09:00:43, 0] lib/util.c:log_stack_trace(1736) BACKTRACE: 11 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x827c5cd] #1 /usr/sbin/smbd(smb_panic+0x5d) [0x827c6fd] #2 /usr/sbin/smbd [0x8220b28] #3 /usr/sbin/smbd(talloc_free+0x1c1) [0x8261a81] #4 /usr/sbin/smbd(open_directory+0x5e4) [0x80f4be4] #5 /usr/sbin/smbd(reply_ntcreate_and_X+0x10b5) [0x80c1105] #6 /usr/sbin/smbd [0x810ace0] #7 /usr/sbin/smbd(smbd_process+0x836) [0x810c076] #8 /usr/sbin/smbd(main+0xbdd) [0x834ffad] #9 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7b4b030] #10 /usr/sbin/smbd [0x8093f31] [2007/08/08 09:00:43, 0] lib/util.c:smb_panic(1637) smb_panic(): calling panic action [/usr/share/samba/panic-action 18483] [2007/08/08 09:00:43, 0] lib/util.c:smb_panic(1645) smb_panic(): action returned status 0 [2007/08/08 09:00:43, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd -- 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 That'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. I just checked now which is a quiet period and indeed, the messages do not show. One less thing to worry about :-) Regards, Dan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Issue with Samba version 3.0.25b on Debian
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? Volker pgpdWNBYAfw1T.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Issue with Samba version 3.0.25b on Debian
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? Volker Hi, It is OK, there is a lot of space left on the disk. Regards, Dan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Issue with Samba version 3.0.25b on Debian
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 pgp1zPKVo8eOf.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Issue with Samba version 3.0.25b on Debian
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 I'm using ext3 with RAID1. Here are some more details: -- server01:/home/dan# df -h FilesystemSize Used Avail Use% Mounted on /dev/md0 72G 15G 54G 21% / tmpfs 248M 0 248M 0% /lib/init/rw udev 10M 60K 10M 1% /dev tmpfs 248M 0 248M 0% /dev/shm server01:/home/dan# mdadm --detail /dev/md0 /dev/md0: Version : 00.90.03 Creation Time : Fri Apr 22 15:38:44 2005 Raid Level : raid1 Array Size : 76172096 (72.64 GiB 78.00 GB) Device Size : 76172096 (72.64 GiB 78.00 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sun Aug 12 13:43:09 2007 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 2fae712e:5c464738:f87979ca:777de3c9 Events : 0.6969538 Number Major Minor RaidDevice State 0 820 active sync /dev/sda2 1 8 181 active sync /dev/sdb2 -- I have deleted the locking.tdb like you have said. I will monitor from now and report back. Tomorrow the users will start using the files again. Regards, Dan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
