Bug 2639 - smbd process causing high load
Summary: smbd process causing high load
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.14a
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-22 05:13 UTC by A. Bitz
Modified: 2005-04-25 01:58 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description A. Bitz 2005-04-22 05:13:00 UTC
Using Server with Suse 9.2 and samba-3.0.14-0.1 (rpm).

Sometimes (once a day or so) one of my smbd-processes owned by root causes high
load using all of the CPU it gets.

Killing the process is possible, samba keeps running without problems.
Comment 1 Lars Müller 2005-04-22 08:00:17 UTC
Are you running 3.0.14 or 3.0.14a?  Set bug report version is 14a while you
mentioned 14 as package version.

You might use smbstatus to check which user is connected to the high load
causing process.  Is it always the same user or client?

You might even attach strace to the process which might allow us to isolate any
infinite loop.
Comment 2 A. Bitz 2005-04-24 23:52:05 UTC
 
> Are you running 3.0.14 or 3.0.14a?  Set bug report version is 14a while you 
> mentioned 14 as package version. 
 
I'm using 3.0.14, but that version is not in the list, so I choose 3.0.14a. 
  
> You might use smbstatus to check which user is connected to the high load 
> causing process.  Is it always the same user or client? 
 
I will do this as soon as the problem occurs again. 
 
Comment 3 Lars Müller 2005-04-25 01:58:11 UTC
Please update to the 3.0.14a bug fix release.  The same packages are available at

ftp://ftp.SuSE.com/pub/projects/samba/ and
http://download.Samba.org/samba/ftp/Binary_Packages/SuSE/

Even if we added the 14a fix to our 3.0.14 packages asap you can't be sure to
have the right, fixed version running.

Please reopen the bug with the information attached requested in comment #1.