Hi team, A Samba "panic" occurs after repeatedly saving "word" files on the server.
Following the panic the "active connection" disappears, but the "active shares" and "open files" stay. Windows reports different errors such as "delayed write failed", "Cannot complete the save due to a file permission error" etc. Many of the Word files appear corrupted when reopening. Our environment: --------------------- - Linux 9 Redhat - Samba 3.0 beta 3 (same problem on beta 2) - Server with 1 GB ram, lots of disk, 100 MB/s network - network switched I have been searching Google, and been switching locks, time outs and whatever for a day or so, but this didn't help. The problem started suddenly, yesterday morning, and I can not think of any network change causing the problem. The beta 2 version worked fine for a number of weeks ! We are using Unicode filenames (including Hebrew, Arabic etc. characters), but the problem occurs also with English filenames, and from different computers (usually XP SP1) The problem occurs also when the network is about empty. Here is part of the log: (names changed) -------------------------- [2003/07/24 19:21:24, 1] smbd/service.c:make_connection_snum(692) YYYws-2 (132.72.73.97) connect to service XXX initially as user XXX (uid=516, gid=521) (pid 1260) [2003/07/24 19:21:32, 1] smbd/service.c:make_connection_snum(692) ggg (132.72.74.35) connect to service zzz initially as user zzz (uid=916, gid=919) (pid 1261) [2003/07/24 19:21:49, 1] smbd/service.c:close_cnum(873) YYYws-2 (132.72.73.97) closed connection to service XXX [2003/07/24 19:21:51, 1] smbd/service.c:make_connection_snum(692) YYYws-2 (132.72.73.97) connect to service XXX initially as user XXX (uid=516, gid=521) (pid 1260) [2003/07/24 19:22:33, 0] lib/fault.c:fault_report(36) =============================================================== [2003/07/24 19:22:33, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 1261 (3.0.0beta3) Please read the appendix Bugs of the Samba HOWTO collection [2003/07/24 19:22:33, 0] lib/fault.c:fault_report(39) =============================================================== [2003/07/24 19:22:33, 0] lib/util.c:smb_panic(1462) PANIC: internal error [2003/07/24 19:22:33, 0] lib/util.c:smb_panic(1469) BACKTRACE: 11 stack frames: #0 smbd(smb_panic+0x11c) [0x81b991c] #1 smbd [0x81a8202] #2 /lib/tls/libc.so.6 [0x420275c8] #3 smbd(make_nmb_name+0x52) [0x80f8f32] #4 smbd(cli_full_connection+0x7e) [0x80d5efe] #5 smbd(change_trust_account_password+0x1ad) [0x80cc25d] #6 smbd [0x80c6b62] #7 smbd(smbd_process+0x183) [0x80c6e93] #8 smbd(main+0x4ae) [0x821f56e] #9 /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015574] #10 smbd(ldap_msgfree+0x8d) [0x8075e41] [2003/07/24 19:23:30, 0] lib/fault.c:fault_report(36) =============================================================== And here is the latest smb.conf ------------------------------------- # Samba config file created using SWAT # from 132.72.72.20 (132.72.72.20) # Date: 2003/07/23 18:10:34 # Global parameters [global] workgroup = CCC realm = AAA server string = Samba Server security = DOMAIN log file = /var/log/samba/log.%m max log size = 50 large readwrite = No local master = No domain master = No browse list = No dns proxy = No wins server = 1111111111111 ldap ssl = no map archive = No oplocks = No [homes] comment = Home Directories read only = No nt acl support = No mangling char = ^ browseable = No fake oplocks = Yes strict locking = No delete readonly = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No As I am at a complete loss what to look for next, any help would be most appreciated. Thanks David de Leeuw Head, Medical Computing Unit Ben Gurion University of the Negev Beer Sheva Israel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
