[Samba] active connection gets lost in samba version 3.0 beta 3

david de leeuw david at bgumail.bgu.ac.il
Thu Jul 24 17:39:39 GMT 2003


Hi Jason,

With these parameters Word crashes as well, but the messages in the log are
very different.

Now I get "Transport endpoint is not connected"
"write_socket_data: write failure. Error = Connection reset by peer"
etc.

See the log.

David

---- Original Message ----- 
From: "Jason C. Waters" <jwaters at h2os.com>
To: <samba at lists.samba.org>
Sent: Thursday, July 24, 2003 8:25 PM
Subject: Re: [Samba] active connection gets lost in samba version 3.0 beta 3


> Try adding these to your global configuration
>
> locking = no
> level2 oplocks = no
----------------------------------------------------------------------------
-----------------

 2003/07/24 19:23:30, 0] lib/util_sock.c:get_socket_addr(900)
  getpeername failed. Error was Transport endpoint is not connected
[2003/07/24 19:23:30, 0] lib/util_sock.c:write_socket_data(388)
  write_socket_data: write failure. Error = Connection reset by peer
[2003/07/24 19:23:30, 0] lib/util_sock.c:write_socket(413)
  write_socket: Error writing 4 bytes to socket 16: ERRNO = Connection reset
by peer
[2003/07/24 19:23:30, 0] lib/util_sock.c:send_smb(574)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2003/07/24 19:23:30, 1] smbd/service.c:make_connection_snum(692)
  davidws-2 (132.72.73.97) connect to service lodewijk initially as user
lodewijk (uid=516, gid=521) (pid 1387)
[2003/07/24 19:24:42, 0] lib/fault.c:fault_report(36)
  ===============================================================
[2003/07/24 19:24:42, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 1387 (3.0.0beta3)
  Please read the appendix Bugs of the Samba HOWTO collection
[2003/07/24 19:24:42, 0] lib/fault.c:fault_report(39)
  ===============================================================
[2003/07/24 19:24:42, 0] lib/util.c:smb_panic(1462)
  PANIC: internal error
[2003/07/24 19:24:42, 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+0x298) [0x80c6fa8]
   #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:24:42, 1] smbd/service.c:make_connection_snum(692)
  davidws-2 (132.72.73.97) connect to service lodewijk initially as user
lodewijk (uid=516, gid=521) (pid 1395)
[2003/07/24 19:25:51, 0] lib/fault.c:fault_report(36)
  ===============================================================
[2003/07/24 19:25:51, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 1395 (3.0.0beta3)
  Please read the appendix Bugs of the Samba HOWTO collection
[2003/07/24 19:25:51, 0] lib/fault.c:fault_report(39)
  ===============================================================
[2003/07/24 19:25:51, 0] lib/util.c:smb_panic(1462)
  PANIC: internal error
[2003/07/24 19:25:51, 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:42:03, 0] lib/charcnv.c:convert_string(194)
  convert_string: Required 25, available 16
[2003/07/24 19:42:03, 1] smbd/service.c:make_connection_snum(692)
  davidws-2 (132.72.73.97) connect to service lodewijk initially as user
lodewijk (uid=516, gid=521) (pid 1530)
[2003/07/24 19:43:13, 0] lib/fault.c:fault_report(36)
  ===============================================================
[2003/07/24 19:43:13, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 1530 (3.0.0beta3)
  Please read the appendix Bugs of the Samba HOWTO collection
[2003/07/24 19:43:13, 0] lib/fault.c:fault_report(39)
  ===============================================================
[2003/07/24 19:43:13, 0] lib/util.c:smb_panic(1462)
  PANIC: internal error
[2003/07/24 19:43:13, 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]


>
> david de leeuw wrote:
>
> >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.
 > > [...]
> >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





More information about the samba mailing list