>>>>>>>>>>>>>>>>>> Ursprüngliche Nachricht <<<<<<<<<<<<<<<<<<
Am 30.10.02, 17:56:54, schrieb [EMAIL PROTECTED] zum Thema Re: [Samba] internal error: signal 11: > On Wed, Oct 30, 2002 at 11:35:42AM +0000, Gerhard Vögel wrote: > > Hello, > > > > we got the following error in the samba logs: > > > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(38) > > Oct 30 06:29:01 hornbill smbd[12783]: > > =============================================================== > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(39) > > Oct 30 06:29:01 hornbill smbd[12783]: INTERNAL ERROR: Signal 11 in pid > > 12783 (2.2.6-SuSE) > > Oct 30 06:29:01 hornbill smbd[12783]: Please read the file BUGS.txt in > > the distribution > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(41) > > Oct 30 06:29:01 hornbill smbd[12783]: > > =============================================================== > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/util.c:smb_panic(1094) > > Oct 30 06:29:01 hornbill smbd[12783]: PANIC: internal error > > Oct 30 06:29:01 hornbill smbd[12783]: > > > > The error is continuously repeated with increased pids until the machine > > will be rebooted. Restart of smbd, nmbd and winbind has no effect. > > > > Clients can connect to samba but they cannot access files. File access on > > NT clients is aborted with different messages. > > > > Samba version is 2.2.6 (Suse RPM) and linux kernel is 2.4.19, but it > > already happened with 2.2.4 and kernel 2.4.16. I cannot reproduce the > > error, but it happens once in a week. > Can you add the following to the smb.conf file : > In the [global] section add : > panic action = /bin/sleep 99999 > and then when this occurs attach to the frozen smbd process > with gdb. Once attached, type "bt" (backtrace) at the gdb > prompt and then mail in the backtrace. Please ensure smbd is > built with symbols. > This will help us track down and fix the bug. I'll try, but the server already is in production use and I am not always there and cannot foresee when the next problem occurs. So it could take months to get a backtrace. Do you have any other suggestions or any ideas what may have the invalid memory reference? Thanks Gerhard -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
