Im going to install the new version, and report back in a week or so.
Thanks for the reply!
Majeed
Tim Jordan wrote:
> I seen a there is a fix for winbind crashing in the latest release notes.
> http://download.samba.org/samba/ftp/pre/
> TJ
> On Mon, 2004-04-05 at 10:25, Majeed wrote:
>
>>/I have also been seeing this over the last few weeks. For me it also
>>happens randomly as you stated. I am trying to pin point when it
>>started, and I believe it started right after I upgraded the kernel
>>2.4.24 to 2.4.25 (vanilla sources on gentoo 1.4) (mremap problems), but
>>I can't be too sure. Samba 3.0.2 compiled with the following
options:
>>./configure --prefix=/usr --sysconfdir=/etc/samba --localstatedir=/var
>>--libdir=/usr/lib/samba --with-privatedir=/etc/samba/private
>>--with-lockdir=/var/cache/samba --with-piddir=/var/run/samba
>>--with-swatdir=/usr/share/swat --with-configdir=/etc/samba
>>--with-logfilebase=/var/log/samba --enable-static --enable-shared
>>--with-manpages-langs=en --without-spinlocks --with-libsmbclient
>>--with-automount --with-smbmount --with-winbind --with-syslog
>>--with-idmap --with-ldap --with-ads --with-krb5 --with-pam
>>
>>Here are some symptoms I am seeing when the problem occurs.
>>Symptom 1) I cannot login through ssh: Its wierd becuase i can
>>connnect, put in my username and password it authenticates but then the
>>connection gets reset. There is even a line in the ssh log file that
>>says access was granted. I then to to the console and login.
>>
>>Symptom 2) While logged into the console I run a "netstat
-antu" and get
>>some interesting results
>>tcp 0 0 sambaserv_ip:44134 win2000dc_ip:139
>>CLOSE_WAIT
>>tcp 0 0 sambaserv_ip:44072 win2000dc_ip:139
>>CLOSE_WAIT
>>tcp 0 0 sambaserv_ip:44075 win2000dc_ip:139
>>CLOSE_WAIT
>>tcp 0 0 sambaserv_ip:44076 win2000dc_ip:139
>>CLOSE_WAIT
>>tcp 0 0 sambaserv_ip:44078 win2000dc_ip:139
>>CLOSE_WAIT
>>tcp 0 0 sambaserv_ip:44079 win2000dc_ip:139
>>CLOSE_WAIT
>>
>>There are HUNDREDS of these CLOSE_WAIT lines all with different
>>ascending port numbers
>>After restarting samba and winbind netstat looked normal and everything
>>worked as it should have.
>>
>>Symptom 3) While logged into the console I check the samba log files and
>>log.winbind showed the following problems.
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>[2004/04/05 10:11:05, 0] lib/util_sock.c:open_socket_in(634)
>> open_socket_in(): socket() call failed: Too many open files
>>
>>Again there were HUNDREDS of these lines.
>>
>>So I think winbind might be the cause of the problems. This happens on
>>both my production and my test server. Test server is mirrored to
>>production for testing.
>>
>>Today I am going to download the newest version of the samba 3 and see
>>if that helps, if it doesn't then I might try a different kernel
>>version. As mentioned before all i do is restart samba and winbind and
>>thinks will work perfectly for a random amount of time. Usually 3 or
>>more days before it happens again.
>>
>>Does anyone have any suggestions? Maybe some different things I could
>>look for? Maybe different compile options?
>>
>>Thanks
>>Majeed Qulbain
>>
>>
>>
>>
>>
>>
>>
>>
>>Hoskinson, David P wrote:
>>
>>>We have a windows 2003 dc here at the university and I have
successfully
>>>setup samba-3.0.2-6.3E on a RHEL WS3 machine. The problem is that
after
>>>several hours, or several days winbind stops running and connections
>>>fail. I have seen instances of this on other sites, but no firm
>>>answers. I can provide files and logs if helpful
>>>
>>>
>>>/
>>