2.2.2 runaway SMBD process

Jeremy Allison jra at samba.org
Sat Nov 17 14:47:02 GMT 2001

On Sat, Nov 17, 2001 at 09:58:18AM -0000, Noel Kelly wrote:
> Hello,
> I am running Samba 2.2.2 with acl-0.7.16 on RedHat 6.2 (2.2.19).  The PDC is
> a Windows 2000 Server and the Samba server is a domain member using Winbind.
> All the workstations are Windoze 2000 Pro with SP2.
> Everything seemingly works fine but every day or two I get a runaway SMBD
> process which hogs the CPU and becomes unkillable.  The only resolution is
> to reboot the server completely.  This has occurred at least once when a
> workstation crashed but we have not proven that this is always the case.  I
> was rather hoping that it was a Windoze problem to do with not having SP2
> installed but this has now been disproved.
> This is a serious problem.  I have seen postings here before about disabling
> OPLOCKS but am reticent to do this becasue of the drop in performance which
> could put cracks in our arguments for using Samba in the first place.  Also
> I thought 2.2.2 had fixes for OPLOCK bugs!
> Does anyone have any suggestions other than disabling OPLOCKS ?  Even a way
> of killing the runaway process would be useful at this time ("kill -9" has
> no affect at all on the rogue SMBD or its children).
> We could regress to a 'more stable' version but we would lose the
> functionality of WINBIND which is important to this installation.

Can you tell me if you're getting any errors in your log files ?

When you say "unkillable" does this mean it doesn't
respond to a kill -9 ? If so this is a kernel problem
not a Samba problem.



More information about the samba mailing list