[Samba] Lots of smbd processes and connections?
Brian
bbayorgeon at charter.net
Tue Oct 27 18:01:38 MDT 2009
>On 10/27/09 4:31 PM, "Jeremy Allison" <jra at samba.org> wrote:
>> On Mon, Oct 26, 2009 at 08:57:20PM -0500, Brian wrote:
>>> Just looked .... I'm getting 500K log every 12 seconds with log level 2.
My
>>> "new" server is a box with modern hardware and so forth and its spending
24%
>>> processor time filling out logs.
>>>
>>> John suggest 3.3.8 and I realized I was at 3.3.3 so I upgraded samba to
>>> 3.3.8 and got the same result!
>>>
>>> So I have had samba version 3.0.something (older FBSD implementation,
older
>>> 166 pentium) through 3.3.8 running (7.2 FBSD implementation with modern
>>> hardware) and all of them are being flooded by vista. Ya ya I
know...blame
>>> Gates, but there must be a fix here some place?
>>>
>>> The situation with 3.3.8 is the first time I noticed dozens of samba
>>> processes spawned as a result. Earlier versions got spammed, but didn't
>>> branch a bunch of processes.
>>
>> Log a bug at bugzilla.samba.org and attach a debug level 10 log
>> from one client and also a wireshark trace. The wireshark trace
>> is very important in order to determine if this is a client or
>> server bug.
>>
>> Jeremy.
>
>Already done that :-)
>
>https://bugzilla.samba.org/show_bug.cgi?id=6782
>
>Matthew
I will try and do the same at bugzilla
but for now a bit more information after some experimentation.
When homes share definition is removed I get:
[2009/10/27 17:23:33, 0] smbd/service.c:make_connection(1292)
dadsdesktop (10.0.2.149) couldn't find service roo
[2009/10/27 17:23:33, 0] smbd/service.c:make_connection(1292)
dadsdesktop (10.0.2.149) couldn't find service roo
[2009/10/27 17:23:33, 0] smbd/service.c:make_connection(1292)
dadsdesktop (10.0.2.149) couldn't find service root
[2009/10/27 17:23:33, 0] smbd/service.c:make_connection(1292)
dadsdesktop (10.0.2.149) couldn't find service root
This supports comments from other people that the client re-tries with the
correct name and then connects. I do not have issues connecting to my home
share. Maybe some lag sometimes...
When I make a share named "roo", the "can't find service" messages go away
and I get a visible "roo" share.
Also get the following from smbstatus when I have made no attempt to connect
to the "roo" share with explorer or whatever. This tells me the client is
purposely trying to connect to "roo" by itself.
Samba version 3.3.8
PID Username Group Machine
-------------------------------------------------------------------
6848 root wheel dadsdesktop (10.0.2.149)
Service pid machine Connected at
-------------------------------------------------------
roo 6848 dadsdesktop Tue Oct 27 18:55:56 2009
root 6848 dadsdesktop Tue Oct 27 18:55:56 2009
No locked files
Seems to me the client is the issue here...
More information about the samba
mailing list