[Samba] Over 400 smbd pid's?

[Ed Kasky]

Over the past 2 days, my smbd processes are multiplying worse than 
rabbits.  At least with rabbits it's easy to tell why you wind up 
with so many...

Here's the setup:
Samba version 3.2.8-0.24 installed via rpm on a FC6 box with 2 nics, 
both on the same subnet.  The samba server acts as a PDC in a mixed 
environment but mostly windows pc's running xp.  It is used mostly 
for file (Quickbooks) and print services.

We have a small home business network with usually only 3 accounts 
connected,  and no more than 10 open files at any given time.  I 
noticed yesterday that I was having trouble logging in from one 
machine - share's not available, etc.  So I checked the daemon to 
make sure that it was running an lo and behold - there were over 400 
instances of smbd.

It took two attempts to stop them all from the init script - the 
first run seemed to only kill about 2 or 3 and the second one 
finished the job.  So I restarted and monitored the situation and all 
seemed okay for a few hours and then after about 3 hours they started 
multiplying again until I restarted the daemon again.  There was just 
normal file activity during the couple of hours that it took to go 
from 3 to over 400 pid's.

I increased the log level to 3 but all I am seeing is the normal 
wins, nmbd connections.  I am seeing a few errors but nothing 
significant I don't think - tell me if I'm wrong - but nothing in 
these log files that correlate to the timing of the runaway processes:

[2009/02/11 16:30:16,  2] smbd/server.c:open_sockets_smbd(580)
   waiting for a connection
*** WARNING *** The programme 'smbd' uses the Apple Bonjour 
compatiblity layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see 
<http://0pointer.de/avahi-compat?s=libdns_sd&e=smbd>

[2009/02/12 17:12:32,  3] lib/util_sock.c:interpret_string_addr_internal(122)
   interpret_string_addr_internal: getaddrinfo failed for name :: 
[Address family for hostname not supported]

Feb 12 10:07:01 yoda smbd[18495]: [2009/02/12 10:07:01,  0] 
lib/util_sock.c:read_socket_with_timeout(939)
Feb 12 10:07:01 yoda smbd[18495]: [2009/02/12 10:07:01,  0] 
lib/util_sock.c:get_peer_addr_internal(1676)
Feb 12 10:07:01 yoda smbd[18495]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb 12 10:07:01 yoda smbd[18495]:   read_socket_with_timeout: client 
0.0.0.0 read error = Connection reset by peer.
Feb 12 10:07:01 yoda smbd[18495]: [2009/02/12 10:07:01,  0] 
lib/util_sock.c:write_data(1136)
Feb 12 10:07:01 yoda smbd[18495]: [2009/02/12 10:07:01,  0] 
lib/util_sock.c:get_peer_addr_internal(1676)
Feb 12 10:07:01 yoda smbd[18495]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb 12 10:07:01 yoda smbd[18495]:   write_data: write failure in 
writing to client 0.0.0.0. Error Broken pipe
Feb 12 10:07:01 yoda smbd[18495]: [2009/02/12 10:07:01,  0] 
smbd/process.c:srv_send_smb(74)
Feb 12 10:07:01 yoda smbd[18495]:   Error writing 75 bytes to client. 
-1. (Transport endpoint is not connected)
Feb 12 11:44:29 yoda smbd[20241]: [2009/02/12 11:44:29,  0] 
smbd/nttrans.c:call_nt_transact_ioctl(2029)
Feb 12 11:44:29 yoda smbd[20241]:   call_nt_transact_ioctl(0x90073): 
Currently not implemented.
Feb 12 16:15:15 yoda smbd[2092]: [2009/02/12 16:15:15,  0] 
smbd/nttrans.c:call_nt_transact_ioctl(2029)
Feb 12 16:15:15 yoda smbd[2092]:   call_nt_transact_ioctl(0x9005c): 
Currently not implemented.
Feb 12 17:13:29 yoda smbd[4331]: [2009/02/12 17:13:29,  0] 
smbd/nttrans.c:call_nt_transact_ioctl(2029)
Feb 12 17:13:29 yoda smbd[4331]:   call_nt_transact_ioctl(0x9005c): 
Currently not implemented.

smb.conf sans shares:

[global]
         workgroup = ET
         server string = Samba PDC at %h running %v
         interfaces = eth0
         bind interfaces only = Yes
         username map = /etc/samba/smbusers
         log level = 2
         log file = /var/log/samba/log.%m
         time server = Yes
         printcap name = cups
         logon script = %u.bat
         logon path =
         logon home =
         domain logons = Yes
         preferred master = Yes
         domain master = Yes
         dns proxy = No
         wins support = Yes
         hosts allow = 10.10.10.0/255.255.255.0, 
128.125.63.0/255.255.255.0, 127.
         cups options = raw
         oplocks = No
         level2 oplocks = No

Any suggestions as to where to look next?

Thanks in advance...

Ed

...........................................................................

Randomly Generated Quote (710 of 1503):
If at first you don't succeed, redefine success.