Hello, We use samba to backup some (rather large) sql databases.
Lately we ocasionally are getting fail reports, as in the file could not be written, and windows generating an error 64: "The specified network name is no longer available" While going trough the logs, i can see the following error (sorry for the long output): ----- [2008/05/19 01:14:46, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client x.x.x.x. Error Broken pipe [2008/05/19 01:14:46, 0] lib/util_sock.c:send_smb(769) Error writing 39 bytes to client. -1. (Broken pipe) [2008/05/19 01:14:46, 1] smbd/service.c:close_cnum(1150) xxxxx (x.x.x.x) closed connection to service xxxxx [2008/05/19 01:16:25, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client x.x.x.x. Error Broken pipe [2008/05/19 01:16:25, 0] lib/util_sock.c:send_smb(769) Error writing 62 bytes to client. -1. (Broken pipe) [2008/05/19 01:16:25, 1] smbd/service.c:close_cnum(1150) xxxxx (x.x.x.x) closed connection to service xxxxx [2008/05/19 01:16:25, 0] smbd/server.c:exit_server_common(657) =============================================================== [2008/05/19 01:16:25, 0] smbd/server.c:exit_server_common(659) Abnormal server exit: send_trans2_replies: send_smb failed. [2008/05/19 01:16:25, 0] smbd/server.c:exit_server_common(660) =============================================================== [2008/05/19 01:16:25, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 11 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c373] #1 /usr/sbin/smbd [0x82c2265] #2 /usr/sbin/smbd [0x82c2413] #3 /usr/sbin/smbd [0x80c39c8] #4 /usr/sbin/smbd(handle_trans2+0x2453) [0x80cd623] #5 /usr/sbin/smbd(reply_trans2+0x64c) [0x80d112c] #6 /usr/sbin/smbd [0x80ea674] #7 /usr/sbin/smbd(smbd_process+0x6f8) [0x80eb838] #8 /usr/sbin/smbd(main+0x10df) [0x82c380f] #9 /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7c38ea8] #10 /usr/sbin/smbd [0x8082b11] [2008/05/19 01:16:25, 0] smbd/server.c:exit_server_common(664) Last message was SMBtrans2 [2008/05/19 01:16:25, 5] lib/util.c:show_msg(485) [2008/05/19 01:16:25, 5] lib/util.c:show_msg(495) size=84 smb_com=0x32 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=24 smb_flg2=55303 smb_tid=1 smb_pid=5320 smb_uid=0 smb_mid=26752 smt_wct=15 smb_vwv[ 0]= 6 (0x6) smb_vwv[ 1]= 8 (0x8) smb_vwv[ 2]= 2 (0x2) smb_vwv[ 3]= 0 (0x0) smb_vwv[ 4]= 0 (0x0) smb_vwv[ 5]= 0 (0x0) smb_vwv[ 6]= 0 (0x0) smb_vwv[ 7]= 0 (0x0) smb_vwv[ 8]= 0 (0x0) smb_vwv[ 9]= 6 (0x6) smb_vwv[10]= 68 (0x44) smb_vwv[11]= 8 (0x8) smb_vwv[12]= 76 (0x4C) smb_vwv[13]= 1 (0x1) smb_vwv[14]= 8 (0x8) smb_bcc=19 [2008/05/19 01:16:25, 10] lib/util.c:dump_data(2222) [000] 00 00 00 11 14 FC 03 00 00 00 00 00 06 00 00 00 ........ ........ [010] 00 00 00 ... [2008/05/19 01:16:25, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd ----- Here i see dumping core in /var/log/samba/cores/smbd, but i don't see it there at all. Apart from that, can anyone give me an indication of what is going on here, and why it is exiting? Here are some system components: Kernel: 2.6.20.3 OS: Debian (etch) Samba: 3.0.24-6etch8 Proc: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz Mem: 2071640kB Disk: 5x 500G (RAID5) Raid: LSI Logic SAS based MegaRAID driver Thanks alot for looking into this. Cheers, Mark. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
