I have a machine running redhat 6.2 and samba 2.0.6 that does a persistent mount to my Windows 2000 machine for the purposes of serving files via FTP. The samba connection occasionally times out it seems, I get the message smb_request: result -32, setting invalid smb_retry: new pid=20679, generation=12 and it generates a new connection I've got SO_KEEPALIVE active in the socket options in my SMB.CONF to try and maintain the connections. The problem is that when it generates a new connection, the old connection port is left in a CLOSE state for a long time, occasionally long enough that it manages to crash the server (Based on the log I think PROFTPD helps crash it but I'm not sure.) Mar 5 11:14:59 trentuc kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000040 Mar 5 11:14:59 trentuc kernel: current->tss.cr3 = 01f53000, %cr3 = 01f53000 Mar 5 11:14:59 trentuc kernel: *pde = 00000000 Mar 5 11:14:59 trentuc kernel: Oops: 0002 Mar 5 11:14:59 trentuc kernel: CPU: 0 Mar 5 11:14:59 trentuc kernel: EIP: 0010:[schedule+132/640] Mar 5 11:14:59 trentuc kernel: EFLAGS: 00010046 Mar 5 11:14:59 trentuc kernel: eax: 00000000 ebx: c0d0c000 ecx: 00000001 edx: 00000000 Mar 5 11:14:59 trentuc kernel: esi: c024bc00 edi: 0000000e ebp: c0d0df08 esp: c0d0def8 Mar 5 11:14:59 trentuc kernel: ds: 0018 es: 0018 ss: 0018 Mar 5 11:14:59 trentuc kernel: Process proftpd (pid: 3382, process nr: 36, stackpage=c0d0d000) Mar 5 11:14:59 trentuc kernel: Stack: 0000000e 00002000 00000286 c024bc00 c0d0df30 c01115c0 c0d0df1c 00000000 Mar 5 11:14:59 trentuc kernel: 00002000 c0d2df1c c021d804 016bb3f0 c0d0c000 c011121c 00000000 c012f821 Mar 5 11:14:59 trentuc kernel: c06bd994 0000000e c06bd998 0000002d 00000104 0000000e c0d0c000 00000062 Mar 5 11:14:59 trentuc kernel: Call Trace: [schedule_timeout+108/140] [process_timeout+0/16] [do_select+157/532] [sys_select+1014/1360] [syst em_call+52/56] Mar 5 11:14:59 trentuc kernel: Code: 89 42 40 89 50 3c c7 43 3c 00 00 00 00 c7 43 40 00 00 00 00 any ideas would be appreciated Coruscare icq 37404155 ------------------------------------------------------------- Sign up for ICQmail at http://www.icq.com/icqmail/signup.html
On 6 Mar 2001, coruscare wrote:> I have a machine running redhat 6.2 and samba 2.0.6 that does a > persistent mount to my Windows 2000 machine for the purposes of > serving files via FTP.Try upgrading to samba 2.0.7 plus this patch http://www.hojdpunkten.ac.se/054/samba/smbmount-2.0.7-ascii+fixes.patch It should fix the bug with sockets not being closed and fixes a few memory leaks. Be sure to use 2.2.18 if you are going to do serious smbfs work, earlier versions have a few rarely triggered but nasty bugs that may corrupt memory.> I've got SO_KEEPALIVE active in the socket options in my SMB.CONF to > try and maintain the connections.Being disconnected seems to be unavoidable. With winNT you can set the autodisconnect timeout of the server with this registry setting: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\autodisconnect Valid values: -1 to 65535 minutes (?) I think that setting works with win2k as well.> Mar 5 11:14:59 trentuc kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000040Ouch. But this does not have to be directly related to the sockets waiting in close. /Urban
The ports are still lingering in a closed status tcp 0 0 192.168.2.17:139 0.0.0.0:* LISTEN tcp 0 0 192.168.2.17:3534 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:3535 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:3536 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:3537 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:139 192.168.2.20:3827 ESTABLISHED tcp 0 0 192.168.2.17:3539 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:3540 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:3541 192.168.2.20:139 CLOSE tcp 0 0 192.168.2.17:3542 192.168.2.20:139 CLOSE Any further ideas? On Tue, 06 March 2001, Urban Widmark wrote:> > On 6 Mar 2001, coruscare wrote: > > > I have a machine running redhat 6.2 and samba 2.0.6 that does a > > persistent mount to my Windows 2000 machine for the purposes of > > serving files via FTP. > > Try upgrading to samba 2.0.7 plus this patch > http://www.hojdpunkten.ac.se/054/samba/smbmount-2.0.7-ascii+fixes.patch > > It should fix the bug with sockets not being closed and fixes a few memory > leaks. > > Be sure to use 2.2.18 if you are going to do serious smbfs work, earlier > versions have a few rarely triggered but nasty bugs that may corrupt > memory. > > > I've got SO_KEEPALIVE active in the socket options in my SMB.CONF to > > try and maintain the connections. > > Being disconnected seems to be unavoidable. With winNT you can set the > autodisconnect timeout of the server with this registry setting: > > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\autodisconnect > Valid values: -1 to 65535 minutes (?) > > I think that setting works with win2k as well. > > > > Mar 5 11:14:59 trentuc kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000040 > > Ouch. But this does not have to be directly related to the sockets waiting > in close. > > /Urban > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba------------------------------------------------------------- Sign up for ICQmail at http://www.icq.com/icqmail/signup.html
On 7 Mar 2001, Howard Nugent wrote:> The ports are still lingering in a closed status > tcp 0 0 192.168.2.17:139 0.0.0.0:* LISTEN > tcp 0 0 192.168.2.17:3534 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:3535 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:3536 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:3537 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:139 192.168.2.20:3827 ESTABLISHED > tcp 0 0 192.168.2.17:3539 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:3540 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:3541 192.168.2.20:139 CLOSE > tcp 0 0 192.168.2.17:3542 192.168.2.20:139 CLOSEAll of these in CLOSE are expected on an unpatched smbmount, but I was pretty sure this was fixed by the patch. Are you sure you are not still using the old smbmount binary? The new smbmount should log things to /usr/local/samba/var/log.smbmount (or similar, depending on how your logging is setup). /Urban
Looks like I forgot to configure --with-smbmount :( On Wed, 07 March 2001, Urban Widmark wrote:> > On 7 Mar 2001, Howard Nugent wrote: > > > The ports are still lingering in a closed status > > tcp 0 0 192.168.2.17:139 0.0.0.0:* LISTEN > > tcp 0 0 192.168.2.17:3534 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:3535 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:3536 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:3537 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:139 192.168.2.20:3827 ESTABLISHED > > tcp 0 0 192.168.2.17:3539 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:3540 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:3541 192.168.2.20:139 CLOSE > > tcp 0 0 192.168.2.17:3542 192.168.2.20:139 CLOSE > > All of these in CLOSE are expected on an unpatched smbmount, but I was > pretty sure this was fixed by the patch. Are you sure you are not still > using the old smbmount binary? > > The new smbmount should log things to /usr/local/samba/var/log.smbmount > (or similar, depending on how your logging is setup). > > /Urban > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba------------------------------------------------------------- Sign up for ICQmail at http://www.icq.com/icqmail/signup.html
On 8 Mar 2001, Howard Nugent wrote:> Looks like I forgot to configure --with-smbmount :(Why the sad face? The patch not working because of a user error is excellent news! If you are doing everything right (w/ patch) and still get this problem, then you are having a much more exotic problem than the one this patch tries to fix. The only people I know who likes exotic problems are people with time to spare ... :) /Urban